> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useplinth.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Change plan

> Commits a plan change. For upgrades (by default): charges the prorated difference immediately. For downgrades (by default): schedules the change at the next period end — no charge now. This behaviour is controlled by your TenantPolicy preset.




## OpenAPI

````yaml POST /v1/subscriptions/{id}/change
openapi: 3.0.3
info:
  title: Plinth API
  version: 0.9.0
  description: >
    Recurring billing for Nigerian SaaS — card charging, bank transfers via
    virtual accounts,

    proration, dunning, and recovery in one API.


    All amounts are in **kobo** (1/100th of a Naira). ₦5,000 = `500000`.
servers:
  - url: https://api.useplinth.com
    description: Production
  - url: http://localhost:7331
    description: Local development
security:
  - BearerAuth: []
tags:
  - name: Sandbox
    description: Create an isolated sandbox environment for testing. No auth required.
  - name: Customers
    description: Who you are billing. One customer can have multiple subscriptions.
  - name: Plans
    description: Plan groups and the plans within them. Customers subscribe to plans.
  - name: Subscriptions
    description: The recurring billing relationship between a customer and a plan.
  - name: Virtual Accounts
    description: Dedicated bank account numbers for customers who pay by transfer.
  - name: Invoices
    description: Created at each billing cycle. Tracks what a customer owes for a period.
  - name: Webhooks
    description: >-
      Register endpoints that receive signed, retried events. See Receiving
      webhooks.
  - name: Admin
    description: Test clock control, billing tick, and suspense resolution. Test-mode only.
paths:
  /v1/subscriptions/{id}/change:
    post:
      tags:
        - Subscriptions
      summary: Change plan
      description: >
        Commits a plan change. For upgrades (by default): charges the prorated
        difference immediately. For downgrades (by default): schedules the
        change at the next period end — no charge now. This behaviour is
        controlled by your TenantPolicy preset.
      operationId: change-plan
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          example: sub_01JABC...
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - plan_id
              properties:
                plan_id:
                  type: string
                  example: pln_01JABC...
                quantity:
                  type: integer
                  example: 1
      responses:
        '200':
          description: Plan changed or change scheduled
          content:
            application/json:
              schema:
                type: object
                properties:
                  object:
                    type: string
                    enum:
                      - subscription
                  strategy:
                    type: string
                    enum:
                      - immediate_prorated
                      - at_period_end
                      - at_trial_end
                  direction:
                    type: string
                    enum:
                      - upgrade
                      - downgrade
                      - lateral
                  invoice_id:
                    type: string
                    nullable: true
                  amount_charged_minor:
                    type: string
                    nullable: true
                  credit_applied_minor:
                    type: string
                    nullable: true
                  scheduled_for:
                    type: string
                    format: date-time
                    nullable: true
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >
        Use `sk_test_` keys for sandbox. Use `sk_live_` keys for production.
        Obtain your key from the dashboard.

````