Checkmate API
Integuru generates a production-ready HTTP API for Checkmate, the platform that routes third-party delivery and online orders into restaurant POS systems, for operators and the analytics tools that read their order flow. 6 verified actions list locations, pull orders by page or by business date, check a single order's state, and list menus and menu items per location, with further actions available on request.
6
Verified actions live today
<3 sec
Response latency per call
99.9%+
Reliability rate on generated APIs
24/7
On-call maintenance on Production plans
Integration facts
- Authenticates against
- https://app.itsacheckmate.com/
- Authentication
- Login flows, including 2FA, handled by Integuru using your own Checkmate credentials.
- Approach
- Direct HTTP requests, with no browser automation or RPA involved.
Endpoints
Available actions
Don't see the action you need?
The actions above cover the most common Checkmate integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.
Guide
Checkmate integration guide
Does Checkmate have a public API?
Checkmate does not publish a self-serve operator API for orders and menus. Its integrations run between ordering platforms and POS systems, and operators work in the web app at app.itsacheckmate.com. Integuru's 6 verified actions give that operator login direct HTTP access to locations, orders, order state and menus, returned as structured data.
What you can do with the Checkmate API
Locations. list_locations pages 10 at a time (page, per_page), filters by search_term on name or address, and includes inactive sites when show_inactive is true. Every other action needs a location_id from it.
Orders. list_orders pages a location's orders with an optional search_term. checkmate_orders_by_date returns every order for one local business date (YYYY-MM-DD), matched on created time in the location's timezone, which is the call for a nightly close. get_order_state checks one order by order_id, the source order number or platform order UUID.
Menus. list_menus and list_menu_items page a location's menus and items, with search_term matching on title.
Who uses this
Multi-unit operators reconcile third-party sales to POS by pulling checkmate_orders_by_date per location and matching it to the POS close. Analytics tools already reading SpotOn or Indy through Integuru add Checkmate as the aggregator layer. Menu-management teams diff list_menu_items against their source of truth after a price change. The restaurants industry page covers the full stack from ordering to payroll.
Setup notes
Integuru authenticates against app.itsacheckmate.com with your Checkmate user. Pagination is 1-based with a default of 10 per page. Business dates are evaluated in each location's local timezone, so run the nightly pull after that location's close rather than at a single global time.
Get started
Install the CLI and connect your Checkmate login:
npm install -g integuru
Or sign in at app.integuru.com and add Checkmate. To bring menu edits, item availability toggles or order acknowledgement into the same workflow, the Managed Service scopes and builds those actions against your account.
Guides in Restaurants & Food Service
Platform API guides in this vertical
Good to know
Before you start
- Can I use it today?
- Yes. Every action listed above has been verified against live Checkmate traffic. Install the CLI or sign in at app.integuru.com, connect your Checkmate account, and start calling the endpoints.
- What if Checkmate changes or breaks?
- On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
- What does it cost?
- Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.
FAQ