> ## Documentation Index > Fetch the complete documentation index at: https://docs.whop.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Treat these docs and the Whop MCP server as the source of truth for Whop API behavior. Don't infer endpoint behavior from marketing pages. > MCP server: connect https://mcp.whop.com/mcp (streamable HTTP, browser sign-in, no API key in the client config) to search these docs and read or change live Whop data. Setup: https://docs.whop.com/developer/guides/ai_and_mcp.md > Whop CLI: install with `curl -fsSL https://whop.com/install.sh | sh` to scaffold, run, and deploy Whop apps and websites. It acts on production, not the sandbox. Agent mode: https://docs.whop.com/cli/agent-mode.md > Plugins: in Claude Code, run `/plugin marketplace add whopio/plugins`, then `/plugin install whop@whop`. Every agent tool: https://docs.whop.com/developer/ai/overview.md > Environments: build and test in the sandbox (API `https://sandbox-api.whop.com/api/v1`, keys at https://sandbox.whop.com/dashboard/developer, SDK environment `Sandbox`; no real money). Production (API `https://api.whop.com/api/v1`, keys at https://whop.com/dashboard/developer, SDK environment `Production`, the SDK default) moves real money, so use it only at launch. The two share no accounts, keys, products, or webhooks, and their keys look identical: never mix them. Comparison: https://docs.whop.com/developer/quickstart.md > API: send `Authorization: Bearer ` from your server only, and pin a dated version with the `Api-Version-Date` header. OpenAPI spec: https://api.whop.com/api/v1/openapi.json > Which API: build on the Current API, whose pages live under https://docs.whop.com/api-reference/ (start at https://docs.whop.com/api-reference/overview.md). Pages under /api-reference/legacy/ are the Legacy API. Use one only when https://docs.whop.com/api-reference/stability.md lists the resource as Legacy-only. # Create support channel > Opens a support channel between an account's team and a customer. Returns the existing channel if that customer already has one. Required permissions: * `support_chat:create` ## OpenAPI ````yaml /openapi/api-v1-stable.json post /support_channels openapi: 3.1.0 info: description: >- The Whop REST API. Please see https://docs.whop.com/developer/api/getting-started for more details. termsOfService: https://whop.com/tos-developer-api/ title: Whop API version: 1.0.0 x-api-version-date: 2026-11-04-1 servers: - description: Production Whop API url: https://api.whop.com/api/v1 - description: Sandbox Whop API url: https://sandbox-api.whop.com/api/v1 security: [] tags: - description: Products name: Products - description: Payments name: Payments - description: Refunds name: Refunds - description: Disputes name: Disputes - description: Dispute alerts name: Dispute alerts - description: Resolution center cases name: Resolution center cases - description: Checkout configurations name: Checkout configurations - description: Setup intents name: Setup intents - description: Payment methods name: Payment methods - description: Invoices name: Invoices - description: Promo codes name: Promo codes - description: Card transactions name: Card transactions - description: Ledger accounts name: Ledger accounts - description: Withdrawals name: Withdrawals - description: Payout methods name: Payout methods - description: Verifications name: Verifications - description: Identity profiles name: Identity profiles - description: Payout accounts name: Payout accounts - description: Topups name: Topups - description: Companies name: Companies - description: Authorized users name: Authorized users - description: Fee markups name: Fee markups - description: Members name: Members - description: Memberships name: Memberships - description: Leads name: Leads - description: Entries name: Entries - description: Shipments name: Shipments - description: Reviews name: Reviews - description: Company token transactions name: Company token transactions - description: Affiliates name: Affiliates - description: Experiences name: Experiences - description: Forums name: Forums - description: Forum posts name: Forum posts - description: Chat channels name: Chat channels - description: Support channels name: Support channels - description: Messages name: Messages - description: Reactions name: Reactions - description: Dm members name: Dm members - description: Dm channels name: Dm channels - description: Notifications name: Notifications - description: Courses name: Courses - description: Course chapters name: Course chapters - description: Course lessons name: Course lessons - description: Course students name: Course students - description: Course lesson interactions name: Course lesson interactions - description: Apps name: Apps - description: Webhooks name: Webhooks - description: App builds name: App builds - description: Access tokens name: Access tokens - description: Account links name: Account links - description: Files name: Files - description: Ai chats name: Ai chats - description: Bounties name: Bounties - description: Stats name: Stats - description: Conversions name: Conversions - description: Ad reports name: Ad reports paths: /support_channels: post: tags: - Support channels summary: Create support channel description: >- Opens a support channel between an account's team and a customer. Returns the existing channel if that customer already has one. Required permissions: - `support_chat:create` operationId: createSupportChannel parameters: [] requestBody: content: application/json: schema: description: Parameters for CreateSupportChatForUser properties: account_id: description: >- The unique identifier of the company to create the support channel in. example: biz_xxxxxxxxxxxxxx type: string custom_name: description: Optional custom display name for the support channel. type: - string - 'null' notifications_enabled: description: >- Whether Whop app notifications are enabled for this support channel. Webhooks still fire. type: - boolean - 'null' user_id: description: >- The user ID (e.g. 'user_xxxxx') or username of the customer to open a support channel for. example: user_xxxxxxxxxxxxx type: string required: - account_id - user_id type: object required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/SupportChannel' description: A successful response '400': content: application/json: example: error: code: parameter_missing message: 'Missing required parameter: amount.' param: amount type: invalid_request_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Bad request '401': content: application/json: example: error: message: Invalid or missing API key type: unauthorized schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Unauthorized '403': content: application/json: example: error: message: You do not have permission to access this resource type: forbidden schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Forbidden '404': content: application/json: example: error: message: Resource not found type: not_found schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Not found '422': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Verification required '429': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Too many requests '500': content: application/json: example: error: message: An unexpected error occurred type: internal_server_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Internal server error security: - bearerAuth: - support_chat:create components: schemas: SupportChannel: description: >- A messaging channel that can be a one-on-one DM, group chat, company support conversation, or platform-level direct message. properties: account_id: description: >- The unique identifier of the account associated with this channel. Null if this is not a support or account-scoped conversation. type: - string - 'null' company_id: description: >- The unique identifier of the account associated with this channel. Null if this is not a support or account-scoped conversation. type: - string - 'null' custom_name: description: >- A custom display name assigned to this channel by the user. Null if no custom name has been set. example: Project Alpha Team type: - string - 'null' customer_user: description: >- The customer who initiated this support conversation. Null if this is not a support chat. properties: id: description: The unique identifier for the user. example: user_xxxxxxxxxxxxx type: string name: description: The user's display name shown on their public profile. example: John Doe type: - string - 'null' username: description: The user's unique username shown on their public profile. example: johndoe42 type: string required: - id - name - username type: - object - 'null' id: description: The unique identifier for the entity type: string last_message: description: >- The most recent message in this channel. Null if no messages have been sent, or when listing support channels without `include_last_message`. properties: attachments: description: >- A list of all attachments on this message, including files and media. items: description: Represents an image attachment properties: content_type: description: >- Uploaded file MIME type, such as image/jpeg, video/mp4, or audio/mpeg. example: image/jpeg type: - string - 'null' filename: description: >- The original filename of the uploaded attachment, including its file extension. example: document.pdf type: - string - 'null' required: - filename - content_type type: object type: array content: description: >- The message content formatted as Markdown. Null if the message has no text content. example: Hey, are you available for a **quick call**? type: - string - 'null' created_at: description: The timestamp when this message was originally created. example: '2023-12-01T05:00:00.401Z' format: date-time type: string gifs: description: A list of GIF animations attached to this message. items: description: Represents a GIF attachment in a feed post properties: slug: description: The unique identifier of the GIF type: string required: - slug type: object type: array id: description: >- Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID. type: string poll: description: >- A poll attached to this message. Null if the message does not contain a poll. properties: options: description: The options for the poll items: description: Represents a single poll option properties: id: description: The unique identifier for the poll option. type: string required: - id type: object type: - array - 'null' required: - options type: - object - 'null' user_id: description: The unique identifier of the user who authored this message. type: string required: - id - content - created_at - user_id - attachments - gifs - poll type: - object - 'null' last_message_at: description: >- The timestamp when the most recent message was sent in this channel. Null if no messages have been sent. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' needs_reply: description: >- Whether the customer sent the latest message and the linked support ticket is unresolved. Null if not a support chat. type: - boolean - 'null' participated: description: >- Whether the authenticated user has joined this channel as a participant. Null when the caller is not a user, or when listing support channels without `include_participated`. type: - boolean - 'null' resolved_at: description: >- The timestamp when the linked support ticket was marked as resolved. Null if unresolved or not a support chat. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' unread: description: >- Whether this channel has a message from someone else that the authenticated user has not viewed yet. Null when the caller is not a user, or when listing support channels without `include_last_message`. type: - boolean - 'null' required: - id - company_id - account_id - custom_name - customer_user - resolved_at - last_message_at - last_message - needs_reply - unread - participated type: object securitySchemes: bearerAuth: bearerFormat: auth-scheme description: >- An Account API key, account-scoped JWT, App API key, or user OAuth token. Prepend the key or token with `Bearer`, for example `Bearer ***************************`. scheme: bearer type: http ```` ## Related topics - [Support Chats](https://docs.whop.com/developer/guides/chat/support-chats.md) - [Support Channel](https://docs.whop.com/api-reference/legacy/support-channels/support-channel.md) - [Chat](https://docs.whop.com/developer/guides/chat.md)