ZiroWait
Sign In
Available on request

Build on ZiroWait.

A secure REST API for your queue: create and cancel tokens, and read queues, entries and appointments. Server-to-server, with scoped keys.

Example request
curl -X POST https://api.zirowait.com/v1/queues/$QUEUE_ID/entries \
  -H "Authorization: Bearer $ZIROWAIT_KEY" \
  -H "Idempotency-Key: 6f1c2b7e-4d1a-4f0b" \
  -d '{ "name": "Priya", "phone": "+919876500001" }'
{ "data": {
  "id": "clx8f2a1c…",
  "token": "A12",
  "status": "WAITING",
  "position": 6,
  "predictedWaitMinutes": 18
} }

Example values. The full reference is in the docs.

What you can build

Your queue, in your own software.

Self check-in kiosks

Let people join the queue from your own kiosk, app or website. They are created straight into your ZiroWait queue.

Live queue on your screen

Read waiting and in-service tokens into your own lobby display or dashboard.

Sync with billing and POS

Pull the day's entries and appointments into the software you already run.

Appointments in your calendar

Read each day's bookings into your own scheduling or reporting tools.

Built for security

Built so your customers' data stays theirs.

Scoped, expiring keys

Each key gets only the permissions you choose, expires, and can be revoked instantly.

Keys are never stored

We keep only a keyed hash of the secret, and show the key once. A database leak yields no usable keys.

IP allowlist

Lock a key to your server's address. From anywhere else it is refused, even with the right key.

Audit log and request ids

Every request is recorded with its time, address and result, never the data or the key.

Safe retries

Idempotency keys mean a retried request never creates a duplicate token.

Businesses kept apart

Every request is limited to the one business that owns the key, enforced on every query.

Read the full security notes →

Coming next

Events pushed to you.

Signed webhooks are next. Until they arrive, poll the entries endpoint for changes.

Illustration of what webhooks will look like
Where we are

Honest about what's ready.

Now

API keys and the v1 endpoints

Ten endpoints for queues, tokens and appointments, with an OpenAPI 3.1 spec you can import into Postman or generate a client from. Available on request. We switch it on for your business.

Next

Signed webhooks and a sandbox

Get events pushed to you, and test with keys that never touch real data.

Later

Self-serve access and pricing

Once the above has proven itself. Pricing will be published here first.

Questions

Good things to ask first.

How do I get access?

Request it below. We switch the API on for your business, then your business owner creates keys in Dashboard → Settings → Developer API.

Is there an OpenAPI spec?

Yes. It is public at https://api.zirowait.com/v1/openapi.json, no key needed. Import it into Postman or Insomnia, or generate a typed client from it.

Can I call it from a website or app?

No, and that's deliberate. Keys must stay on your server, so the API sends no CORS headers and browsers cannot call it.

Does the API send WhatsApp messages?

Not in v1. It reads and manages your queue; it never messages anyone.

Are there webhooks or a sandbox?

Not yet. They're next. Until then, poll the entries endpoint.

What will it cost?

Pricing isn't set yet. We'll publish it before self-serve access opens.

I'm an agency with several clients. Can that work?

Each client business gets its own keys. Tell us what you need and we'll help set it up.

API access

Tell us what you want to build.

A few lines are enough: your business, what you'll build, and what you need from ZiroWait.

Request API access