Customers
The people who buy: contact details, saved payment methods, store credit and history.
Endpoints
Guides that use it
API endpoint and requests
The base URL of the Comecero API, why every call must use HTTPS, and the headers and JSON body format that every request and response uses.
Lists and pagination
How Comecero API lists return pages of up to 100 items, the difference between offset and cursor lists, and how to sort them and filter them by date.
Partial updates
How to update a Comecero object with a POST that holds only the fields you want to change, how null clears a field and which fields are replaced whole.
Accept payments
Build a checkout with the API. Create a cart, take a card, PayPal or Apple Pay payment, handle 3-D Secure and declines, and capture or void later.
Refunds
Give money back with the API. Refund a whole order or part of it by amount or items, refund one payment, refund to store credit and follow the refund events.
Subscriptions
Sell a subscription with a plan and a cart, follow renewals with webhooks, change items with proration, cancel, retry failed payments and handle grace periods.
Create a download POST
Makes a new download link to a file, for example to send a customer a file by hand. Comecero makes these on its own for each order item whose product has a file. The link's limits come from the file unless you send your own. The body is JSON and may be an empty object. The token needs the create permission on downloads. Secret and trusted tokens may call it.
List customers GET
Lists the customers of your account, oldest first. Search with `q` and filter by date or by whether the customer has paid. The list is cursor-based: follow `next_page_url`, or send `after_item` or `before_item`. It does not take `sort_by`; use `date_type` with `desc`. Secret tokens only. A limited token cannot list customers.