Changelog

Entries use these labels:

​

2026-09-09 — API 2.3.0

• API Published additive public contract version 2.3.0, including observation-only onchain source registration at POST /v2/onchain-sources, with transaction, bounded address, and provider-payment source identities.
• API Added reviewed Ethereum and Solana stablecoin enrichment for Circle USDC and Paxos USDP, including finality, exact atomic transfers, and unrecognized token activity.
• Docs Added Monitoring stablecoins operations with request examples, lifecycle states, retry behavior, and dashboard guidance.

Onchain enrichment is asynchronous and does not create synthetic events, findings, alerts, targets, or ledger entries. Existing event producers do not need to change unless they choose to register an onchain source.

​

2026-08-30

• API Added additive v2.2.0 capture-only settlement evidence: settlement identities, allocations, revisions, and exact financial breakdowns.
• API Settlement evidence is durable and visible in event reads, but does not create monitoring operations, targets, findings, alerts, transactions, or ledgers.
• Docs Added strict limits and compatibility guidance to the generated v2.2.0 OpenAPI contract. v1 remains frozen.

​

2026-08-24

• API Added optional causation_id to event requests and returned it, alongside correlation_id, on event reads. The additive public contract is version 2.1.0.
• API Causation IDs preserve the producer’s claim about the single earlier event that led to this event; they do not change operation grouping or evaluation.
• Docs Added Causation IDs and the correlation/causation distinction to the cross-service guide.
• SDK The TypeScript and Python SDK repositories can consume the 2.1.0 artifact through their normal contract-sync process; their releases are separate.

The field is additive and optional. Existing integrations need no change.

​

2026-08-21

• API Added optional correlation_id to the POST /v2/events event schema. It accepts 1 to 200 visible ASCII characters and is rejected when null, empty, or whitespace-padded. Senders that previously received unknown_field for this key can now send it.
• API Correlation IDs link evidence for investigation only. Operation grouping, flows, deadlines, and findings are unchanged, and event reads do not return the field.
• Docs Added Correlation IDs and Trace a flow across services.

The field is additive and optional. Existing integrations need no change, and the contract remains version 1.0.0.

​

2026-08-19

• Docs Split integration verification into a delivery guide and a monitoring guide.
• Docs Added symptom-based Troubleshooting, a redacted support-packet template, operational runbooks, and an expanded security boundary.
• Docs Added Postman import guidance that uses the generated OpenAPI artifact instead of a separate collection.
• Docs Expanded the error catalog and contract-checked examples for partial batches, retries, pagination, provider enrichment, and 503 handling.

No public API or SDK behavior changed. The contract remains version 1.0.0.

​

2026-08-11

• SDK Documented @reconifyhq/sdk 1.0.0 and reconify-python 1.0.0.
• Docs Added TypeScript and Python examples alongside cURL.
• Docs Reorganized the portal around sending events, verifying delivery, enriching provider data, and preparing for production.
• Docs Added Integrate with an AI agent with a copy-ready prompt and an AGENTS.md rules file.
• API Published the versioned contract index at /openapi/manifest.json for SDK consumers.
• Docs Corrected examples that omitted required entity_id.

No public API behavior changed. The contract remained version 1.0.0.

​

2026-08-05

• API Added event and issue reads.
• API Added issue assignment and investigation notes.
• API Added read, write, and admin API-key scopes.
• API Added optional note idempotency with Idempotency-Key.
• API Redacted member email addresses from public responses.
• Breaking Removed retired event fields and JWT authentication from public data routes.
• Migration Use organization API keys for public data routes and use only open, resolved, or resolved_late finding statuses.

​

Migration actions

• Use event.id for per-event retry protection.
• Use Idempotency-Key only for note creation.
• Replace JWT authentication on public data routes with an organization API key.
• Replace unsupported finding statuses with open, resolved, or resolved_late.