Skip to content
Banking/open banking

biapi.pro

Budgea API Documentation sandbox and mock API

# Budgea Development Guides Welcome to **Budgea**'s documentation. This documentation is intended to get you up-and-running with our APIs and advise on the implementation of some regulatory aspects of your application, following the DSP2's guidelines. ## Getting Started **IMPORTANT** Depending on your status with regard of the DSP2 regulation, **agent** or **partner**, you may call our APIs or sim Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
167
Collections
-
Event types
-
Start this simulation
example request
curl https://your-biapi-pro.slurry.io/2.0/account_types \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.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 167.

  • GET/account_types
  • GET/account_types/{id_account_type}
  • POST/admin/jwt
  • POST/auth/init
  • POST/auth/jwt
  • POST/auth/renew
  • POST/auth/token
  • DELETE/auth/token
  • POST/auth/token/access
  • GET/auth/token/code
  • GET/banks
  • POST/banks/categories