Build on the platform behind the table.
Yusker runs discovery, ordering, pay-at-table and the point of sale for hospitality. Two API surfaces expose it to developers: the Venue API, live today for suppliers and integrators, and the Payments API, in a design-partner preview.
Venue API — live
The Venue API is how suppliers, inventory systems and custom tools plug into a venue’s operation on Yusker:
- Keys & auth — venue-scoped
yk_bearer keys with granular scopes, minted by the owner in the portal. - Venues, menus & orders — read venue data and orders; update menu prices and availability.
- Order webhooks —
order.created/order.updated, HMAC-signed, retried with backoff.
Payments API — preview
Yusker Payments is built as a managed payment facilitator: it boards sub-merchants (venues) under a single platform, prices each one, moves funds from the diner to the venue, keeps a transparent platform fee, and posts every cent to a double-entry ledger — the same rails that power pay-at-table, online ordering, and marketplace payouts across the Yusker network. Canadian-native: settles in CAD, prices to Canadian interchange, and treats Interac as a first-class rail.
The Payments API is not yet publicly callable — it is being finalized with design partners, and shapes may change before general availability. Request access to join the program; the docs are published so you can evaluate the integration surface today.