SpotOn
Integuru generates a production-ready HTTP API for SpotOn, the restaurant POS and payments platform. The integration covers 9 actions spanning customer listing, settlements, net sales reporting, location management, employee data, and order retrieval, all carrying richer docs, enabling restaurant tech teams to automate POS and financial data access programmatically.
Last reviewed: July 2026
Overview
Integuru's SpotOn integration provides production-ready HTTP API access to SpotOn, the restaurant POS and payments platform at dashboard.spoton.com, covering 9 actions: list_customers, spoton_get_settlements, get_net_sales_report, spoton_restaurant_get_locations, spoton_restaurant_get_employees, spoton_restaurant_get_employee, spoton_restaurant_get_orders, spoton_restaurant_get_order, and spoton_restaurant_get_location. All 9 actions carry richer documentation. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.
No public developer API. SpotOn does not expose an official developer API for POS and operational data. Restaurant tech teams that need customer records, settlement data, order history, or employee data programmatically have had no standard integration path.
The integration covers the full operational data surface of a SpotOn restaurant account: customer management via list_customers, financial reporting via spoton_get_settlements and get_net_sales_report, location management via spoton_restaurant_get_locations and spoton_restaurant_get_location, employee data via spoton_restaurant_get_employees and spoton_restaurant_get_employee, and order data via spoton_restaurant_get_orders and spoton_restaurant_get_order. See the Aloha integration or Resy integration for other restaurant-tech integrations, or browse the full integrations catalogue.
Use Cases
Integuru's SpotOn integration covers the POS, financial, employee, and order workflows that restaurant tech teams need to automate.
- Customer listing: Call
list_customerswith optionallimitandoffsetfor paginated customer record retrieval. - Settlement reporting: Call
spoton_get_settlementswith requiredstart_dateandend_date(both YYYY-MM-DD) to retrieve settlement records for a date range. These are the only required parameters across all 9 SpotOn actions. - Monthly net sales report: Call
get_net_sales_reportwith optionaldate(any date within the target month, YYYY-MM-DD; defaults to today) to retrieve the monthly net sales report. - Location listing: Call
spoton_restaurant_get_locationswith no parameters to retrieve all restaurant locations on the account. - Location detail: Call
spoton_restaurant_get_locationwith optionallocation_key(auto-detected if omitted) to retrieve detail for a specific location. - Employee roster: Call
spoton_restaurant_get_employeeswith optionallocation_keyto retrieve all employees at a location. - Single employee detail: Call
spoton_restaurant_get_employeewith optionallocation_keyto retrieve a specific employee record. - Order listing: Call
spoton_restaurant_get_orderswith optionalstart_date(defaults to today),end_date(defaults tostart_date), andlocation_keyto retrieve orders for a date range. - Single order detail: Call
spoton_restaurant_get_orderwith the same optional date and location parameters to retrieve a specific order record.
Setup Notes
Integuru's SpotOn integration authenticates against https://dashboard.spoton.com/. Configure credentials once during Integuru setup; Integuru handles session management automatically.
The only actions with required parameters are spoton_get_settlements (start_date and end_date, both YYYY-MM-DD). All other SpotOn actions are fully optional. location_key is auto-detected from the authenticated account when omitted, making single-location setups parameter-free for most actions.
Richer documentation for all 9 actions is available via the Integuru dashboard after setup.