Skip to main content
Need a key, found something wrong, or want to talk to a human? Keys are self-serve; everything else reaches the team below.

Get an API key

Keys are self-serve. Sign up, verify your email, and your key is active immediately. No card is required, and the Free plan covers the full dataset with a trailing 24 month history window and 2,500 calls a month.

Create your account

app.financialdatapi.com
You can create, rotate and revoke keys from the same dashboard, and upgrade a plan there when you need the full published history or higher limits.
Keys are hashed server-side and are never returned after issue. Store yours securely when you create it. If it is lost or exposed, rotate it from the dashboard.

Get help with the API

For bugs, unexpected responses, or questions about behavior, email the same address. Before you write, the reference and the spec answer most questions.

API reference

Endpoints, parameters, scopes, and the response envelope.

OpenAPI spec

The machine-readable contract. If it is not in the spec, it is not part of the public surface.

Always include the request_id

Every Financial Data API response carries a request_id (mirrored as the top-level requestId, and inside error on failures). It identifies the exact request and lets us trace it server-side, so it is the single most useful thing to send.
When you report an issue, include:
  • The request_id from the affected response.
  • The full request URL (method, path, and query parameters).
  • The HTTP status and the error.code if the call failed.
  • A short note on what you expected versus what you got.
You do not need to paste your API key, and you should not. The request_id is enough for us to find the request.

Response times

We aim to acknowledge access requests and support email within one business day.

Status

For live service health, check the unauthenticated health endpoints. GET /health reports liveness and GET /ready reports readiness; neither requires a key.