celerlinksdevelopers
Celerlinks / Integration guides

Authentication

A secret key connects your server to your Celerlinks account.

Create a key

Open the developer portal, choose an environment, then API keys, and create a key. You can keep up to three keys per environment. Copy a new key when it is created; it will not be displayed again.

Manage API keys
Request headers
Authorization: Bearer YOUR_API_KEY
Accept: application/json

Keep the secret on your server

Store it in an environment variable or secret manager. Never embed it in browser JavaScript, mobile applications, URLs, or source control. New portal keys are stored as hashes. Key lists display only an identifier and usage information.

Rotate without interrupting your integration

  1. Create a replacement key.
  2. Update your server and verify a catalogue request.
  3. Revoke the old key in the portal.

Revocation blocks new requests immediately. Existing in-flight requests can still finish. A revoked key cannot be recovered.

Account access

Keys act on the account that creates them. Live keys are account-wide credentials with access to the supported integration routes. Wallet payments use this account’s balance and require its transaction PIN when one is set. Sandbox keys access only simulated data. Granular scopes are not available.