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

# Create sub-account

> Create a new sub-account (project) with its own API key. All charges are billed to the parent team's balance. Use creditLimit to set a spending cap. The sub-account's API key is returned only in the creation response. Requires a parent project API key; sub-account API keys receive HTTP 403.



## OpenAPI

````yaml /openapi.json post /v1/sub-accounts
openapi: 3.0.3
info:
  title: Zavu Unified Messaging Layer API
  version: 0.2.0
  description: >
    Unified multi-channel messaging API for Zavu.


    Supported channels:

    - **SMS**: Simple text messages

    - **WhatsApp**: Rich messaging with media, buttons, lists, CTA URL buttons,
    and templates

    - **Telegram**: Bot messaging with text, media, and interactive elements

    - **Email**: Transactional emails via Amazon SES


    Design goals:

    - Simple `send()` entrypoint for developers

    - Project-level authentication via Bearer token

    - Support for all WhatsApp message types (text, image, video, audio,
    document, sticker, location, contact, buttons, list, cta_url, reaction,
    template)

    - If a non-text message type is sent, WhatsApp channel is used automatically

    - 24-hour WhatsApp conversation window enforcement

    - Universal `to` field accepts phone numbers (E.164), email addresses, or
    numeric chat IDs (Telegram/Instagram)
servers:
  - url: https://api.zavu.dev
security:
  - bearerAuth: []
paths:
  /v1/sub-accounts:
    post:
      tags:
        - Sub-Accounts
      summary: Create sub-account
      description: >-
        Create a new sub-account (project) with its own API key. All charges are
        billed to the parent team's balance. Use creditLimit to set a spending
        cap. The sub-account's API key is returned only in the creation
        response. Requires a parent project API key; sub-account API keys
        receive HTTP 403.
      operationId: createSubAccount
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SubAccountCreateRequest'
            examples:
              basic:
                summary: Basic sub-account
                value:
                  name: Client ABC
              with_limit:
                summary: Sub-account with spending cap
                value:
                  name: Client ABC
                  externalId: client_123
                  creditLimit: 100000
      responses:
        '201':
          description: Sub-account created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SubAccountResponse'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Forbidden. Sub-account API keys cannot manage sub-accounts.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
components:
  schemas:
    SubAccountCreateRequest:
      type: object
      required:
        - name
      properties:
        name:
          type: string
          maxLength: 200
          description: Name of the sub-account.
          example: Client ABC
        externalId:
          type: string
          description: External reference ID for your own tracking.
        creditLimit:
          type: integer
          minimum: 0
          description: >-
            Spending cap in cents. When reached, messages from this sub-account
            will be blocked. Omit or set to 0 for no limit.
        metadata:
          type: object
          additionalProperties: true
    SubAccountResponse:
      type: object
      required:
        - subAccount
      properties:
        subAccount:
          $ref: '#/components/schemas/SubAccount'
    Error:
      type: object
      required:
        - code
        - message
      properties:
        code:
          type: string
          example: invalid_request
        message:
          type: string
          example: Phone number is invalid
        details:
          type: object
          additionalProperties: true
    SubAccount:
      type: object
      required:
        - id
        - name
        - status
        - totalSpent
        - createdAt
      properties:
        id:
          type: string
        name:
          type: string
          example: Client ABC
        externalId:
          type: string
          nullable: true
          description: External reference ID set by the parent account.
        status:
          $ref: '#/components/schemas/SubAccountStatus'
        totalSpent:
          type: integer
          description: Total amount spent by this sub-account in cents.
        creditLimit:
          type: integer
          nullable: true
          description: >-
            Spending cap in cents. When reached, messages from this sub-account
            will be blocked.
        metadata:
          type: object
          nullable: true
          additionalProperties: true
        apiKey:
          type: string
          description: API key for the sub-account. Only returned on creation.
        createdAt:
          type: string
          format: date-time
    SubAccountStatus:
      type: string
      enum:
        - active
        - inactive
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````