All pages

Developer docs

uetr.ai API

Track international bank transfers by their UETR and read what the banks report about them. Every call acts on one uetr.ai account, with the rights of the user who created the credential. The same actions are tools on the MCP server at https://uetr.ai/mcp.

New here? The quickstart makes a first call in a few minutes.

Base address

https://uetr.ai/api/v1. The OpenAPI document is at https://uetr.ai/openapi.json.

Authentication

Create an API key on the AI and API page of uetr.ai and send it only in the Authorization header as Bearer <key>. A key sent in a URL is revoked at once. AI apps on the MCP server sign in through https://auth.uetr.ai instead and receive their own tokens, and a script can send its API key to the MCP server too. A read key can make the reads its user may make, and changes need a key with read and write access. Some operations are the account owner's alone, as on the website: their pages say so, and a teammate's keys and connected apps cannot call them. More in authentication.

Versions

Versions are dates. A key keeps the version it was created on, and a call can name another known version in the uetr-version header. The current version is 2026-10-14. Breaking changes ship only as a new dated version.

Limits

Calls and changes have per-account limits, listed in rate limits. A refused call carries rate_limited with a Retry-After header and retry_after_seconds in the body. Wait that long, then try again.

Refusals

A refusal is a problem+json body (RFC 9457) with a stable code to act on and a plain-English detail to pass on. Every code is listed on the errors page.

Operations

Transfers

Payment records

Account

Team

Webhooks

Owner confirmation