Changelog
What changed in the Matchai developer documentation and, once it opens, in the Matchai API: new endpoints, changes and deprecations, newest first.
This page lists the changes that matter to people who build on Matchai, newest first. Today it covers the developer documentation. Once the Matchai API opens, it also records every change to the API, including every deprecation, before the change takes effect.
2026-10-20
Developer documentation published; the Matchai API is in design (coming soon)
The developer documentation is public.
Live today
- The MCP server and its public tools, for AI assistants.
- Listing search at
/ask, for plain-language search over published listings. - AI-readable pages:
llms.txt, Markdown copies, structured data and sitemaps on every Matchai host. - The OpenAPI contract of these public endpoints at
https://matchai.co/openapi.json. - The rate limits of these public surfaces.
Coming soon
The Matchai API is in design. It is documented now, in preview, so that partners and developers can plan. Every page and endpoint is marked Coming soon, and none of it works yet.
- The API at
https://api.matchai.co/v1: listings, contacts, conversations, calendar, documents, sites and the Matchai Page. See the API reference. - API keys for your own account, and Connect with Matchai (OAuth 2.1) for apps that serve other professionals.
- Final actions and approvals, so that sending, publishing, paying and deleting ask the account holder first.
- Webhooks, and authenticated tools on the MCP server.
- The error format, rate limit headers and versioning rules the API will follow.
The preview contract can be downloaded at https://matchai.co/docs/openapi/matchai-v1.yaml. Details can still change before the API opens.
How future entries will look
Entries are dated and listed newest first. Under each date, changes are grouped by what happened to you:
| Group | What it holds |
|---|---|
| Added | New endpoints, fields, scopes, event types and tools |
| Changed | Behaviour that changed without breaking a correct integration |
| Deprecated | Something that will be removed, what replaces it, and how to move across |
| Removed | Something that was deprecated earlier and is now gone |
| Fixed | Behaviour that did not match the documentation, now corrected |
A change that can break a correct integration is marked Breaking and is announced under Deprecated before it happens. See versioning for what counts as breaking.
An entry looks like this. The example is not a real change:
## 2027-01-15
### Added
- `GET /v1/…`: what it returns, and the scope it needs.
### Deprecated
- **Breaking, in a later version.** What is retired, what replaces it, and how to move across.