SpotOn
SpotOn is an all-in-one restaurant point-of-sale and management platform that combines POS, online ordering, reservations, payments, labor, and reporting for restaurants and hospitality businesses. For developers and integration partners, SpotOn offers the Restaurant POS Export API, a location-centric REST API that delivers close-to-realtime data export from the SpotOn Restaurant POS System. It exposes resources such as orders, menu items, modifiers, employees, taxes, surcharges, payment options, labor reports, and time clock entries. Authentication uses an API key supplied via the x-api-key request header, with access granted on a per-location basis. SpotOn also publishes the Reserve API (powered by SeatNinja) for its reservations and waitlist product.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles SpotOn the way a machine reads it — 135 machine-readable artifacts across 15 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 — SpotOn scores 62.6/100 (strong), with a separate agent-readiness read of 48/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.
How we profile SpotOn
Each block below is one kind of artifact we hold for SpotOn. 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 15
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.
SpotOn Availability API
Available reservation times and wait-time lookups.
SpotOn Cash Deposits API
Cash deposit records recorded at a location.
SpotOn Employees API
Employee records and their job positions for a location.
SpotOn Job Positions API
Job position definitions for a location.
SpotOn Locations API
Location details for the SpotOn POS organization.
SpotOn Menu Items API
Menu item catalog for a location.
SpotOn Order Types API
Order type definitions for a location, such as Dine In or Takeout.
SpotOn Orders API
Order and check data export, including items, modifiers, payments, and taxes.
SpotOn Paid In Outs API
Cash paid in and paid out records for a location.
SpotOn Payment Options API
Payment methods configured at a location.
SpotOn Report Categories API
Hierarchical report categories used to group menu items.
SpotOn Reservations API
Create and manage guest reservations.
SpotOn Restaurants API
Restaurants accessible with the API key.
SpotOn Time Clock Entries API
Employee shift clock-in and clock-out records.
SpotOn Waitlist API
Add guests to a restaurant waitlist.
Scroll within the panel for all 15 ·
Pricing 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.
Spoton Plans Pricing
PLANSRate 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.
Spoton 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.
Spoton Finops
FINOPSFeatures 7
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.
Restaurant POS
All-in-one point-of-sale for counter-service and full-service restaurants.
Online Ordering
Branded online ordering integrated with the POS.
Reservations and Waitlist
SpotOn Reserve manages reservations, waitlists, and guest communication.
Payments
Integrated card processing with per-transaction take rates.
Labor Management
Employees, job positions, time clock entries, and labor reporting.
Reporting
Sales, cash, and labor reporting with close-to-realtime data export.
Data Export API
Location-centric REST API exporting orders, menu, payments, and labor data.
Scroll within the panel for all 7 ·
Semantic 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.
Spoton Reserve Context
JSON-LDSpectral Rules 2
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.
SpotOn API Rules
SPECTRALSpotOn API Rules
SPECTRALJSON Schema 31
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.
AvailabilityResponse
JSON SCHEMAAvailabilitySlot
JSON SCHEMACustomerInformation
JSON SCHEMAReservationRequest
JSON SCHEMAReservation
JSON SCHEMARestaurant
JSON SCHEMAWaitTimeResponse
JSON SCHEMAWaitlistEntry
JSON SCHEMAWaitlistRequest
JSON SCHEMAAddress
JSON SCHEMABreak
JSON SCHEMACashDeposit
JSON SCHEMAEmployee
JSON SCHEMAJobPosition
JSON SCHEMALocation
JSON SCHEMAMenuItemCatalog
JSON SCHEMAOrderCheck
JSON SCHEMAOrderDiscount
JSON SCHEMAOrderGuest
JSON SCHEMAOrderMenuItem
JSON SCHEMAOrderModifier
JSON SCHEMAOrderPayment
JSON SCHEMAOrder
JSON SCHEMAOrderSurcharge
JSON SCHEMAOrderTax
JSON SCHEMAOrderType
JSON SCHEMAOwnerInfo
JSON SCHEMAPaidInOut
JSON SCHEMAPaymentOption
JSON SCHEMAReportCategory
JSON SCHEMATimeClockEntry
JSON SCHEMAScroll within the panel for all 31 ·
JSON Structure 31
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.
Reserve Availability Response Structure
JSON STRUCTUREReserve Availability Slot Structure
JSON STRUCTUREReserve Customer Information Structure
JSON STRUCTUREReserve Reservation Request Structure
JSON STRUCTUREReserve Reservation Structure
JSON STRUCTUREReserve Restaurant Structure
JSON STRUCTUREReserve Wait Time Response Structure
JSON STRUCTUREReserve Waitlist Entry Structure
JSON STRUCTUREReserve Waitlist Request Structure
JSON STRUCTURERestaurant Pos Export Address Structure
JSON STRUCTURERestaurant Pos Export Break Structure
JSON STRUCTURERestaurant Pos Export Cash Deposit Structure
JSON STRUCTURERestaurant Pos Export Employee Structure
JSON STRUCTURERestaurant Pos Export Job Position Structure
JSON STRUCTURERestaurant Pos Export Location Structure
JSON STRUCTURERestaurant Pos Export Menu Item Catalog Structure
JSON STRUCTURERestaurant Pos Export Order Check Structure
JSON STRUCTURERestaurant Pos Export Order Discount Structure
JSON STRUCTURERestaurant Pos Export Order Guest Structure
JSON STRUCTURERestaurant Pos Export Order Menu Item Structure
JSON STRUCTURERestaurant Pos Export Order Modifier Structure
JSON STRUCTURERestaurant Pos Export Order Payment Structure
JSON STRUCTURERestaurant Pos Export Order Structure
JSON STRUCTURERestaurant Pos Export Order Surcharge Structure
JSON STRUCTURERestaurant Pos Export Order Tax Structure
JSON STRUCTURERestaurant Pos Export Order Type Structure
JSON STRUCTURERestaurant Pos Export Owner Info Structure
JSON STRUCTURERestaurant Pos Export Paid In Out Structure
JSON STRUCTURERestaurant Pos Export Payment Option Structure
JSON STRUCTURERestaurant Pos Export Report Category Structure
JSON STRUCTURERestaurant Pos Export Time Clock Entry Structure
JSON STRUCTUREScroll within the panel for all 31 ·
Examples 31
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.
Reserve Reservation Example
EXAMPLEReserve Restaurant Example
EXAMPLEScroll within the panel for all 31 ·
Security Posture 3
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.
Accounting and Reconciliation
Export orders, payments, and cash deposits to reconcile against statements and accounting systems.
Business Intelligence
Pull POS sales and labor data into a warehouse for analytics and dashboards.
Payroll Integration
Export time clock entries and pay rates to drive payroll processing.
Menu Synchronization
Keep third-party ordering and inventory systems in sync with the POS menu catalog.
Guest Booking Experiences
Build reservation and waitlist flows using the Reserve API and its JavaScript SDK.
Integrations 4
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 Systems
Feed exported sales, cash, and tip data into accounting and bookkeeping platforms.
Payroll Providers
Use time clock and labor data to integrate with payroll services.
Data Warehouses
Load POS export data into analytics warehouses and BI tools.
Reservation Front-Ends
Embed SpotOn Reserve booking and waitlist via the JavaScript SDK.
Resources
Every other property we hold for SpotOn — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
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 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/spoton · machine-readable index on apis.io