Use the API when exchange-rate proof work repeats

Automate the same evidence workflow

Use the API when an ERP, internal tool, marketplace, PSP, GRC system, or reconciliation process needs repeatable exchange-rate evidence. The integration should still begin with the business record and the official source/date decision behind it.

Reference rates are inputs. The important output is reusable proof evidence with source attribution, document id, payload hash, signed documents, and public verification.

The repeatable flow

The public API model is dataset-first so web and API users work from the same source/product/periodicity vocabulary.

• Discover valid datasets from the catalog.
• Retrieve reference-rate data when the workflow needs it.
• Open or reuse proof bundles for supported source/date combinations.
• Download ready proof documents after readiness checks pass.
• Verify proof document metadata by document id and payload hash.

What the human reviewer still receives

A technical integration is only useful if the evidence can still be reviewed by a person. Keep the signed proof document with the accounting, tax, audit, reconciliation, or control record that used the rate.

The recipient can inspect the document and use public verification without access to the preparer account or the integration that opened the proof bundle.

What automation does not change

Bulk work means repeating the existing proof workflow consistently. It does not add a separate public source/date lookup before registration, a source-selection rule, compliance approval, or a new product path.

Before registration, a visitor can inspect samples and use the public proof check. After registration, Basic is a real working plan within its current limits; paid plans change volume, history, and performance according to the product catalog.