Products
Create a product
Creates a product: a name and one fixed price in one currency.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.
Headers
Idempotency-KeystringRequiredA unique value per logical operation, 1-255 chars of
A-Z a-z 0-9 _ . : -.More
Reuse it to retry. Same key with the same body replays the stored response; same key with a different body is a
409, because answering with the first call's result would hand you a receipt for a payout you did not request. A4xxreleases the key, so you can fix the body and reuse it.Reuse it; do not generate one per attempt. A key minted per attempt defeats replay entirely: every retry looks like a new request, so every retry pays. We also watch for an identical body arriving under a different key within 15 minutes and refuse it with
DUPLICATE_REQUEST_DETECTED.Records are kept for 7 days. That is a retention window only: there is no path where an expired key is re-executed.
Body
This endpoint expects a JSON object.
namestringRequireddescriptionstring | nullOptionalimageBase64string | nullOptionaldata:image/png;base64,...orimage/jpeg, at most 700,000 characters (about 500KB). Shown on the payer page.currencystringRequiredAllowed values:USDEURGBPAEDShow 10 more values
MXNBRLARSINRCNYHKDPHPSGDIDRTHBunitAmountstringRequiredMust be above zero.
Behavior
A link made from it copies the name and price at that moment; changing the product later changes nothing about links already made from it (the description and image are read live, so a typo fixed here is fixed on every live page).
(name) is unique among your active products: a second 409s. Archive
the old one to reuse the name. Idempotency-Key is required on an
API key.
Responses
201The product.
Body · CheckoutProduct
idstring<uuid>RequirednamestringRequireddescriptionstring | nullRequiredcurrencystringRequiredunitAmountstringRequiredarchivedAtstring<date-time> | nullRequiredlinkCountintegerRequiredLinks created from it.
createdAtstring<date-time>Required
Errors
400VALIDATION_ERROR(a field is malformed;errorsnames each),BAD_REQUEST(a request we understood but cannot carry out, named indetail: editing a published link, deleting one that was live, bothproductIdanditems),LINK_EXPIRED(publishing a draft whoseexpiresAthas passed), or, on a write,IDEMPOTENCY_KEY_REQUIRED/IDEMPOTENCY_KEY_INVALID(the header is missing or malformed).401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403A valid key that may not make this write. Nothing was changed.
FORBIDDEN: the key belongs to a different organization, or your business has not completed verification to accept payments;detailsays which.ACCOUNT_BLOCKED: API access for your organization is suspended.LIVE_KEY_ORG_NOT_APPROVED: a live key, before we have approved your business verification. Use a test key until then.INSUFFICIENT_SCOPE: a read-only key.
409A product with that name already exists, or the
Idempotency-Keywas reused with a different body.429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?