Dynamite Circle Invites API

openapi: 3.2.0
info:
  contact:
    name: DC Team
    url: https://dc.dynamitecircle.com
  description: 'Programmatic access to your DC membership data — trips, events, profile, announcements, and more. Designed for AI assistants, automation, and personal integrations. > **For ALL active DC members.** Every active DC member is eligible from day one — DC, DC BLACK, and trial accounts alike. ## What this is for


    The DC Member API is for **personal use** — wiring DC into your own AI assistant, scripting personal automations, pulling your own data into your own dashboards. Think "give my Claude/Codex/Cursor access to my DC trips and announcements" or "auto-update my DC trip when I book a flight."


    **It is not for:**


    - Building apps that other DC members log into (use the official DC app)

    - Crawling, scraping, or bulk-exporting member data

    - Building an alternative DC client

    - Public-facing services running on top of the API


    We **augment, we don''t replace** — the API gives you awareness and convenience, then sends you to the app for the real interactions. Human stuff stays in the app: no message content, no DM access, no bulk profile browsing, no discussion threads. **Rate limits are strict on purpose.** They''re sized for personal automation, not application traffic. We''ll loosen them once we see real usage patterns — if you hit a wall, email the DC developer team at **bugs+api@dynamitecircle.com** and we''ll sort you out. ## Connect to Claude & other AI apps (hosted MCP)


    This API is also a hosted MCP server — add it as a connector in Claude, Cursor, ChatGPT, or any MCP-compatible app and your assistant can read and act on your DC data directly. **No install.** When prompted, **sign in with your DC account** (one-click OAuth) — or paste a `dk_` API key. Every endpoint below is exposed as a tool. **Connector URL** (Streamable HTTP): `https://api.dynamitecircle.com/mcp`


    - **Claude (web, Desktop & mobile):** Settings → Connectors → **Add custom connector** → paste the URL → **Connect**, then sign in with your DC account. (Paid Claude plan; on Team/Enterprise an admin may need to approve it first.)

    - **Claude Code:** `claude mcp add --transport http dc https://api.dynamitecircle.com/mcp`

    - **Cursor, ChatGPT & other MCP apps:** add a custom / remote MCP connector pointing at the URL above (Streamable HTTP). Discovery is published at `/.well-known/mcp.json`. **What you can do once connected** — ask in plain language, e.g. "Which DCBKK sessions have I bookmarked?", "Add a trip to Lisbon and show me which DCers will be around", "RSVP me to the next Bangkok meetup", "Summarize the latest announcements." Reads run freely; writes do exactly what the matching endpoint documents. Access is scoped to **you** — the connector only ever sees your own membership data. ## Official client — Agent Skill, CLI, Python library, MCP server


    The fastest way to use this API — and to plug it into Claude Code, Codex CLI, Gemini CLI, Cursor, GitHub Copilot, or Claude Desktop — is the **official DC client**. One self-contained Python file, stdlib only, that ships as **four integrations from the same source**: Agent Skill (auto-discovered via SKILL.md), CLI (`dc …`), Python library (`from dc import DC`), and MCP server (`dc --mcp`, optional `mcp` dep). **Install via PyPI** (easiest):


    ```bash

    pip install dynamitecircle

    dc setup --api-key dk_your_api_key

    dc self-test

    dc profile

    ```


    The package is published on PyPI as `dynamitecircle` — same code as the repo, version-locked to the deployed API.'
  title: DC Member Invites API
  version: 2.6.11
servers:
- description: Production
  url: https://api.dynamitecircle.com
