Enable Banking vs MX Platform API

Enable Banking

Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.

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.

Enable Banking

1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions
2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours
3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner
4. On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap
5. Follow continuation_key until it's absent to get every transaction

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