Skip to main content
MCP server version: 2.8.0 Breaking changes and deprecations are called out inline. If your integration targets a version older than the one listed here and something no longer works as documented, check for a deprecation note; otherwise contact support.

​
Versioning policy

FaceSign follows a non-breaking-by-default versioning policy for the REST API:
  • Additive changes (new endpoints, new fields on responses, new optional fields on requests) ship without a version bump. Your integration should ignore unknown fields.
  • Breaking changes (field removals, type changes, required-field additions) are rare. When they happen, we:
    • Publish a deprecation notice in this changelog at least 90 days in advance
    • Email the integration contact on your account
    • Maintain the deprecated behavior behind a dated version header for 6 months after the notice
No breaking changes are currently planned for the 1.x line.

​
2026-04-16 · Docs restructure

Documentation
  • Restructured /docs around MCP-first hello-world flow. /docs now redirects to /docs/mcp (Build with AI).
  • Consolidated the full MCP integration guide into a single /docs/mcp page with anchor sections (Quickstart, Supported Clients, Tool Catalog, Recipes, Troubleshooting).
  • Introduced a dedicated Use Cases section (wire transfer, account recovery, anomaly step-up, payment authentication).
  • Moved Concepts (sessions, flows, nodes, reports) under Reference as a single consolidated page.
  • Added /docs/reference/authentication for API-key mechanics and retry guidance. Operational prerequisites live inline on the MCP page.
  • Added /docs/security/audit-evidence covering what’s retained, how to retrieve it, and known gaps.
No API changes in this release.

​
Reporting a docs issue

Spot something inaccurate, outdated, or missing? Email developers@facesign.ai with the page URL and what’s wrong. We triage docs issues weekly.