Skip to main content
Every request to the eBRC API authenticates with a single header over HTTPS:

Getting a key

  • Keys are issued per environment, shown once at issue, and never stored in a readable form: keep yours somewhere safe.
  • Create your account in the eBRC API console and request access there; issued keys appear in the console, where you can view and copy them.
  • Production keys work after the NDA and production agreement, both e-signed in the console.
  • Help, or a key reissue: amin@eximfiles.io.
Keep API keys server side. Never embed them in client-side code or commit them to version control.

Authentication errors

These are the exact responses the API returns: The error body follows the standard error shape.

Rate limits

Limits are applied per API key (per client IP when unauthenticated) over a 60 second window: When a limit is exceeded the API returns 429 with the message Too many requests. Please try again later. The API does not currently send rate limit headers, so back off and retry after a short delay rather than reading headers.

Free general use

The API is free for general use: the rate limits above, plus a published allowance of 250 production certificates a month and 10 exporter entities, with sandbox not metered. The full definition and the quote path for volume live on the Pricing page.