Dashboard
APISubscription Bot Payment Provider Details API
api.botsubscription.com
GET/v1/endpoint
AuthenticationBearer
Token
Stays in this tab. Required for this endpoint — the value below is what gets sent.
Examples
curl --request GET \
  --url https://api.botsubscription.com/v1/endpoint \
  --header 'Authorization: Bearer sk_live_•••'

Get a Subscription Bot Merchant Account

Retrieve detailed information about a specific merchant account. For setup status and instructions, see provider webhook verification.

GET/v2/projects/{project_id}/merchant-accounts/{merchant_account_id}

Authorization

Bearer API KeyRequired

API key scope: merchant-accounts:read (required for restricted keys).

Path Parameters

project_idstringrequired

The unique identifier of the project.

merchant_account_idstringrequired

The unique identifier of the merchant account.

Query Parameters

expandstring

Use requirements for field definitions, requirements.enabled for enabled choices, or requirements.available for available choices. Crypto payment-currency options are merchant-specific.

When options.enabled is returned for a requirement, each choice has string value and label fields, with optional description and opaque object metadata. Pass the selected value to checkout unchanged. An expansion can omit enabled; do not infer choices or a universal network list when it is absent.

supported_currencies, when included, is either a list of currency codes or true for all currencies. currency_compatible reports compatibility with the selected currency context; these fields may be omitted.

Manual webhook providers can include webhook_setup with a URL, instructions, an optional dashboard URL and optional missing_credentials names. Project API keys do not receive webhook signing secrets. If setup information cannot be built, webhook_setup_error: true can be returned without the setup block; retry the detail request. The account response itself still uses HTTP 200.

Last updated: