comecerodocs

Tokens

API tokens: secret (server), trusted and limited (browser).

Endpoints

get/authsList tokenspost/auths/limitedCreate a limited tokenget/auths/optionsList token permission optionspost/auths/secretCreate a secret tokenpost/auths/trustedCreate a test trusted tokenget/auths/{auth_id}Get a tokenpost/auths/{auth_id}Update a tokendelete/auths/{auth_id}Delete a token

Guides that use it

Authentication

The three Comecero API token types, how long each one lasts, how to create a secret token in the dashboard and how a browser gets a limited token.

Account and test mode

Sign up for Comecero, keep test and live tokens and data apart, test payments with test cards for success and decline, and get ready to go live.

Going live

A checklist for moving your Comecero integration from test to live mode. Tokens, gateways, webhooks, test leftovers, error handling and safe payment retries.

Hello World

Build a test checkout in one HTML page. Get a limited token from the browser, create a cart, pay it with a test card and show the result.

Update your account POST

Changes your company and contact details or your alias. Only the fields you send change. `live` and `closed` are set by Comecero and are ignored here. Fires the `account:modified` event. This needs a live token: a test token gets `400` with the code `token_type_mismatch`. Live secret and trusted tokens may call this with the `accounts` update permission.

List tokens GET

Lists the tokens of your account in the mode of the token you call with: a test token lists test tokens, a live token lists live tokens. The list is offset-based. Each token shows a masked `token`, never the full value. To find one token, send the full token in `q`. You get that token, or an empty list. Secret and trusted tokens may call this with the `auths` read permission.