Skip to main content
The Dash.fi Public API lets you read and act on your account data from your own systems. It’s a REST API that returns JSON and uses API key authentication.

​
Base URL

All endpoints are served under a single base URL:

​
Authentication

The API uses API key authentication via a Bearer token. Send your API key in the Authorization header on every request:

​
Get your API key

Create your key in the Dash.fi dashboard under Settings → Developer → API:
1

Open developer settings

In app.dash.fi, go to Settings → Developer and select the API tab.
2

Generate a key

Under API keys, click Generate. Generating a key requires the API key permission — if you don’t see the button, ask an administrator on your account.
3

Copy it once

The full key is shown only once, right after you generate it. Copy it and store it somewhere safe.
Keep your API key secret — anyone with it can act on your behalf. Never commit it to source control or expose it in client-side code. You can hold one key at a time: if it’s lost or leaked, click Regenerate in the same screen. Regenerating invalidates the previous key immediately, so swap it into your integrations right away.

​
Endpoints

Every endpoint is listed under API Reference, grouped by resource. Each page carries an interactive playground — paste your API key into the Authorization field and send a real request straight from the docs. Start with GET /health to check connectivity and that your credentials are accepted before wiring up anything else.
The Card endpoints require the card management feature to be enabled for your account, and the Account endpoints require account management. Until a feature is enabled, its endpoints return 403 Forbidden. Contact support@dash.fi to request access.
The Account endpoints read and act across every account on your customer, so they also need a customer-scoped API key. An account-scoped key gets a 403 there.

​
Webhooks

Dash.fi can POST events to a URL you own as they happen — for example card.financial_event.v1. Each delivery carries event metadata in headers (X-Outpost-Event-Id, X-Outpost-Topic, X-Outpost-Timestamp, X-Outpost-Signature) and the payload directly in the body, with no envelope. Topics are versioned (<domain>.<event>.v<major>); a breaking change ships as a new topic version, so your subscriptions never shift schema underneath you. Manage subscriptions in the dashboard under Settings → Developer → Webhooks. Webhooks must be enabled for your account first — if the tab is unavailable, contact support@dash.fi to request access.