Authentication
Authentication
Create API keys in your back office. Sign every call.
API keys
Create API keys in your back office. Each key pair is made in your browser. You keep the private key. We keep only the public key.
Each key has:
- a name,
- the environments it may use,
- what it can do: play, manage environments, or read money,
- and the IP addresses it may call from.
Apps
Use one key for each app or server. Then you can turn one off alone.
Signing calls
Every call, both ways, is signed with the sender’s private key. We use ECDSA P-256 with SHA-256.
Each call has four headers.
| Header | What it holds |
|---|---|
Key-Id | Which key signed the call. |
Environment | Which environment the call is for. |
Sent-At | When the call was sent. |
Signature | The signature, made with the sender’s private key. |
A call older than 5 minutes is refused.
Key-Id: key_7Hq2Xc9LpQ
Environment: staging
Sent-At: 2026-10-31T12:20:00Z
Signature: MEUCIQD3…
{ "requestId": "r-01JC9B…",
"firstSentAt": "2026-10-31T12:20:00Z", … }IP addresses
On Live, every key needs its IP addresses.
Changing a key
- 1
Create a new key.
- 2
Move your servers to it.
- 3
Delete the old key.