Skip to content
Hypamoon

Point of sale

Revo XEF API docs and access, and how to use it from Claude

Possible, with help from Revo XEF. The API is documented, but you cannot just create a key: access goes through Revo XEF first.

Possible

The Revo XEF API at a glance

From the docs of Revo XEF, checked on 21 November 2026.

Public API docs
Yes.
API documentation
Revo XEF API documentation on api.revo.works
How it signs in
A bearer token. Three headers: the account name as tenant, an account token as Bearer token (created under account management), and an integrator token from Revo.
Access
On request. You ask Revo XEF for access first.
Webhooks
Yes. It can tell your app when something changes. api.revo.works
Revo XEF MCP
Claude connects to Hypamoon through MCP. Once Revo XEF gives you access, your chat writes an adapter for the Revo XEF API, and Claude then works with your Revo XEF data through that same connection. Every change waits for your approval. This is the MCP connection of Hypamoon, not an MCP server made by Revo XEF.

The check

Three questions about the API of Revo XEF, answered from its own docs.

Public API docs
Yes. Public reference for orders, tables, catalogue, customers, reports and webhooks. Read the docs
A key you create yourself
No. You create an account token yourself, but every call also needs an integrator token that Revo issues after you submit its API request form. api.revo.works
Versions or a changelog
Yes. Versions in the path (v2, v3 for reports) and an API changelog kept since October 2024. api.revo.works
Hosting
Cloud
Condition
API access starts with the request form; Revo validates it and then contacts you.

What you can build

Read sales, tables and the catalogue from Revo XEF for your own reports, and create orders from your own ordering page, once Revo gives you an integrator token.

Your chat writes it as a Hypamoon adapter from the docs above. Reading starts after you click Allow in the portal, and every write waits for your approval, one call at a time. How adapters work

Good to know

  • Your adapter uses a fixed key: you paste it once in the Hypamoon portal, never in the chat, and it only goes to the API host you allow.
  • The limit is 120 requests per minute and 2 MB per request.

Try it in your chat

First get access from Revo XEF. Then fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for Revo XEF. API docs: https://api.revo.works/sections/xef.html. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 21 November 2026.

Revo XEF is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Revo XEF. Found something that changed? Tell us at support.

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect Revo XEF?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot