API

One gateway. The apps use it. So can you.

Everything the terminal, the Manager app and the Driver app do goes through one HTTPS service that speaks JSON. Partners get the same service, scoped to the stores that authorise them, with a sandbox store to build against first.

basehttps://$JET_HOST

The host comes with your sandbox credentials. Substitute it for $JET_HOST below.

Reference

Five routes that cover a first integration: sign in, read sales, read tickets, ask Oreon, confirm. The rest of the surface comes with the sandbox.

POST/api/restaurant/loginauth: None

Sign in with a restaurant account. Returns a token scoped to the account’s store.

Request
curl -X POST https://$JET_HOST/api/restaurant/login \
  -H "Content-Type: application/json" \
  -d '{ "username": "[email protected]", "password": "••••••••" }'
Response · 200
{
  "success": true,
  "accessToken": "eyJhbGciOiJIUzI1NiIs…",
  "store": { "id": 12, "name": "Bridge Pizza" },
  "timezone": "America/New_York"
}

Accounts with several stores call GET /api/restaurant/stores and POST /api/restaurant/select-store to switch. Staff-level actions additionally need POST /api/restaurant/pin-login with the user’s PIN.

How access works

Authentication is per restaurant account, with roles. A partner sees one store’s data because that store’s owner said so, and stops seeing it when they say otherwise.

Transport
HTTPS, JSON in and out. Every response carries a top-level "success".
Auth
Bearer token from /api/restaurant/login. Role guards on every route: terminal, manager, driver, restaurant. Staff-level actions need a PIN sign-in on top.
Scope
One store per token. Multi-store accounts select the store and get a re-issued token.
Time
Report dates are read in the store’s timezone. Timestamps come back in UTC.
Sandbox
A test store with realistic data. Nothing you do there touches a live counter.
Rate limits
Agreed when credentials are issued, based on what you are polling and how often.

What the rest of the gateway covers

Areas of the service, in plain words. The endpoint list for each comes with the sandbox.

  • 01

    Menu

    Categories, items, portions, modifier groups, screen menus, floor plans.

  • 02

    Tickets

    Open and closed tickets, items, payments, void and refund actions.

  • 03

    Payments

    Card processing through our processor, printer routing, receipts.

  • 04

    Reports

    Sales summary, hourly and daily series, products, staff, customers, hours.

  • 05

    Delivery

    Runs, driver claims by code, live location, tips at the door, settlement.

  • 06

    Marketing

    Customer list, coupons, loyalty milestones, text campaigns.

  • 07

    Oreon

    Plain-language questions and confirmed menu changes.

  • 08

    Stores and staff

    Locations, roles, PIN sign-in, time clock.

Get a sandbox

Tell us what you are building and which store. A person who works on the gateway replies with a test account, credentials and the routes you need.

[email protected](302) 538-9599
CallSee my savings