> ## 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.

# Create a plan group

> A plan group is a named collection of plans (e.g., "Core" containing Starter, Pro, Max). Create the group first, then add plans to it.




## OpenAPI

````yaml POST /v1/plan-groups
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/plan-groups:
    post:
      tags:
        - Plans
      summary: Create a plan group
      description: >
        A plan group is a named collection of plans (e.g., "Core" containing
        Starter, Pro, Max). Create the group first, then add plans to it.
      operationId: create-plan-group
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - name
              properties:
                name:
                  type: string
                  maxLength: 100
                  example: Core
                description:
                  type: string
                  maxLength: 500
                  example: Main product tiers
      responses:
        '201':
          description: Plan group created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PlanGroup'
components:
  schemas:
    PlanGroup:
      type: object
      properties:
        object:
          type: string
          enum:
            - plan_group
        id:
          type: string
          example: pg_01JABC...
        name:
          type: string
          example: Core
        created_at:
          type: string
          format: date-time
  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.

````