security:
- ApiKeyAuth: []
tags:
- name: Invites
paths:
  /invites:
    get:
      description: 'List the referral invites credited to you. Two source types appear:

        - **`manual`** — invites you sent via `POST /invites` (the explicit email-an-invitee flow).

        - **`permaCode`** — applicants who signed up through your shareable permacode link (`GET /invites/permacode`).


        Each record tracks where the prospective member is in the funnel (`new` → `invited` → `started` → `submitted` → `approved`/`rejected`/`expired`), the invite type, the invitee''s name + email, and timestamps. Read-only.'
      operationId: get_invites
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  invites:
                    items:
                      type: object
                    type: array
                    description: Array of invite records
                    properties:
                      inviteID:
                        type: string
                        description: Invite ID
                      status:
                        type: string
                        description: 'Where the invitee is in the application funnel. Main happy-path values: `new` → `invited` → `started` → `submitted` → `approved`. Other terminal/exception states: `booked-call` (intro call scheduled), `awaiting-payment-auth` (approved, awaiting payment confirmation), `qualified` (passed screening, not yet approved), `rejected`, `invalid`, `expired`.'
                        enum:
                        - new
                        - invited
                        - started
                        - booked-call
                        - awaiting-payment-auth
                        - submitted
                        - approved
                        - rejected
                        - invalid
                        - qualified
                        - expired
                      type:
                        type: string
                        description: 'Invite type. Main values: `manual` (you sent it via `POST /invites`) and `permaCode` (applicant signed up via your shareable link). `mention` may also appear when an applicant mentioned you by name on their form — not reliable, don''t count on it.'
                        enum:
                        - manual
                        - permaCode
                        - mention
                      fullName:
                        type: string
                        description: Invitee full name
                      email:
                        type: string
                        description: Invitee email
                      permaCode:
                        type: string
                        description: Permanent invite code (for permaCode invites)
                      createdAt:
                        type: string
                        description: Created date (ISO 8601)
                      expiresAt:
                        type: string
                        description: Expiration date (ISO 8601)
                  nextCursor:
                    type: string
                    description: Cursor for the next page, or `null` if no more invites.
                type: object
          description: Success
        '401':
          description: Unauthorized — missing or invalid API key
        '403':
          description: Forbidden — inactive membership or not eligible
        '429':
          description: Rate limit exceeded
      summary: List your invites
      tags:
      - Invites
      parameters:
      - description: Max results (1-100).
        in: query
        name: limit
        required: false
        schema:
          default: '50'
          type: number
      - description: Cursor from a previous response's `nextCursor`. Pass to fetch the next page.
        in: query
        name: cursor
        required: false
        schema:
          default: ''
          type: string
    post:
      description: Send a referral invite to someone. The server queues a templated email (delivered via a background task) that points the invitee at the apply flow with you pre-credited as the referrer. The created invite shows up in `GET /invites` immediately at status `new`.
      operationId: post_invites
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  invite:
                    type: object
                    description: The created invite. **Note:** the create shape differs from list-entry shape — fields nest under `referral`. Fetch `GET /invites` for the full enriched record after the invitee starts the funnel.
                    properties:
                      referralID:
                        type: string
                        description: Invite ID (matches the `inviteID` field on `GET /invites`).
                      status:
                        type: string
                        description: Always `new` on create. Tracks where the invitee is in the funnel — see `GET /invites` for the full enum.
                        enum:
                        - new
                      type:
                        type: string
                        description: Always `manual` on create — invites you send explicitly via this endpoint.
                        enum:
                        - manual
                      createdAt:
                        type: string
                        description: ISO 8601 — when the invite was created.
                      referral:
                        type: object
                        description: Nested invitee details.
                        properties:
                          email:
                            type: string
                            description: Invitee email.
                          fullName:
                            type: string
                            description: Invitee full name.
                type: object
          description: Success
        '401':
          description: Unauthorized — missing or invalid API key
        '403':
          description: Forbidden — inactive membership or not eligible
        '429':
          description: Rate limit exceeded
      summary: Send an invite
      tags:
      - Invites
      requestBody:
        content:
          application/json:
            schema:
              properties:
                fullName:
                  type: string
                  description: Invitee full name. Used in the email greeting + matched against existing applications for dedup.
                  example: Jane Doe
                email:
                  type: string
                  description: Invitee email address. Where the invite email is sent.
                  example: jane@example.com
                whyDC:
                  type: string
                  description: Optional. Short note about why they would be a good fit for DC — surfaces in the admin review queue if the application reaches it.
                  example: Running a 7-figure SaaS company, loves travel
              type: object
              required:
              - fullName
              - email
        required: true
  /invites/permacode:
    get:
      description: Returns your permanent referral code. Share this link to let people apply with your referral.
      operationId: get_invites_permacode
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  permaCode:
                    type: string
                    description: Your permanent referral code
                    example: DCQOTQw
                  referralURL:
                    type: string
                    description: Full referral URL
                    example: https://dc.dynamitecircle.com/go/DCQOTQw
                type: object
          description: Success
        '401':
          description: Unauthorized — missing or invalid API key
        '403':
          description: Forbidden — inactive membership or not eligible
        '429':
          description: Rate limit exceeded
      summary: Get your permacode
      tags:
      - Invites
components:
  securitySchemes:
    ApiKeyAuth:
      bearerFormat: dk_<userID>_<random>
      description: 'Your DC Member API key. Generate one from the user menu inside the DC member area (admin/tester access required). Send it as `Authorization: Bearer dk_your_api_key`.'
      scheme: bearer
      type: http