Skip to content
Banking/open banking

fire.com

Fire Financial Services Business sandbox and mock API

The fire.com API allows you to deeply integrate Business Account features into your application or back-office systems. The API provides read access to your profile, accounts and transactions, event-driven notifications of activity on the account and payment initiation via batches. Each feature has its own HTTP endpoint and every endpoint has its own permission. The API exposes 3 main areas of fun Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
39
Collections
-
Event types
-
Start this simulation
example request
curl https://your-fire.slurry.io/business/v1/accounts \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 39.

  • GET/v1/accounts
  • POST/v1/accounts
  • GET/v1/accounts/{ican}
  • GET/v1/accounts/{ican}/transactions
  • GET/v1/accounts/{ican}/transactions/filter
  • POST/v1/apps
  • POST/v1/apps/accesstokens
  • GET/v1/aspsps
  • GET/v1/batches
  • POST/v1/batches
  • GET/v1/batches/{batchUuid}
  • PUT/v1/batches/{batchUuid}