Whop Checkout Configurations API

Reusable checkout / payment flow configurations.

Operations 4

GET /checkout_configurations List checkout configurations #
POST /checkout_configurations Create a checkout configuration #
GET /checkout_configurations/{id} Retrieve a checkout configuration #
DELETE /checkout_configurations/{id} Delete a checkout configuration #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/whop-checkout-configurations-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

whop-checkout-configurations-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Whop REST API (v1) Checkout Configurations API
  description: 'The Whop REST API (v1) is the current primary REST surface for the Whop digital-products / memberships / creator-commerce platform. It lets applications manage memberships and access, products (access passes) and their pricing plans, take payments and issue refunds, manage users and companies, build checkout flows, pay out users via transfers, and register webhooks. All requests are authenticated with a Bearer token (`Authorization: Bearer <API_KEY>`); a Company/Account API key and an App API key are the two key types, with OAuth tokens used when acting on behalf of a signed-in Whop user.

    Grounding notes: base URLs, the Bearer scheme, the `List memberships` and `List payments` query parameters and response fields, and the resource / operation catalog are taken from Whop''s published documentation at docs.whop.com (see the docs `llms.txt` index). Individual action sub-paths (for example the cancel / pause / resume membership actions) are modeled from the documented operation names; verify exact path segments against the live reference on reconciliation.'
  version: '1.0'
  contact:
    name: API Evangelist
    email: kin@apievangelist.com
    url: https://apievangelist.com
  license:
    name: API documentation - Whop Terms of Service
    url: https://whop.com/terms-of-service/
servers:
- url: https://api.whop.com/api/v1
  description: Production
- url: https://sandbox-api.whop.com/api/v1
  description: Sandbox
security:
- bearerAuth: []
tags:
- name: Checkout Configurations
  description: Reusable checkout / payment flow configurations.
paths:
  /checkout_configurations:
    get:
      operationId: listCheckoutConfigurations
      tags:
      - Checkout Configurations
      summary: List checkout configurations
      responses:
        '200':
          description: A page of checkout configurations.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/CheckoutConfiguration'
                  page_info:
                    $ref: '#/components/schemas/PageInfo'
    post:
      operationId: createCheckoutConfiguration
      tags:
      - Checkout Configurations
      summary: Create a checkout configuration
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CheckoutConfiguration'
      responses:
        '201':
          description: The created checkout configuration.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CheckoutConfiguration'
  /checkout_configurations/{id}:
    parameters:
    - name: id
      in: path
      required: true
      schema:
        type: string
    get:
      operationId: retrieveCheckoutConfiguration
      tags:
      - Checkout Configurations
      summary: Retrieve a checkout configuration
      responses:
        '200':
          description: A checkout configuration.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CheckoutConfiguration'
    delete:
      operationId: deleteCheckoutConfiguration
      tags:
      - Checkout Configurations
      summary: Delete a checkout configuration
      responses:
        '204':
          description: The checkout configuration was deleted.
components:
  schemas:
    PageInfo:
      type: object
      description: Cursor pagination metadata.
      properties:
        has_next_page:
          type: boolean
        has_previous_page:
          type: boolean
        start_cursor:
          type:
          - string
          - 'null'
        end_cursor:
          type:
          - string
          - 'null'
    CheckoutConfiguration:
      type: object
      description: A reusable checkout / payment flow configuration.
      properties:
        id:
          type: string
        plan_id:
          type:
          - string
          - 'null'
        redirect_url:
          type:
          - string
          - 'null'
        metadata:
          type: object
          additionalProperties: true
        created_at:
          type: string
          format: date-time
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Whop API key
      description: 'Bearer token authentication. Use a Company/Account API key or an App API key in the `Authorization: Bearer <API_KEY>` header. OAuth access tokens are used when acting on behalf of a signed-in Whop user.'