Revel Systems (BYOK)

Revel Systems (BYOK) — connector documentation

• MCP endpoint: https://byok-revel.connectorbay.com/mcp
• REST API: POST https://byok-revel.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-revel.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Revel Systems Revel API key and secret joined with a colon (KEY:SECRET), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-revel.connectorbay.com/health · Tool schemas: https://byok-revel.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-revel · agent@connectorbay.com

What Revel Systems (BYOK) is for

Revel Systems (BYOK) lets an AI assistant read your own Revel Systems data through the Revel Systems API with a key you supply (Revel API key and secret joined with a colon (KEY:SECRET)). Read-only: 10 tools (list_establishments, list_products, list_product_categories, list_product_classes, list_orders, list_payment_types, list_discounts, list_business_days, list_pos_stations, list_revenue_centers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.revelup.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Revel Systems. Revel Systems and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which locations are in my Revel enterprise?"
• "What active products are in category 12 and what do they sell for?"
• "What categories are on my Revel menu?"
• "What product classes do I use for reporting?"
• "What were my latest closed orders and their totals?"
• "Which payment types can my Revel POS take?"

What it does

• list_establishments: List the Revel locations (establishments) of the enterprise with name, active flag, time zone, phone and brand. Needs an enterprise-level key.
• list_products: List menu products with price, cost, SKU, category, active flag and food, drink or alcohol flags. Filter by category, name, SKU, active or online display.
• list_product_categories: List menu categories with name, parent, sorting and active flag.
• list_product_classes: List product classes (reporting groups such as food or beverage) with parent and active flag.
• list_orders: List orders (newest first by default) with totals only: subtotal, tax, gratuity, discounts, final total, dining option, guest count and whether it is closed or a web order. No customer details are returned.
• list_payment_types: List the payment types set up for the establishment (cash, card, house account and similar) with active flag.
• list_discounts: List configured discounts with name, amount, type, active flag, validity dates and minimum spend.
• list_business_days: List business days (opened and closed fiscal days) per establishment, newest first when ordered by -id.
• list_pos_stations: List POS stations (terminals) with name, active flag, mode, model, last time online and revenue center.
• list_revenue_centers: List revenue centers (cost areas such as dining room or bar) with active flag.

BYOK key

You bring your own Revel Systems Revel API key and secret joined with a colon (KEY:SECRET) (https://developer.revelsystems.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.revelup.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.revelsystems.com/ (the API this connector calls, with a BYOK key)

Live from the Revel Systems API (*.revelup.com) with a BYOK key; documentation: https://developer.revelsystems.com/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Revel Systems. Revel Systems and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Revel Systems account.

Built for: Worldwide. Languages: English.

Revel Systems (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Revel Systems (BYOK) is. Revel Systems (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Revel Systems data: Read your Revel Systems POS locations, menu products, categories, orders, discounts, payment types and stations with your own API key and secret. You bring your own Revel Systems Revel API key and secret joined with a colon (KEY:SECRET); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Revel Systems call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to *.revelup.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Revel Systems rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Revel Systems receives. The request we make on your behalf, including the key and the arguments, under Revel Systems's own terms and privacy policy. Revel Systems acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Revel Systems gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Revel Systems data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Revel Systems (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Revel Systems at any time to end all access.

Children. Revel Systems (BYOK) is a general-audience service operated by the adult using the assistant, under Revel Systems's own age rules.

Changes. We will post changes here with a new effective date.

Revel Systems (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Revel Systems (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Revel Systems (BYOK) provides: Read your Revel Systems POS locations, menu products, categories, orders, discounts, payment types and stations with your own API key and secret. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Revel Systems credentials and only access data you are allowed to access. Revel Systems's terms apply to your use of Revel Systems; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Revel Systems. Revel Systems and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Revel Systems returns, lightly trimmed; it may be incomplete, delayed or changed by Revel Systems. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Revel Systems account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Revel Systems's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Revel Systems may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Revel Systems key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Revel Systems takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-revel

Revel Systems (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-revel.connectorbay.com/mcp
• REST API: https://byok-revel.connectorbay.com/openapi.json
• Live status: https://byok-revel.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Revel Systems (BYOK) never asks for them.