Revel Systems
Revel Systems is a cloud iPad-based POS for restaurants and retailers. The Revel Open API exposes products, orders, customers, employees, inventory, schedules, and reporting via a REST interface for partner integrations. The API follows Django Tastypie conventions (objects/meta list envelope, field-lookup filtering) and is complemented by an HMAC-signed webhook channel.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Revel Systems the way a machine reads it — 86 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Revel Systems scores 49.5/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Revel Systems
Each block below is one kind of artifact we hold for Revel Systems. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Revel Webhooks
Event-driven webhook channel that delivers POS events (order finalized, customer created/updated, stock changes, menu updates, timesheet changes, integration changes, reward car...
Revel Systems Customers API
Customer records and addresses.
Revel Systems Establishments API
Establishment (location) resources.
Revel Systems Orders API
Order and order-item resources.
Revel Systems Products API
Product catalog and modifier resources.
Revel Systems Scheduling API
Labor scheduling and timesheet resources.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Revel Open API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Revel Systems Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Revel Systems Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Tastypie REST Conventions
List endpoints return an objects array with a meta pagination envelope (total_count, limit, offset, next, previous).
Field-Lookup Filtering
Filter resources with Django-style lookups (e.g. id__lt, created_date__range, name__icontains).
Field Selection and Expansion
Use the fields parameter to limit returned attributes and expand to inline one level of foreign-key relationships.
Batch Retrieval
Retrieve multiple records by ID in a single call using the set/id1;id2;id3 path form.
Signed Webhooks
Real-time event delivery secured with HMAC-SHA1 signatures and per-event-type endpoint registration.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Revel Webhooks
Revel Systems delivers event notifications to partner-registered HTTPS endpoints via webhooks. Each event type is delivered by HTTP POST with a JSON body. Requests carry an HMAC...
ASYNCAPISemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Revel Open Api Context
JSON-LDRevel Webhooks Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 18
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CustomerList
JSON SCHEMACustomer
JSON SCHEMAEstablishmentList
JSON SCHEMAEstablishment
JSON SCHEMAOrderList
JSON SCHEMAOrder
JSON SCHEMAProductList
JSON SCHEMAProduct
JSON SCHEMATimeScheduleList
JSON SCHEMATimeSchedule
JSON SCHEMACustomerEventPayload
JSON SCHEMAIntegrationChangedPayload
JSON SCHEMAMenuUpdatedPayload
JSON SCHEMAOrderFinalizedPayload
JSON SCHEMAPingPayload
JSON SCHEMARewardCardEventPayload
JSON SCHEMAStockStatusPayload
JSON SCHEMATimesheetEventPayload
JSON SCHEMAScroll within the panel for all 18 ·
JSON Structure 18
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Revel Open Api Customer List Structure
JSON STRUCTURERevel Open Api Customer Structure
JSON STRUCTURERevel Open Api Establishment List Structure
JSON STRUCTURERevel Open Api Establishment Structure
JSON STRUCTURERevel Open Api Order List Structure
JSON STRUCTURERevel Open Api Order Structure
JSON STRUCTURERevel Open Api Product List Structure
JSON STRUCTURERevel Open Api Product Structure
JSON STRUCTURERevel Open Api Time Schedule List Structure
JSON STRUCTURERevel Open Api Time Schedule Structure
JSON STRUCTURERevel Webhooks Customer Event Payload Structure
JSON STRUCTURERevel Webhooks Integration Changed Payload Structure
JSON STRUCTURERevel Webhooks Menu Updated Payload Structure
JSON STRUCTURERevel Webhooks Order Finalized Payload Structure
JSON STRUCTURERevel Webhooks Ping Payload Structure
JSON STRUCTURERevel Webhooks Reward Card Event Payload Structure
JSON STRUCTURERevel Webhooks Stock Status Payload Structure
JSON STRUCTURERevel Webhooks Timesheet Event Payload Structure
JSON STRUCTUREScroll within the panel for all 18 ·
Examples 18
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Revel Open Api Order Example
EXAMPLEScroll within the panel for all 18 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Order Synchronization
Sync finalized orders into accounting, ERP, or analytics systems via the Order resource and order.finalized webhook.
Catalog Management
Create and maintain products, modifiers, and combo sets across establishments.
Customer and Loyalty
Sync customer profiles and loyalty/reward data with marketing and CRM platforms.
Labor and Scheduling
Read and write employee shifts and timesheets via TimeSchedule, TimeScheduleRule, and TimeSheetEntry.
Inventory Monitoring
React to stock-status changes in real time via the inout.stock webhook.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Accounting and ERP
Push order and sales data into accounting and ERP systems.
Payments
Establishment-level payment configuration including ACH for US establishments.
Marketing and CRM
Sync customer and loyalty data with marketing platforms.
Resources
Every other property we hold for Revel Systems — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/revel-systems · machine-readable index on apis.io