Home › Developer portal › Versions and changelog
Document menu← Home
Developer portal
  1. Quick start
  2. Authentication
  3. REST API reference
  4. Webhooks guide
  5. Exports guide
  6. ERP integration guide
  7. Bank integration guide
  8. Tauraco Collateral documentation
  9. MCP documentation
  10. Code samples
  11. Error handling
  12. Sandbox environments
  13. Versions and changelog
  14. FAQ
  15. Developer support
Developers

Versions and changelog

Versioning policy

  • Versioned path: /public/v1. A breaking change would give a new path version; v1 would stay served during the transition.
  • Version date: Tauraco-Version header (today 2026-11-01), optional in requests, always returned.
  • Compatible additions without notice: a new response field, a new event, a new optional filter, a new error code. Your code must ignore unknown fields.
  • Withdrawals: announced with Deprecation, Sunset and Link: <…>; rel="deprecation" on the operation concerned, and in this changelog.
  • API version: 1.0.0-beta until the beta closes.

Surface status

Statuses on 2026-11-06, in the sense of the delivery report: "developed and tested" (code and green tests), "deployed and reachable" (production address checked on 2026-11-05, or on 2026-11-06 for the names under tauraco.ai), "developed but not deployed", "partially implemented", "blocked by a dependency", "not started". The production release took place on 2026-11-05.

SurfaceStatusStill to do
Exports (application)developed and tested; module opened in production on 2026-11-05end-to-end check in production, to come
Webhooks v2developed and tested; module opened in production on 2026-11-05end-to-end check in production, to come
OAuth 2.0deployed and reachable (2026-11-05): metadata, JWKS, /oauth/token, /oauth/registerfirst authenticated call to be checked in production
Public API /public/v1deployed and reachable (2026-11-05): OpenAPI served (73 operations), 401 without a tokenfirst authenticated call to be checked in production
Bank API /public/v1/bankdeployed and reachable (2026-11-05): 401 without a token; legal notices validatedconnecting an institution; no real institution connected
MCP server /mcpdeployed and reachable (2026-11-05): 401 with resource_metadata without a token, also under mcp.tauraco.io and, since 2026-11-06, under mcp.tauraco.aireal Claude.ai connector: blocked by a dependency (test to be done)
Connectorsdeveloped and tested against simulated servers; module opened in production on 2026-11-05no connector tested against a real vendor environment
Developer portaldeployed and reachable (2026-11-05) under docs.tauraco.ai, docs.tauraco.io and developers.tauraco.io; under developers.tauraco.ai since 2026-11-06nothing
Sandboxdeveloped but not deployed (built, never launched)launch by the operator
api.tauraco.ai, mcp.tauraco.ai, developers.tauraco.ai namesdeployed and reachable (2026-11-06): api.tauraco.ai redirects (308) to api.tauraco.io, mcp.tauraco.ai serves the MCP server (401 without a token), developers.tauraco.ai redirects to this portalnothing

Changelog

2026-11-06: dedicated names under tauraco.ai

  • https://mcp.tauraco.ai/mcp is online: same MCP server as https://api.tauraco.io/mcp, same 401 answer with resource_metadata without a token; the resource identity stays https://api.tauraco.io/mcp.
  • https://developers.tauraco.ai redirects to this portal.
  • https://api.tauraco.ai redirects (308, path, method and body kept) to https://api.tauraco.io, which stays the canonical API address and the token issuer.

2026-11-05: production release

  • The public API, the bank API, the OAuth authorization server (dynamic registration included), the MCP server, exports, v2 webhooks and connectors are open in production. Canonical addresses under https://api.tauraco.io; see Surfaces and addresses.
  • Aliases online: https://mcp.tauraco.io/mcp (same resource as https://api.tauraco.io/mcp) and https://developers.tauraco.io (redirects to this portal). The api.tauraco.ai, mcp.tauraco.ai and developers.tauraco.ai names followed on 2026-11-06.
  • Legal notices of the bank API validated.
  • The sandbox is still to come.

2026-11-05 — sandbox built, test scenarios, alignments

  • Sandbox built (isolated stack, fictitious data, demo webhook receiver) but not launched yet: see Sandbox environments.
  • Sixteen end-to-end test scenarios (exports, isolation between companies, scopes, bank, revocation, MCP, connectors, private documents, formula injection, OpenAPI conformance, migrations).
  • Odoo: pushing partners and invoices as drafts only; no pull in v1.
  • MCP: tauraco_get_financing_status returns the same not_found refusal for a missing request and for another company's request.
  • French summaries of the financial institution operations (/bank/*) in the OpenAPI file; no path or schema changed.

2026-11-04 — OpenAPI specification and Postman collection

  • OpenAPI 3.1 file of the public API (73 operations, version 1.0.0-beta) exported from the application, and a Postman collection generated from that file, downloadable from the REST API reference. The financial institution operations (/bank/*) are included (bank API, lot 2C).

2026-11-03 — developer portal (beta)

  • First publication of the developer portal, in French and English: sixteen pages, cURL, Python, TypeScript, Java and C# samples.
  • Interactive reference served locally (Scalar 1.76.4, no third-party script or font).
  • Documentation of the 31 scopes, the 24 error codes, the 13 webhook events, the 24 datasets and the 8 export formats.

2026-11-01 — API version 1.0.0-beta (in development)

  • Scope: about 40 REST operations, OAuth client_credentials and authorization_code with PKCE, signed v2 webhooks, read-only MCP server, read bank API with additional-information requests and reconciliation.

Outside version 1

ItemReason
Bank decisions through the API (offer, decline, disbursement, discharge, release)human actions of a decision-maker; no automatic decision
MCP writes other than requesting an exportno per-call confirmation or agent mandate in v1
Inventory and accounting writes through the APIno ready idempotent and audited writer, risk on entry chaining
/projects, /contracts, /applications, /guaranteesno entity, or a relay to build with the ecosystem
invoice.updated, tender.published, guarantee.status_changedno single emitter, or no event infrastructure in the ecosystem
Native SAP, Dynamics 365, Oracle, PeopleSoft, NetSuite, Cegid, Xero, Sage X3, Sage API (Accounting, Intacct, Active) connectorsneither developed nor tested: documented fact sheets only
Pulling from Odoomethod prepared, not exposed in v1
UBL, Factur-X Schematron validation, ISO 20022 compliancebeta or experimental formats, no compliance claimed
mTLS, DPoP, FAPIrequire a dedicated host name
Client ID Metadata Documents (CIMD)dynamic registration is enough in v1