fire.com
Fire Financial Services provides business payment accounts and related services including bank transfers, debit cards, FX, and open banking payments. Its products let businesses automate payments, reconciliation, and account-based payment acceptance.
fire.com exposes two documented HTTP APIs: the Fire Financial Services Business API for business-account operations and a dedicated Open Banking TPP API at dia-api.fire.com; both require authentication and no GraphQL, MCP, or CLI surface was found.
- Fire Financial Services Business APIdiscovered
- Fire Dedicated Open Banking TPP APIdiscovered
Sign in to Fire Business, open Settings → API, click Add New Application, choose the required permissions, and create the app. Fire then shows three values you must save: Client ID, Client Key, and Refresh Token; the Client Key is only shown once. Use these to mint short-lived bearer access tokens as described in the Authentication guide.
For Fire's dedicated Open Banking API, register a TPP application using dynamic client registration at TPP API documentation. Fire supports DCR at `https://dia-api.fire.com/tpp/register` and uses tls_client_auth; the certificate must match the tls_client_auth_dn in your registration request and be present in your JWKS. The OpenID configuration is published at dia.fire.com generic discovery, with business and personal variants also documented.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing