Authentication

The Partner API uses an API key to authenticate requests. Your API key is issued during onboarding by Fintegence Support.

Environments

Environment	Base URL	Purpose
Staging	`https://<STAGING_URL>`	Integration and testing. Blockchain operations use test networks.
Production	`https://api.fintegence.io`	Live operations with real funds.

Staging and production use separate API keys. A staging key does not work in production and vice versa.

API key

Include the API key in the x-api-key header of every request:

Request format

All requests must be sent over HTTPS.

Request and response bodies use JSON. Send Content-Type: application/json with every request that has a body.

All amounts are sent and returned as strings (e.g. "10.5") to avoid floating-point precision issues.

The API version is part of the path (/v1/...).

Use endpoint paths exactly as documented - some include the /partner segment (e.g. /v1/partner/balances) and some do not (e.g. /v1/exchange/rates).

Test your connection

The simplest way to verify your API key is to call Get Balances:

A successful response returns HTTP 200 with the list of your balances. If you receive HTTP 401, see Troubleshooting below.

IP whitelisting

In production, requests are accepted only from IP addresses registered for your account. Before going live, send the list of your production server IP addresses to support@fintegence.com. Requests from other IP addresses are rejected with HTTP 401, even with a valid API key.

If your server IP addresses change (e.g. after migrating your infrastructure), update the list with Support in advance to avoid interruptions.

Troubleshooting

Problem	Possible cause
`401` on every request	The `x-api-key` header is missing or misspelled, or the key contains extra spaces.
`401` with a key that works on staging	Staging and production keys are separate. Use the production key.
`401` in production only	The request comes from an IP address that is not whitelisted.

Keeping your API key secure

Use the API key only in server-side code. Never expose it in frontend applications, mobile apps or public repositories.

Store the key in a secrets manager or environment variables, not in source code.

Restrict access to the key to the people and systems that need it.

If you suspect that your key has been compromised, contact support@fintegence.com immediately to revoke it and issue a new one.

Environments#

API key#

Request format#

Test your connection#

IP whitelisting#

Troubleshooting#