Skip to content

API reference

Endpoints, request fields, response schemas and generated examples for every Kustom API.

Every operation of every Kustom API is listed on this page, under the API it belongs to. Each has a permanent URL, linkable request and response fields, and examples generated from the OpenAPI specification.

Five things are true of all of them, whichever you pick: the credential to send, how a request and a response are written, what an error body means, what will be refused and how to make a retry safe. Read those once and they hold everywhere.

Checkout API

Create, read, update, and abort Checkout orders/checkout/v3/orders

4 operations

Checkout Callback API

Callbacks Kustom makes to merchant URLs

6 operations

Customer Tokens API

Read tokens, create orders, and manage token status/customer-token/v1/tokens

3 operations

Hosted Payment Page API

Create and distribute hosted payment sessions/hpp/v1/sessions

4 operations

Elements API

Configure Elements clients and allowed origins/elements/v1/clients

9 operations

Shipping Service Callback API

Authentication, shipping options, and shipment reservations

6 operations

Order Management API

Capture, refund, acknowledge, and amend orders/ordermanagement/v1/orders

15 operations

In-Person Payments API

Enrollments, devices, locations, and terminal sessions/ipp/v1

13 operations

Settlements API

Payouts, transactions, and settlement reports

8 operations

Checkout Configuration API

Configure Checkout on behalf of merchants/v1/config

20 operations

Elements Partner API

Manage Elements clients for platform merchants/elements/v1/clients

9 operations

Native Partner Onboarding API

Onboard merchants and request credentials/accountmanagement/v1/merchants

5 operations

Every API is served from one host per environment, and the path decides which API you reach.

EnvironmentHost
Playground (testing)https://api.playground.kustom.co
Productionhttps://api.kustom.co
APIBase path
Checkout/checkout/v3/orders
Checkout callbackyour own URLs
Order Management/ordermanagement/v1/orders
Settlements/settlements/v1
Hosted Payment Page/hpp/v1/sessions
Customer Token/customer-token/v1/tokens
In-Person Payments/ipp/v1
Elements/elements/v1/clients
Shipping Service Callbackyour own URLs
Native partner onboarding/accountmanagement/v1/merchants
Checkout configuration/config/checkout/v1/config

Credentials are environment-specific and never interchangeable. See Authentication and environments for how to get them. Every API in the first table takes the same API credentials, sent as HTTP Basic auth. The partner APIs are the exception: onboarding uses an OAuth 2.0 bearer token from Kustom’s authorization server (getting one), and checkout configuration takes partner credentials rather than a merchant’s.

Give each system its own credentials. One pair works everywhere, but a Merchant ID can carry several, and separate ones cost nothing: your store’s checkout, the job that imports settlements and a support tool each get their own. Then you can rotate or revoke one without breaking the others, and a leak exposes only what that one system does.

This page is also available as Markdown — append .md to its URL — and is indexed in llms.txt.