The Xenmark Integration API lets another tool read your review data — what is new in your inbox, which projects you are on, and what is still open on a revision. It is read-only by design, and it is free on every plan, including Free.
Create a Personal API token
Open your profile in Xenmark and go to Account & Security → Connected apps → Connect an app. Choose Personal API token and generate one.
The token is shown once. Paste it into the tool that needs it and nowhere else. Your Xenmark password is never entered into anything outside Xenmark itself.
You can hold up to five tokens, one per tool, and disconnect any of them from the same screen. Disconnecting a token stops that tool immediately.
What the API can read
The API lives at api.xenmark.app and covers the parts of a review worth reading from somewhere else:
- Your identity — your account and organisation.
- Notifications — comments, replies and mentions, newest first, with a cursor so a tool can resume exactly where it left off.
- Projects, drawings and revisions — the projects you are a member of, the drawings in each, and the revisions of each drawing.
- Review data — a summary per revision counting Open, In progress and Closed items, the comments on a revision, and the replies on a comment.
Every row that points at something in Xenmark carries a web_url, so a tool can always send you straight to the drawing or the comment it is describing.
What the API will not do
It is read-only and stays that way. Nothing outside Xenmark can create a comment, change a status, upload a drawing or alter a project through it.
It never returns email addresses, files, billing details or account roles, and it never reaches a project you are not a member of. What you can read through the API is exactly what you can see in the app.
Requests are rate-limited per token — 120 per hour and 20 per minute — which is ample for a notification checker or an assistant, and a natural brake on anything heavier. Exceeding a limit returns a Retry-After header.
Where the documentation lives
Two starting points, depending on how you prefer to work:
- Postman — the whole API as runnable requests, with a Getting Started section covering the token, the variables and your first call. Nothing to install.
- GitHub — the contract itself: the OpenAPI 3.0 specification of every route, the Postman collection, and a changelog tracking each release. Published under Creative Commons Attribution 4.0, so you can copy the schema straight into your own tools.
Both are kept in step with the API. When the contract changes, the version number changes with it and the changelog says what moved.
Both are linked from the Integrations & API page.
Connecting an AI assistant instead
If what you want is to ask an assistant about your reviews rather than write code against the API, the Xenmark MCP server is built on this same API and needs the same token.