MX Platform API vs Yodlee Core API

MX Platform API

Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and Deprecation and Sunset response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.

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.

MX Platform API

1. Send Accept: application/json, Accept-Version: v20260929 and Basic auth of client_id:api_key on every call. A missing version returns 406
2. Ask the owner to allowlist the calling machine's static IP in the Client Dashboard first. Other addresses get 403, and some failed authentication returns 404
3. Test against https://int-api.mx.com with institution mxbank, username mxuser and any password. It has no aggregation throttle
4. Set your own id when creating users and members. A repeat returns 409, which makes a retried create safe
5. Expect 202 without an error when a standard aggregation is throttled (three hours by default). Balance checks stop at 5 per member every 2 hours with 429
6. Pass includes[]=merchant or includes[]=category as an array on transaction lists. A comma-separated string returns 400

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