Authentication
Every request to the Finlogic API is authenticated with your secret key sent as a bearer token.
Bearer tokens
Pass your secret key in the Authorization header of every request:
Request header
Authorization: Bearer sk_live_9a8b7c6d5e4f...
Requests without a valid key return 401 Unauthorized. Requests made over plain HTTP are rejected — the API is HTTPS only.
Environments
| Environment | Key prefix | Behaviour |
|---|---|---|
| Sandbox | sk_test_ | Simulated rails. Transfers auto-complete after ~30 seconds; test webhook events fire normally. |
| Production | sk_live_ | Real money movement on live settlement rails. |
Objects never cross environments — a quote created with a test key cannot be executed with a live key.
Key security
- Store keys in environment variables or a secrets manager, never in source control.
- Use the dashboard's IP allowlist (Settings → API Keys) to restrict which servers may use your live key.
- Rotate keys from the dashboard at any time — the old key keeps working for 24 hours to allow a graceful cutover.
- Scope integrations with restricted keys if a service only needs read access or a single product.
Compromised key? Roll it immediately from the dashboard, then review recent activity under Logs. Contact support if you see transactions you don't recognise.
Idempotency
Network timeouts happen. To retry a POST safely, send an Idempotency-Key header — any unique string (a UUID works well). If we already processed a request with that key, we return the original response instead of creating a duplicate.
cURL
curl https://api.finlogic.com/v1/transfers \
-H "Authorization: Bearer sk_live_..." \
-H "Idempotency-Key: 3f9c2a71-4b0e-4a1c-9e57-1d2f8a6b3c44" \
-H "Content-Type: application/json" \
-d '{ "quote_id": "qt_8f2k1x9d", "beneficiary_id": "bn_71xk2mp0" }'
Idempotency keys are stored for 24 hours.