Skip to content
Banking/open banking

yodlee.com

Yodlee Core APIs sandbox and mock API

This file describes the Yodlee Platform APIs using the swagger notation. You can use this swagger file to generate client side SDKs to the Yodlee Platform APIs for many different programming languages. Yodlee supports the Java SDK and it is available <a href="https://developer.yodlee.com/java-sdk-overview ">here</a>. You can generate a client SDK for Python, Java, JavaScript, PHP or other language Writes persist, data moves on a schedule and every change can fire a signed webhook.

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

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

  • GET/accounts
  • POST/accounts
  • POST/accounts/evaluateAddress
  • GET/accounts/historicalBalances
  • GET/accounts/{accountId}
  • PUT/accounts/{accountId}
  • DELETE/accounts/{accountId}
  • GET/auth/apiKey
  • POST/auth/apiKey
  • DELETE/auth/apiKey/{key}
  • POST/auth/token
  • DELETE/auth/token
Yodlee Core APIs sandbox and mock API | Slurry