Create and send a key
Create an account, open Mon compte → Clés API in the member area, and choose the smallest scopes your integration needs. A key is displayed once. Store it in a secret manager and send it only in the HTTP Authorization header.
curl --fail-with-body \
-H "Authorization: Bearer $NAUTILINKS_API_KEY" \
https://nautilinks.co/api/v1/agent/catalogLive and sandbox keys
| Prefix | Purpose | Side effects |
|---|---|---|
sn_test_ | Contract testing and order simulation. | Validates and prices requests but never creates or charges a real order. |
sn_live_ | Production catalog and ordering. | May spend prepaid credit; any card remainder is returned as a URL for human approval. |
Scopes and failures
Read-only catalog and status operations require the read scope. Order creation and webhook mutation require order. Missing or revoked keys return 401; insufficient scope returns 403. Both use the typed error envelope in Nautilinks OpenAPI 3.1.
Never put a key in a URL, prompt, repository, log, or browser bundle. Rotate it from the member area if it may have been exposed.