canonical: https://jentic.com/apis/fire.com/fire

# Fire Financial Services Business API

Fire Financial Services provides a Business Account API for Irish and UK businesses, exposing accounts, transactions, payment batches, debit cards, and Open Banking AISP/PISP operations. The 39-endpoint API covers payment initiation through batches with approval workflows, transaction filtering and reconciliation, debit card issuance and controls, and webhook-driven event notifications. Auth is per-app bearer tokens scoped by permission, suitable for back-office automation, treasury reconciliation, and embedded fintech use cases.

## For AI agents

Manage Fire business accounts, run payment batches with approval flows, issue and control debit cards, and consume webhook events - all under a permissioned bearer token.

## Scope

Does not handle accounting, KYC onboarding, or merchant card acquiring - use for business banking, payment batches, and card management only.

## Capabilities

- List and inspect Fire business accounts and their balances via /v1/accounts
- Create payment batches and add bank-transfer or internal-transfer items before submitting for approval
- Track batch approval state and per-item status through /v1/batches/{batchUuid}/approvals
- Pull and filter transactions with /v1/accounts/{ican}/transactions/filter for reconciliation
- Issue, block, and unblock debit cards via /v1/cards and /v1/cards/{cardId}/block
- Connect to Open Banking ASPSPs through /v1/aspsps for PSD2 account access
- Exchange app credentials for short-lived API access tokens at /v1/apps/accesstokens

## Use cases

### Bulk Supplier Payments

Pay many suppliers in one operation by creating a batch via POST /v1/batches, adding bank-transfer items via /v1/batches/{batchUuid}/banktransfers, and submitting via PUT /v1/batches/{batchUuid}. Multi-approver workflows are enforced server-side, so the agent only orchestrates submission and status polling. Most teams have a working payments runbook within a week.

Example prompt: Create a new batch, add 25 bank transfer items totaling EUR 48,200 from supplier_invoices.csv, submit for approval, and poll status until APPROVED

### Treasury Reconciliation

Pull filtered transactions through /v1/accounts/{ican}/transactions/filter to match against an internal ledger. The filter supports date range, reference, and amount, so a reconciliation agent can pinpoint specific entries without paginating the full feed. Live in 1-2 days against a real account.

Example prompt: GET /v1/accounts/{ican}/transactions/filter with dateRangeFrom=last Monday, search='INV-' and reconcile each match against open invoices in the ERP

### Card Issuance and Fraud Response

Issue debit cards via POST /v1/cards, view card transactions via GET /v1/cards/{cardId}/transactions, and block or unblock cards through dedicated endpoints. The block endpoint applies within seconds, suitable for rule-based or agent-driven fraud responses. Same-day integration for issuance and freeze flows.

Example prompt: When a card transaction matches a fraud rule, call POST /v1/cards/{cardId}/block with reason='SUSPECTED_FRAUD' and notify the cardholder via email

### AI Agent Finance Operations

Use Fire through Jentic so an agent can answer 'What did we pay last week?' or initiate an authorised batch payment under approval rules. Jentic exposes the 39 Fire endpoints as discoverable tools while keeping the bearer token in the vault, suitable for finance copilots inside SMBs and accounting firms. Get started with Jentic One, the self-hosted execution layer

Example prompt: Through Jentic, search 'create a payment batch', load the /v1/batches schema, and execute with batchType=BANK_TRANSFER and currency=EUR

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/accounts | List Fire business accounts |
| GET | /v1/accounts/{ican}/transactions/filter | Filtered transaction list |
| POST | /v1/batches | Create a payment batch |
| PUT | /v1/batches/{batchUuid} | Submit a batch for approval |
| POST | /v1/batches/{batchUuid}/banktransfers | Add a bank transfer to a batch |
| POST | /v1/cards | Issue a new debit card |
| POST | /v1/cards/{cardId}/block | Block a card immediately |
| POST | /v1/apps/accesstokens | Exchange app credentials for an access token |

## Key resources

- **Accounts** — Business accounts and balances for the authenticated profile
- **Transactions** — Per-account transaction listing with filtering by date, reference, and amount
- **Payment Batches** — Multi-payment batches with approval workflows for bank and internal transfers
- **Cards** — Issue, list, block, and unblock debit cards and view their transactions
- **Open Banking** — ASPSP listing and Open Banking integrations
- **API Applications** — Manage API apps and exchange credentials for access tokens

## Why Jentic

- **Setup:** Wiring the Fire Financial Services Business API by hand means exchanging app credentials for a bearer token, spreading calls across 39 banking, batch, and card endpoints, and handling retries yourself. Through Jentic you install once, import Fire from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Fire puts the account id in the URL path (/accounts/{ican}/...), so a rule can pin your agent to one account: it can read that account's transactions and nothing else. You choose the operations it may call, so actions like creating bank transfers or blocking a card are not included unless you add them.
- **Credential handling:** Your Fire credentials are stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment batch' or 'block a card', and Jentic returns the matching Fire operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Finstar API** — Swiss PSD2 open banking API focused on payment initiation and XS2A account access
- **Fintel API** — Adds equity research signals to complement Fire's transactional banking
- **Finnhub API** — Brings market data and fundamentals alongside Fire's banking primitives

## FAQ

### What authentication does the Fire Business API use?

Fire uses HTTP bearer authentication. Apps exchange credentials at POST /v1/apps/accesstokens for a short-lived token, then send it in the Authorization header. Through Jentic, this exchange and the resulting token are managed in the encrypted vault.

### Can I run multi-approver payment batches with the Fire Business API?

Yes. POST /v1/batches creates a batch, /v1/batches/{batchUuid}/banktransfers adds payments, and PUT /v1/batches/{batchUuid} submits for approval. The /v1/batches/{batchUuid}/approvals endpoint exposes the approval state for each required signer.

### What are the rate limits for the Fire Business API?

Fire applies per-application rate limits and returns 429 responses with retry headers when exceeded. Specific limits depend on your contract tier; Jentic surfaces the standard 429 to the agent for back-off handling.

### How do I reconcile transactions through Jentic?

Search Jentic for 'get filtered account transactions', load the /v1/accounts/{ican}/transactions/filter schema, and execute with date range and reference filters. The structured response can be diffed against your ledger directly.

### Can the Fire Business API issue and block debit cards?

Yes. POST /v1/cards issues a new card, POST /v1/cards/{cardId}/block freezes it, and /v1/cards/{cardId}/unblock restores it. /v1/cards/{cardId}/transactions returns per-card spend history.

### Does Fire support Open Banking PSD2 flows?

Yes. The /v1/aspsps endpoint lists supported ASPSPs (banks) for Open Banking integration, and Fire participates as both AISP and PISP under PSD2.

### Can I limit what my agent is allowed to do with the Fire Business API?

Yes. Because you run Jentic One yourself, your own rules decide which Fire operations and credentials the agent may use. Since Fire puts the account id in the URL path, such as /v1/accounts/{ican}/transactions/filter, you can pin the agent to a single account and let it only read that account's transactions. Write actions like POST /v1/batches to create payment batches, POST /v1/batches/{batchUuid}/banktransfers, or POST /v1/cards/{cardId}/block stay out of reach unless you explicitly add them to what the agent is allowed to call.