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.
Revel Systems is listed with 7 APIs on the APIs.io network, including Revel Webhooks, Customers API, Establishments API, and 4 more. Tagged areas include Point-of-Sale, Restaurant, Retail, and iPad.
The Revel Systems catalog on APIs.io includes 1 event-driven AsyncAPI specification, 2 JSON-LD contexts, and 3 Spectral governance rulesets.
Revel Systems’ developer surface includes authentication, FAQ, engineering blog, and 11 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/revel-systems/"><img src="https://apis.io/badge/revel-systems/card.svg" alt="Revel Systems on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
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...
aid: revel-systems
url: https://raw.githubusercontent.com/api-evangelist/revel-systems/refs/heads/main/apis.yml
name: Revel Systems
kind: company
description: 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.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: medium
source:
- plans
- authentication
- security
generated: '2026-11-02'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/revel-systems.png
tags:
- Point-of-Sale
- Restaurant
- Retail
- iPad
tags_raw:
- POS
- Restaurant
- Retail
- iPad
created: '2026-05-08'
modified: '2026-06-03'
specificationVersion: '0.23'
apis:
- aid: revel:webhooks
name: Revel Webhooks
description: Event-driven webhook channel that delivers POS events (order finalized, customer created/updated, stock changes,
menu updates, timesheet changes, integration changes, reward cards, and ping) to partner HTTPS endpoints via POST. Payloads
are signed with an HMAC-SHA1 X-Revel-Signature header.
humanURL: https://developer.revelsystems.com/revelsystems/docs/webhooks
tags:
- Webhook
- Event
- Point-of-Sale
tags_raw:
- Webhooks
- Events
- POS
properties:
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/docs/webhooks
- type: AsyncAPI
url: asyncapi/revel-webhooks-asyncapi.yml
- type: JSONSchema
url: json-schema/revel-webhooks-order-finalized-payload-schema.json
title: Order Finalized Payload
- type: JSONSchema
url: json-schema/revel-webhooks-customer-event-payload-schema.json
title: Customer Event Payload
- type: JSONSchema
url: json-schema/revel-webhooks-stock-status-payload-schema.json
title: Stock Status Payload
- type: JSONLD
url: json-ld/revel-webhooks-context.jsonld
- type: Examples
url: examples/revel-webhooks-order-finalized-payload-example.json
title: Order Finalized Example
- aid: revel-systems:revel-systems-customers-api
name: Revel Systems Customers API
description: Customer records and addresses.
humanURL: https://developer.revelsystems.com/revelsystems/reference/welcome
baseURL: https://yoursubdomain.revelup.com/resources
tags:
- Customers
properties:
- type: OpenAPI
url: openapi/revel-systems-customers-api-openapi.yml
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/reference/welcome
- type: APIReference
url: https://developer.revelsystems.com/revelsystems/reference
- type: GettingStarted
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: ChangeLog
url: https://developer.revelsystems.com/revelsystems/changelog/welcome-to-revelsystems
- type: JSONSchema
url: json-schema/revel-open-api-order-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-product-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-customer-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-establishment-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-time-schedule-schema.json
- type: JSONStructure
url: json-structure/revel-open-api-order-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-product-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-customer-structure.json
- type: JSONLD
url: json-ld/revel-open-api-context.jsonld
- type: Examples
url: examples/revel-open-api-order-example.json
- type: Examples
url: examples/revel-open-api-product-example.json
- type: Examples
url: examples/revel-open-api-customer-example.json
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- aid: revel-systems:revel-systems-establishments-api
name: Revel Systems Establishments API
description: Establishment (location) resources.
humanURL: https://developer.revelsystems.com/revelsystems/reference/welcome
baseURL: https://yoursubdomain.revelup.com/resources
tags:
- Establishments
properties:
- type: OpenAPI
url: openapi/revel-systems-establishments-api-openapi.yml
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/reference/welcome
- type: APIReference
url: https://developer.revelsystems.com/revelsystems/reference
- type: GettingStarted
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: ChangeLog
url: https://developer.revelsystems.com/revelsystems/changelog/welcome-to-revelsystems
- type: JSONSchema
url: json-schema/revel-open-api-order-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-product-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-customer-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-establishment-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-time-schedule-schema.json
- type: JSONStructure
url: json-structure/revel-open-api-order-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-product-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-customer-structure.json
- type: JSONLD
url: json-ld/revel-open-api-context.jsonld
- type: Examples
url: examples/revel-open-api-order-example.json
- type: Examples
url: examples/revel-open-api-product-example.json
- type: Examples
url: examples/revel-open-api-customer-example.json
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- aid: revel-systems:revel-systems-orders-api
name: Revel Systems Orders API
description: Order and order-item resources.
humanURL: https://developer.revelsystems.com/revelsystems/reference/welcome
baseURL: https://yoursubdomain.revelup.com/resources
tags:
- Order
tags_raw:
- Orders
properties:
- type: OpenAPI
url: openapi/revel-systems-orders-api-openapi.yml
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/reference/welcome
- type: APIReference
url: https://developer.revelsystems.com/revelsystems/reference
- type: GettingStarted
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: ChangeLog
url: https://developer.revelsystems.com/revelsystems/changelog/welcome-to-revelsystems
- type: JSONSchema
url: json-schema/revel-open-api-order-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-product-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-customer-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-establishment-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-time-schedule-schema.json
- type: JSONStructure
url: json-structure/revel-open-api-order-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-product-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-customer-structure.json
- type: JSONLD
url: json-ld/revel-open-api-context.jsonld
- type: Examples
url: examples/revel-open-api-order-example.json
- type: Examples
url: examples/revel-open-api-product-example.json
- type: Examples
url: examples/revel-open-api-customer-example.json
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- aid: revel-systems:revel-systems-products-api
name: Revel Systems Products API
description: Product catalog and modifier resources.
humanURL: https://developer.revelsystems.com/revelsystems/reference/welcome
baseURL: https://yoursubdomain.revelup.com/resources
tags:
- Product
tags_raw:
- Products
properties:
- type: OpenAPI
url: openapi/revel-systems-products-api-openapi.yml
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/reference/welcome
- type: APIReference
url: https://developer.revelsystems.com/revelsystems/reference
- type: GettingStarted
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: ChangeLog
url: https://developer.revelsystems.com/revelsystems/changelog/welcome-to-revelsystems
- type: JSONSchema
url: json-schema/revel-open-api-order-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-product-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-customer-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-establishment-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-time-schedule-schema.json
- type: JSONStructure
url: json-structure/revel-open-api-order-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-product-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-customer-structure.json
- type: JSONLD
url: json-ld/revel-open-api-context.jsonld
- type: Examples
url: examples/revel-open-api-order-example.json
- type: Examples
url: examples/revel-open-api-product-example.json
- type: Examples
url: examples/revel-open-api-customer-example.json
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- aid: revel-systems:revel-systems-scheduling-api
name: Revel Systems Scheduling API
description: Labor scheduling and timesheet resources.
humanURL: https://developer.revelsystems.com/revelsystems/reference/welcome
baseURL: https://yoursubdomain.revelup.com/resources
tags:
- Scheduling
properties:
- type: OpenAPI
url: openapi/revel-systems-scheduling-api-openapi.yml
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/reference/welcome
- type: APIReference
url: https://developer.revelsystems.com/revelsystems/reference
- type: GettingStarted
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/how-to-make-an-api-call
- type: ChangeLog
url: https://developer.revelsystems.com/revelsystems/changelog/welcome-to-revelsystems
- type: JSONSchema
url: json-schema/revel-open-api-order-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-product-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-customer-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-establishment-schema.json
- type: JSONSchema
url: json-schema/revel-open-api-time-schedule-schema.json
- type: JSONStructure
url: json-structure/revel-open-api-order-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-product-structure.json
- type: JSONStructure
url: json-structure/revel-open-api-customer-structure.json
- type: JSONLD
url: json-ld/revel-open-api-context.jsonld
- type: Examples
url: examples/revel-open-api-order-example.json
- type: Examples
url: examples/revel-open-api-product-example.json
- type: Examples
url: examples/revel-open-api-customer-example.json
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- aid: revel-systems:revel-api
name: Revel Systems API
description: REST API for the Revel Systems iPad POS platform, covering orders, payments, products, inventory, customers,
employees, scheduling, cash management, discounts, tax, tables, purchase orders, house accounts, and web orders. Approximately
140 public endpoints return JSON responses and support GET, POST, PUT, PATCH, and DELETE methods.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
baseURL: https://[yoursubdomain].revelup.com/resources/
humanURL: https://developer.revelsystems.com/
overlays: []
contact:
- FN: Revel Systems Developer Support
url: https://support.revelsystems.com/
tags:
- Point-of-Sale
- Order
- Payments
- Inventory
- Loyalty
- Restaurant
- Retail
tags_raw:
- POS
- Orders
- Payments
- Inventory
- Loyalty
- Restaurant
- Retail
properties:
- type: Documentation
url: https://developer.revelsystems.com/revelsystems/docs/rest-api
- type: Authentication
url: https://developer.revelsystems.com/revelsystems/docs/api-platform-authentication
common:
- type: AgenticAccess
url: agentic-access/revel-systems-agentic-access.yml
- type: DomainSecurity
url: security/revel-systems-domain-security.yml
- type: Authentication
url: authentication/revel-systems-authentication.yml
- type: GitHubOrganization
url: https://github.com/RevelSystems
- type: LinkedIn
url: https://www.linkedin.com/company/revel-systems
- type: Website
url: https://revelsystems.com/
- type: Developer
url: https://developer.revelsystems.com/
- type: FAQ
url: https://developer.revelsystems.com/revelsystems/docs/frequently-asked-questions
- type: SpectralRules
url: rules/revel-systems-rules.yml
- type: Vocabulary
url: vocabulary/revel-systems-vocabulary.yml
- type: Plans
url: plans/revel-systems-plans-pricing.yml
- type: RateLimits
url: rate-limits/revel-systems-rate-limits.yml
- type: FinOps
url: finops/revel-systems-finops.yml
- type: Features
data:
- name: Tastypie REST Conventions
description: List endpoints return an objects array with a meta pagination envelope (total_count, limit, offset, next,
previous).
- name: Field-Lookup Filtering
description: Filter resources with Django-style lookups (e.g. id__lt, created_date__range, name__icontains).
- name: Field Selection and Expansion
description: Use the fields parameter to limit returned attributes and expand to inline one level of foreign-key relationships.
- name: Batch Retrieval
description: Retrieve multiple records by ID in a single call using the set/id1;id2;id3 path form.
- name: Signed Webhooks
description: Real-time event delivery secured with HMAC-SHA1 signatures and per-event-type endpoint registration.
- type: UseCases
data:
- name: Order Synchronization
description: Sync finalized orders into accounting, ERP, or analytics systems via the Order resource and order.finalized
webhook.
- name: Catalog Management
description: Create and maintain products, modifiers, and combo sets across establishments.
- name: Customer and Loyalty
description: Sync customer profiles and loyalty/reward data with marketing and CRM platforms.
- name: Labor and Scheduling
description: Read and write employee shifts and timesheets via TimeSchedule, TimeScheduleRule, and TimeSheetEntry.
- name: Inventory Monitoring
description: React to stock-status changes in real time via the inout.stock webhook.
- type: Integrations
data:
- name: Accounting and ERP
description: Push order and sales data into accounting and ERP systems.
- name: Payments
description: Establishment-level payment configuration including ACH for US establishments.
- name: Marketing and CRM
description: Sync customer and loyalty data with marketing platforms.
- type: Blog
url: https://revelsystems.com/blog/
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Revel Systems API — frequently asked questions
Does Revel Systems have an API?
Yes. APIs.io lists 7 APIs from Revel Systems, including Revel Webhooks, Revel Systems Customers API and Revel Systems Establishments API, and 4 more.
Is there an OpenAPI specification for the Revel Systems API?
Yes. APIs.io indexes 5 OpenAPI specifications for Revel Systems, each linked for download from this page.
How do I authenticate with the Revel Systems API?
Revel Systems uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Revel Systems Authentication.
How much does the Revel Systems API cost?
APIs.io lists 1 pricing plan for Revel Systems, with each plan's price, limits and inclusions under Pricing Plans on this page.
Is the Revel Systems API ready for AI agents?
Revel Systems has a Kin Score of 20.5 out of 100 (emerging) and an Agent Readiness score of 28.1 (agent-aware), scored by API Evangelist on 2026-11-02.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: