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 theAuthorization 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 at a glance
Cards
The Card endpoints require the card management feature to be enabled for your account. Until it’s enabled, these endpoints return
403 Forbidden. Contact support@dash.fi to request access.Financial
Health
Use
GET /health to verify connectivity and that your credentials are accepted before wiring up other calls.
Webhooks
Dash.fi can POST events to a URL you own as they happen — for examplecard.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.