The Dislab API: start here

The console is a client of Dislab’s public API, so what you can do in the console your own systems can do too, within what their key allows. Every address starts with:

https://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1

1. Make an API key in Settings that can do what your system needs (see API keys and what each can do).
2. Send it in the Authorization header of every request, as Bearer then the key.
3. Send and expect JSON (Content-Type: application/json).

Your first call, listing your live values:

curl https://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1/values \
  -H "Authorization: Bearer dsk_YOUR_KEY"

What a key can reach:

• Live values: numbers, text and lists your signs show.
• Menus: prices and sold out from your till.
• Screens: what each screen plays, Show it now, and health.

Dislab tells your systems what happens with webhooks. Apps used by many businesses connect with Connect Dislab (OAuth) instead of keys, and can show the console inside themselves: see Embedding Dislab in your app.

API keys work while the account is on Pro. Times are ISO 8601 in UTC; ids are UUIDs. Errors and limits: Errors and limits.