Authentication - Enso Developer Documentation

Obtain API Key

Create an API key in the Enso Developer Portal.
Store it in an environment variable. Never commit the key to source control.

Authenticate requests

Pass your API key using either:

The Authorization: Bearer <API_KEY> header.
The apikey=<API_KEY> query parameter.

Test your API key

Use the authenticated account endpoint to verify the key without building a transaction:

Authorization header
Query parameter

curl \
  -H "Authorization: Bearer $ENSO_API_KEY" \
  "https://api.enso.build/api/v1/account/accountId"

curl \
  "https://api.enso.build/api/v1/account/accountId?apikey=$ENSO_API_KEY"

Next, choose between the Route API and Bundle API.

Rate Limiting

API calls are limited to 10 RPS (600 requests per minute). It can be increased on demand. If you exceed the limit, you’ll receive a 429 Too Many Requests error. If your monthly API credits quota is exceeded, requests also return 429 Too Many Requests. Rate limit and quota errors include a portalUrl field that points to the Developer Portal for key management and plan upgrades.

Auth Errors

Invalid API keys return 401 Unauthorized with error: "invalid_api_key". Retired legacy keys return 401 Unauthorized with error: "legacy_key_retired". Both responses include a portalUrl field so clients can direct users to create or recover an API key in the Developer Portal.

Updated

​Obtain API Key

​Authenticate requests

​Test your API key

​Rate Limiting

​Auth Errors

Obtain API Key

Authenticate requests

Test your API key

Rate Limiting

Auth Errors