Qualpay · Schema
AddSubscriptionRequest
PaymentsPayment ProcessingMerchant ServicesB2B PaymentsReportingTokenization
Properties
| Name | Type | Description |
|---|---|---|
| date_start | string | Format: Fixed length, 10, YYYY-MM-DD format Description: Date the subscription will start. |
| customer_id | string | Format: Variable length, up to 32 AN Description: Customer ID of the subscriber. Customer ID must be for a valid customer profile stored in Customer Vault. A custo |
| customer | object | |
| card_id | string | Format: Fixed length, 32 AN Description: By default, when a subscription is added to a customer, the recurring charges will be billed to the customer's primary pay |
| plan_code | string | Format: Variable length, up to 16 AN Description: Plan code of the recurring plan. Plan should be an active and valid recurring plan. Conditional Requir |
| plan_desc | string | Format: Variable length, AN Description: A short description of the one-off plan. Applicable only to one-off, off-plan subscriptions. |
| plan_frequency | integer | Format: Fixed length, 1 N Description: This field identifies the frequency of billing. Applicable only to one-off subscriptions. Use one of the following codes fo |
| interval | integer | Format: Variable length, up to 2 N Description: Number of months or weeks in a monthly or weekly subscription cycle, respectively. Applicable only for monthly or |
| plan_duration | integer | Format: Variable length, up to 4 N Description: Number of billing cycles in the recurring subscription. Use `-1` if billing cycles are indefinite. Applicable only |
| amt_setup | number | Format: Variable length, up to 12,2 N Description: One-time fee amount. This fee will be charged immediately when a subscription is added. Applicable only to one-o |
| amt_setup_ignore | boolean | Description: By default, if a recurring plan has a one-time fee, the customer is charged the one-time fee when the subscription is created. If `amt_setup_ignore` is set to `true`, th |
| cancel_on_setup_fail | boolean | Description: If the subscription requires a one-time fee, setting `cancel_on_setup_fail` to `true` causes the system to cancel the subscription if the one-time fee cannot be charged |
| amt_tran | number | Format: Variable length, up to 12,2 N Description: Plan transaction amount, which is the amount that will be billed each cycle period. Applicable only to one-off s |
| profile_id | string | Format: Fixed length, 20 N Description: Payment Gateway profile ID that will be used when billing transactions. If `profile_id` is not provided, `tran_currency` wi |
| tran_currency | string | Format: Fixed length, 3 AN Description: The ISO numeric currency code. This must be a currency code associated with one of your payment profiles; contact Qualpay t |
| use_existing_customer | boolean | Description: When set to `true`, the system will try to use an existing `customer_id` if one is available. If there is an existing customer with the same `customer_first_name` and `c |
| pct_tran_fee | number | Format: Percentage of transaction that will be added as a transaction fee. Transaction fees can be used only if merchant is enabled to use them and if the selected payment supports th |
| pct_fee | number | Format: Variable length, up to 3,2 N Description: Percentage of the transaction that will be added as a surcharge. A surcharge is a fee added to the cost of a purc |
| purchase_id | string | Format: Variable length, up to 25 AN Description: Purchase identifier (also referred to as the invoice number generated by the merchant) included in the recurring |
| merchant_id | integer | Format: Variable length, up to 16 AN Description: Identifies the merchant to whom this request applies. Optional field, applicable only if the request is sent on b |
| custom_fields | array | Custom fields for the subscription. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/qualpay/json-schema/qualpay-add-subscription-request-schema.json",
"title": "AddSubscriptionRequest",
"x-generated": "2026-11-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/qualpay-recurring-billing-api-openapi.yml#/components/schemas/AddSubscriptionRequest",
"required": [
"date_start"
],
"type": "object",
"properties": {
"date_start": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 10, YYYY-MM-DD format<br><strong>Description: </strong>Date the subscription will start."
},
"customer_id": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Customer ID of the subscriber. Customer ID must be for a valid customer profile stored in Customer Vault. A customer profile can also be created while adding a subscription by using the customer field.<br><strong>Conditional Requirement: </strong>Either `customer_id` or `customer` is required."
},
"customer": {
"$ref": "#/$defs/AddCustomerRequest"
},
"card_id": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 32 AN<br><strong>Description: </strong>By default, when a subscription is added to a customer, the recurring charges will be billed to the customer's primary payment method. This can be overridden to charge against any of the customer's payment methods by sending any `card_id` belonging to the customer in this field. "
},
"plan_code": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Plan code of the recurring plan. Plan should be an active and valid recurring plan.<br><strong>Conditional Requirement: </strong> Required for on-plan subscriptions. "
},
"plan_desc": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, AN<br><strong>Description: </strong>A short description of the one-off plan. Applicable only to one-off, off-plan subscriptions. "
},
"plan_frequency": {
"type": "integer",
"description": "<strong>Format: </strong>Fixed length, 1 N<br><strong>Description: </strong> This field identifies the frequency of billing. Applicable only to one-off subscriptions. Use one of the following codes for frequency: <ul> <li>`0` - Weekly</li> <li>`1` - Bi-weekly</li> <li>`3` - Monthly</li> <li>`4` - Quarterly</li> <li>`5` - Bi-annually</li> <li>`6` - Annually</li> <li>`7` - Daily</li> </ul><p><strong>Conditional Requirement: </strong>Required for one-off subscriptions.</p>",
"format": "int32"
},
"interval": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 2 N<br><strong>Description: </strong> Number of months or weeks in a monthly or weekly subscription cycle, respectively. Applicable only for monthly or weekly `plan_frequency`.",
"format": "int32"
},
"plan_duration": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 4 N<br><strong>Description: </strong>Number of billing cycles in the recurring subscription. Use `-1` if billing cycles are indefinite. Applicable only to one-off subscriptions. <br><strong>Conditional Requirement: </strong>Required for one-off subscriptions. ",
"format": "int32"
},
"amt_setup": {
"type": "number",
"description": "<strong>Format: </strong>Variable length, up to 12,2 N<br><strong>Description: </strong>One-time fee amount. This fee will be charged immediately when a subscription is added. Applicable only to one-off subscriptions. ",
"format": "double"
},
"amt_setup_ignore": {
"type": "boolean",
"description": "<strong>Description: </strong> By default, if a recurring plan has a one-time fee, the customer is charged the one-time fee when the subscription is created. If `amt_setup_ignore` is set to `true`, the system does not charge the one-time fee. <br><strong>Default: </strong>false"
},
"cancel_on_setup_fail": {
"type": "boolean",
"description": "<strong>Description: </strong> If the subscription requires a one-time fee, setting `cancel_on_setup_fail` to `true` causes the system to cancel the subscription if the one-time fee cannot be charged successfully. <br><strong>Default: </strong>false"
},
"amt_tran": {
"type": "number",
"description": "<strong>Format: </strong>Variable length, up to 12,2 N<br><strong>Description: </strong>Plan transaction amount, which is the amount that will be billed each cycle period. Applicable only to one-off subscriptions. <br><strong>Conditional Requirement: </strong>Required for one-off subscription. ",
"format": "double"
},
"profile_id": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 20 N<br><strong>Description: </strong>Payment Gateway profile ID that will be used when billing transactions. If `profile_id` is not provided, `tran_currency` will be used. If neither `profile_id` nor `tran_currency` is provided, the default USD profile is used. Applicable only to one-off subscriptions. "
},
"tran_currency": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 3 AN<br><strong>Description: </strong>The ISO numeric currency code. This must be a currency code associated with one of your payment profiles; contact Qualpay to add currencies. If `profile_id` is provided, the currency is determined from the profile. Refer to <a href=\"/docs/references#currency-codes\" target=\"_blank\">Currency Codes</a> for a list of currency codes. Applicable only to one-off subscriptions.<br><strong>Default: </strong>840"
},
"use_existing_customer": {
"type": "boolean",
"description": "<strong>Description: </strong> When set to `true`, the system will try to use an existing `customer_id` if one is available. If there is an existing customer with the same `customer_first_name` and `customer_last_name` and primary `card_number` or `card_id`, then the subscription is added to the matching customer. If a customer is not found, a new customer is generated. The generated `customer_id` will be returned in the response. <br><strong>Default: </strong>false<br><strong>Conditional Requirement: </strong>If set to `true`, the `customer` object is required."
},
"pct_tran_fee": {
"type": "number",
"description": "<strong>Format: </strong>Percentage of transaction that will be added as a transaction fee. Transaction fees can be used only if merchant is enabled to use them and if the selected payment supports this particular fee.",
"format": "double"
},
"pct_fee": {
"type": "number",
"description": "<strong>Format: </strong>Variable length, up to 3,2 N<br><strong>Description: </strong>Percentage of the transaction that will be added as a surcharge. A surcharge is a fee added to the cost of a purchase for the privilege of using a credit card instead of another form of payment. Surcharge can be used only if the merchant is enabled to use surcharges and if the selected payment supports a surcharge. ",
"format": "double"
},
"purchase_id": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 25 AN<br><strong>Description: </strong>Purchase identifier (also referred to as the invoice number generated by the merchant) included in the recurring transactions. If not provided, the system generates a purchase identifier based on customer data. Applicable only to one-off subscriptions."
},
"merchant_id": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Identifies the merchant to whom this request applies. Optional field, applicable only if the request is sent on behalf of another merchant.<br><strong>Conditional Requirement: </strong>Required if this request is on behalf of another merchant.",
"format": "int64"
},
"custom_fields": {
"type": "array",
"description": "Custom fields for the subscription.",
"items": {
"$ref": "#/$defs/CustomFields"
}
}
},
"$defs": {
"AddBillingCardRequest": {
"required": [
"billing_zip"
],
"type": "object",
"properties": {
"billing_firm_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Business name, if applicable. <br><strong>Conditional Requirement:</strong> When adding an ACH payment method, the following is required:<br> (a) `tr_number`, `dda_number`, `billing_first_name`, and `billing_last_name`, or<br> (b) `tr_number`, `dda_number`, and `billing_firm_name`."
},
"billing_first_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Billing first name. <br><strong>Conditional Requirement:</strong> When adding an ACH payment method, the following is required:<br> (a) `tr_number`, `dda_number`, `billing_first_name`, and `billing_last_name`, or<br> (b) `tr_number`, `dda_number`, and `billing_firm_name`."
},
"billing_last_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Billing last name. <br><strong>Conditional Requirement:</strong> When adding an ACH payment method, the following is required:<br> (a) `tr_number`, `dda_number`, `billing_first_name`, and `billing_last_name`, or<br> (b) `tr_number`, `dda_number`, and `billing_firm_name`."
},
"card_id": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 32 AN<br><strong>Description: </strong>Card ID received from a tokenization request. `card_id` may be used in place of `card_number` or `card_swipe`. Duplicate cards are not permitted for a customer in the system. The `card_id` should be permanent. If a single-use `card_id` should be used, set the `verify` field to `true`, which makes the `card_id` permanent.<br><strong>Conditional Requirement:</strong> When adding a billing card, the following is required: <br> (a) `card_number`, `exp_date`, and `billing_zip`, or<br> (b) `card_id` and `billing_zip`."
},
"card_number": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>The full card number. When a card is added, it is immediately tokenized, and a `card_id` value is generated and stored in Vault. Duplicate cards are not permitted for a customer in the system.<br><strong>Conditional Requirement:</strong> When adding a billing card, the following is required: <br> (a) `card_number`, `exp_date`, and `billing_zip`, or<br> (b) `card_id` and `billing_zip`."
},
"exp_date": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 4 N, MMYY format<br><strong>Description: </strong>Expiration date of the cardholder's card number.<br><strong>Conditional Requirement:</strong> When adding a billing card, the following is required: <br> (a) `card_number`, `exp_date`, and `billing_zip`, or<br> (b) `card_id` and `billing_zip`."
},
"tr_number": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 9 N<br><strong>Description: </strong>Bank transit/routing number. Applicable for ACH account numbers. <br><strong>Conditional Requirement:</strong> When adding an ACH payment method, the following is required:<br> (a) `tr_number`, `dda_number`, `billing_first_name`, and `billing_last_name`, or<br> (b) `tr_number`, `dda_number`, and `billing_firm_name`."
},
"dda_number": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 17 N<br><strong>Description: </strong>Owner's account number at the bank. Applicable for ACH account numbers. <br><strong>Conditional Requirement:</strong> When adding an ACH payment method, the following is required:<br> (a) `tr_number`, `dda_number`, `billing_first_name`, and `billing_last_name`, or<br> (b) `tr_number`, `dda_number`, and `billing_firm_name`."
},
"billing_addr1": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Billing street address. This address will also be used for AVS verification if AVS verification is enabled. "
},
"billing_addr2": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Billing address line 2."
},
"billing_city": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Billing city."
},
"billing_state": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 3 AN<br><strong>Description: </strong>Billing state."
},
"billing_zip": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 10 AN<br><strong>Description: </strong>Billing zip code. This field will also be used for AVS verification if AVS verification is enabled. <br><strong>Conditional Requirement:</strong> When adding a billing card, the following is required: <br> (a) `card_number`, `exp_date`, and `billing_zip`, or<br> (b) `card_id` and `billing_zip`."
},
"billing_zip4": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 4 N<br><strong>Description: </strong>Billing zip+4 code if applicable."
},
"billing_country": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Billing country."
},
"billing_country_code": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 3 AN<br><strong>Description: </strong>ISO numeric country code for the billing address. Refer to <a href=\"/docs/references\" target=\"_blank\">Country Codes</a> for a list of country codes."
},
"billing_email": {
"type": "array",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>An array of billing email addresses.",
"items": {
"type": "string"
}
},
"cvv2": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 4 N<br><strong>Description: </strong>CVV2 or CID value from the signature panel on the back of the cardholder's card. If present during a request where `verify` is set to `true`, the value will be sent to the issuer for validation. This field is not stored in Customer Vault."
},
"merchant_id": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Identifies the merchant to whom this request applies. Optional field, applicable only if the request is sent on behalf of another merchant.<br><strong>Conditional Requirement: </strong>Required if this request is on behalf of another merchant.",
"format": "int64"
},
"primary": {
"type": "boolean",
"description": "<strong>Description: </strong>Set this field to `true` if this should be the default card. The default card will be used in recurring billing payments.<br><strong>Default: </strong>false"
},
"type_id": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 1 AN<br><strong>Description: </strong>Bank account type. Applicable for ACH account numbers. Possible values: <ul><li>`C` = Personal checking account</li><li>`S` = Personal savings account</li><li>`K` = Business checking account</li><li>`V` = Business savings account</li></ul><p><strong>Default: </strong>C</p>"
},
"verify": {
"type": "boolean",
"description": "<strong>Description: </strong>Set this field to `true` if `card_number` or `card_id` should be verified by the issuer before adding to Customer Vault. When this field is set to `true`, the customer is added to Customer Vault regardless of whether verification succeeds.<br><strong>Default: </strong>false"
}
}
},
"AddCustomerRequest": {
"type": "object",
"properties": {
"customer_id": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Unique customer ID value established by the merchant. The customer ID can be used to add subscriptions through Recurring Billing API requests or make payments through Payment Gateway API requests. Once established, this ID cannot be updated. This field is case sensitive. Only letters and numbers are allowed in a Customer ID.<br><strong>Conditional Requirement: </strong>Either `customer_id` or `auto_generate_customer_id` is required to add a new customer."
},
"auto_generate_customer_id": {
"type": "boolean",
"description": "<strong>Description: </strong>Boolean flag that indicates if the customer ID should be auto-generated. When set to `true`, we generate a unique customer ID, and the generated `customer_id` is returned in the response. Use the returned value to manage the customer profile through Customer Vault API requests. <br><strong>Default: </strong>false<br><strong>Conditional Requirement: </strong>Either `customer_id` or `auto_generate_customer_id` is required to add a new customer."
},
"customer_first_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Customer's first name.<br><strong>Conditional Requirement: </strong>Either customer name or `customer_firm_name` is required."
},
"customer_last_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Customer's last name.<br><strong>Conditional Requirement: </strong>Either customer name or `customer_firm_name` is required."
},
"customer_firm_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Customer business name if applicable. <br><strong>Conditional Requirement: </strong>Either customer name or `customer_firm_name` is required."
},
"customer_phone": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Customer's phone number."
},
"customer_email": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Customer's email address. "
},
"reference_id": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>A merchant-provided value that will be stored with the Customer Vault data for merchant reference."
},
"comments": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Comments."
},
"developer_id": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Used to indicate which company developed the integration, or the name of the solution or system that is connected to us. Suggested usage is `softwareABCv1.0` or `companyXYZv2.0`."
},
"shipping_addresses": {
"type": "array",
"description": "<strong>Description: </strong>An array of shipping addresses. One address should be designated the default shipping address. If it is not, the system selects one address to be the default. ",
"items": {
"$ref": "#/$defs/AddShippingAddressRequest"
}
},
"billing_cards": {
"type": "array",
"description": "<strong>Description: </strong>An array of billing cards. One of the cards should be designated as the default billing card. If it is not, the system selects one of the cards to be the default. ",
"items": {
"$ref": "#/$defs/AddBillingCardRequest"
}
},
"merchant_id": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Identifies the merchant to whom this request applies. Optional field, applicable only if the request is sent on behalf of another merchant.<br><strong>Conditional Requirement: </strong>Required if this request is on behalf of another merchant.",
"format": "int64"
}
}
},
"AddShippingAddressRequest": {
"required": [
"shipping_first_name",
"shipping_last_name"
],
"type": "object",
"properties": {
"shipping_first_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Shipping first name."
},
"shipping_last_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 32 AN<br><strong>Description: </strong>Shipping last name."
},
"shipping_firm_name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Business name of the shipping address, if applicable. "
},
"merchant_id": {
"type": "integer",
"description": "<strong>Format: </strong>Variable length, up to 16 AN<br><strong>Description: </strong>Identifies the merchant to whom this request applies. Optional field, applicable only if the request is sent on behalf of another merchant.<br><strong>Conditional Requirement: </strong>Required if this request is on behalf of another merchant.",
"format": "int64"
},
"primary": {
"type": "boolean",
"description": "<strong>Description: </strong>Set this field to true if this should be the primary address. <br><strong>Default: </strong>false"
},
"shipping_addr1": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Shipping address line 1."
},
"shipping_addr2": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Shipping address line 2."
},
"shipping_city": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>Shipping city."
},
"shipping_state": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 3 AN<br><strong>Description: </strong>Shipping state."
},
"shipping_country": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 128 AN<br><strong>Description: </strong>Shipping country."
},
"shipping_country_code": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 3 AN<br><strong>Description: </strong>ISO numeric country code for the shipping address. Refer to <a href=\"/docs/references\" target=\"_blank\">Country Codes</a> for a list of country codes."
},
"shipping_zip": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 10 AN<br><strong>Description: </strong>Shipping zip code."
},
"shipping_zip4": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 4 N<br><strong>Description: </strong>Shipping zip+4 code, if applicable."
}
}
},
"CustomFields": {
"required": [
"name",
"value"
],
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "<strong>Format: </strong>Variable length, up to 64 AN<br><strong>Description: </strong>The name of the custom field."
},
"value": {
"type": "string",
"description": "<strong>Format: </strong>Fixed length, 128 AN<br><strong>Description: </strong>The value of the custom field."
}
}
}
}
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/qualpay-add-subscription-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.