Skip to content

Reconciliation API

Reconciliation is a microservice mesh. Integrators start work through ingestion and apply operator decisions through exception resolve. The engine, loader, reversals service, exception detection and the workers are chained internally and are not partner APIs.

Documentation status

Last verified: 26 Sep 2026. Endpoint inventory: generated endpoint map. Status labels: status vocabulary. Confirm deployed bases with MasteryHive.

Partner entry points

Canonical path list (generated from OpenAPI): Reconciliation partner endpoint map.

Concern How partners use it Status
Start money pipeline POST /v1/ingestion/background IMPLEMENTED
Start asset pipeline POST /v1/ingestion/asset IMPLEMENTED
Resolve exceptions Messaging request channel (primary), or POST /v1/exceptions/resolve (manual / fallback) IMPLEMENTED
Pipeline status GET /v1/loader/pipeline-status/{session_id} when exposed for your programme IMPLEMENTED

Exception resolve transport

In deployed environments the primary resolve trigger is the platform messaging channel. POST /v1/exceptions/resolve remains as a manual testing / fallback HTTP path over the same resolution behaviour. Full request fields, response and errors: Exception resolve contract.

Reading responses: a success status is not always a finished outcome

Route Status What it means What to inspect
POST /v1/ingestion/background, /asset 202 Accepted and started, not finished Follow progress through pipeline status or your agreed notifications
POST /v1/ingestion/background 409 Ingestion is already running for this period detail.active_session, detail.period
POST /v1/exceptions/resolve 200 The request was processed; individual clusters may have failed results (list; empty means nothing matched) and results[].success (boolean) on every entry
GET /v1/loader/pipeline-status/{session_id} 200 Status snapshot, wrapped in data data.overall (pending, in_progress, complete, failed, cancelled) is computed from the ingestion and reversal stages only, so matching can still be running when it reads complete. Check data.stages and data.errors. An unknown session and an unavailable status store both return overall: pending with empty stages

Internal services: do not call

Engine, loader write APIs, workers, dead-letter replay, and exception detection routes are mesh-internal. They are not part of the partner contract and can change without notice. Do not call them from integrator systems. The full classified inventory is available on the Access-protected engineering documentation site.

Asset events

Downstream consumers: asset event contract.

Auth

See Auth and tenancy. Send scope fields on every call, and confirm how authentication is enforced in your environment with MasteryHive.