Yapily vs Yodlee Core API

Yapily

llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.

Yodlee Core API

A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.

Yapily

1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch
2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty
3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation
4. Check the error source field first; USER and INSTITUTION failures won't clear on retry
5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days

Yodlee Core API

1. Get a token with POST /auth/token, sending Api-Version: 1.1 and the end user's loginName as headers and clientId and secret in a form body. Reuse it for up to 30 minutes
2. Use the admin loginName only for administrative calls such as webhook subscriptions. A token made with a user's loginName reads only that user's data
3. In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there
4. Page GET /transactions with skip and top (1 to 500). Without dates it returns the last 30 days, and at most two years with fromDate and toDate
5. A person must link accounts in FastLink 4 first. Then read GET /providerAccounts for link status before GET /accounts
6. Subscribe to DATA_UPDATES or REFRESH webhooks, or poll GET /dataExtracts/events in windows of at most 60 minutes, and do not poll accounts in a loop