Fire Financial Services Business API

Name: Fire Financial Services Business API
Brand: Fire Financial Services Business API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer39 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Fire Financial Services Business API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fire Financial Services Business API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Fire Financial Services Business API.

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

GET STARTED

Start building with Fire Financial Services Business API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Fire Financial Services Business API for, with concrete tasks.

★ 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.

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.

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.

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

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

Key Endpoints

39 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Fire Financial Services Business API through Jentic.

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.

Fire Financial Services Business API

Connect the Fire Financial Services Business API to your agent

Capabilities

Start building with Fire Financial Services Business API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs