MCP & Integration API

Build Reconcilia integrations with agent-ready context.

Use Reconcilia MCP to give compatible coding agents reviewed product context, then connect authorized financial data through the Integration API. MCP does not receive API keys or workspace data.

Open Integration API docs Download OpenAPI JSON

Context for coding agents

Tenant-scoped API access

MCP never receives API keys

MCP context

Helps compatible coding agents understand Reconcilia architecture, data flows, lifecycles, and Integration API guardrails. It is informational and does not access customer data.

Integration API

Uses tenant-scoped credentials for supported source-data ingestion and approved read access, with validation, idempotency, and traceable results.

How they work together

From reviewed context to an authorized connector

MCP helps a compatible coding agent understand the integration. The connector communicates directly with the Integration API under your organization’s authorization.

Connect MCP for context

Give the coding agent reviewed guidance about Reconcilia architecture, lifecycles, data flows, and operational boundaries.

Build the API connector

Use the Integration API contract to connect supported bank, ERP, payment-provider, cash-position, and forecast source data.

Keep authorization separate

Store the tenant API key in the connector’s approved secret store. The Integration API owns tenant selection, validation, idempotency, and request outcomes.

Request examples

Validate the source data before it becomes operational

These examples show the main integration shapes: reference data, statement batches, ERP documents, expected cash, forecast inputs, and reconciliation visibility.

curl "https://api.reconcilia.ai/integration/v1/statements/direct" \
  -H "x-api-key: rca_test.example.secret" \
  -H "idempotency-key: direct-json-2026-04-27" \
  -H "content-type: application/json" \
  -d '{
    "bankAccountId": "00000000-0000-0000-0000-000000000000",
    "statementType": "TRANSACTION_BATCH",
    "processingMode": "VALIDATE_ONLY",
    "statementDate": "2026-04-27",
    "currency": "USD",
    "statementReference": "direct-json-2026-04-27",
    "transactions": [{
      "transactionDate": "2026-04-27",
      "amount": "1250.00",
      "direction": "INFLOW",
      "description": "Customer payment",
      "bankTransactionReference": "BNK-001"
    }]
  }'

Coverage

API groups for finance source data

The public contract focuses on the data Reconcilia uses to explain cash positions, classify activity, review exceptions, forecast liquidity, and produce reports with source references and traceable context.

Reference data

GET/POST /integration/v1/entities
GET/PATCH/DELETE /integration/v1/entities/{id}
GET/POST /integration/v1/bank-accounts
GET/PATCH/DELETE /integration/v1/bank-accounts/{id}

Statement ingestion

POST /integration/v1/statements
POST /integration/v1/statements/direct
POST /integration/v1/files
GET /integration/v1/files, /jobs, /logs

Accounting source data

GET/POST /integration/v1/gl/accounts
GET/POST /integration/v1/counterparties
GET/POST /integration/v1/erp-documents
GET/POST /integration/v1/payment-journals

Cash Position and Forecast expected data

POST /integration/v1/cash-position-entries
POST /integration/v1/forecast-inputs

Reconciliation visibility

GET /integration/v1/reconciliation/suggestions
GET /integration/v1/reconciliation/match-groups

Idempotency and replay safety

Use idempotency-key on writes. Statement writes prefer statementReference or externalReference; ERP documents prefer entityId + docType + docNo; Cash Position and Forecast inputs prefer requestReference or external source IDs. The same key with a different body returns 409.

Operational boundaries

Integration API keys are tenant-scoped and separate from app user sessions.
ERP docType=PAYMENT is source data only. It does not move money or initiate transfers.
Cash Position expected-entry ingestion creates planning rows only; it does not execute payments or publish final snapshots.
Forecast input ingestion creates source-owned manual inputs only; it does not publish Forecast versions or change Cash Position.
Reconciliation endpoints are visibility-first. Approval, rejection, reversal, and adjustment APIs are not public yet.
DELETE safely deactivates records where supported; it does not erase financial history.

Planning an MCP or Integration API connection?

Share your source systems, file formats, agent use case, validation needs, and access requirements. We will help define the right integration path.

Discuss integration scope Open Integration API docs