Skip to main content

Endpoints

This page covers the public integration API: operations an environment-bound API key can call. Dashboard-only and platform-operator routes are intentionally omitted. For request schemas, response status codes, and parameters, use the live OpenAPI 3.1 document.

Idem means an idempotency-key header is mandatory.

Payments​

MethodPathScopeIdem
POST/v1/ordersorders:write✓
GET/v1/orders, /v1/orders/{id}payments:read
POST/v1/payment-intentspayments:write✓
GET/v1/payment-intents, /v1/payment-intents/{id}payments:read
POST/v1/payment-intents/{id}/confirm, /capture, /cancelpayments:write✓
POST/v1/refundsrefunds:write✓
GET/v1/refunds, /v1/refunds/{id}payments:read
GET/v1/route-decisions/{id}, /v1/risk-decisions/{id}payments:read

Sellers, fulfilment, and payouts​

MethodPathScopeIdem
GET, POST/v1/sellerstrust:read / trust:writePOST ✓
GET/v1/sellers/{id}, /{id}/attestations, /{id}/channelstrust:read
POST/v1/sellers/{id}/status, /{id}/attestationstrust:write✓
GET, POST/v1/beneficiariestrust:read / trust:writePOST ✓
GET/v1/beneficiaries/{id}trust:read
GET, POST/v1/beneficiary-changestrust:read / beneficiary_changes:requestPOST ✓
GET/v1/beneficiary-changes/{id}trust:read
POST/v1/beneficiary-changes/{id}/cancelbeneficiary_changes:request✓
GET, POST/v1/fulfillment-sourcestrust:read / trust:writeSee OpenAPI
GET, POST/v1/fulfillment-eventstrust:read / trust:writePOST ✓
GET/v1/fulfillment-events/{id}, /v1/fulfillment-ingestions/{id}trust:read
GET, POST/v1/verified-commerce-envelopestrust:read / trust:writePOST ✓
GET/v1/verified-commerce-envelopes/{id}trust:read
GET, POST/v1/payout-instructionstrust:read / payouts:writePOST ✓
GET/v1/payout-instructions/{id}trust:read
POST/v1/payout-instructions/{id}/cancelpayouts:write✓

Operations requiring an interactive approval—such as approving or releasing a payout—stay in the dashboard and are not part of the integration API.

Cases​

MethodPathScopeIdem
POST/v1/incidentscases:write✓
GET/v1/incidentscases:read
GET/v1/cases/{id}cases:read
POST/v1/cases/{id}/advance, /resolve, /actions, /appeal, /appeal-linkcases:write✓
GET, POST/v1/cases/{id}/evidencecases:read / cases:writePOST ✓
GET/v1/cases/{id}/evidence/{evidenceId}, /contentcases:read
POST/v1/cases/{id}/evidence/{evidenceId}/statuscases:write✓
GET/v1/appeals/{id}cases:read

Read-only operational data​

MethodPathScope
GET/v1/webhook-endpoints, /{id}, /{id}/deliveries, /v1/webhook-inboxwebhooks:read
GET/v1/policies, /templates, /{id}policies:read
GET/v1/insights/funnel, /savings, /savings/{id}, /imports, /imports/{id}insights:read
GET/v1/recon/files, /files/{id}, /exceptions, /exceptions/aging, /exceptions/{id}recon:read
GET/v1/quickstartpayments:read
GET/v1/demo/seedtrust:read

The OpenAPI document is generated from the live route table and is the authoritative operation list. If an operation is absent there, do not build an integration against it.