Skip to main content
GET
/
api
/
v1
/
instore-queues
cURL
curl --request GET \
  --url https://api-staging.getmeadow.com/api/v1/instore-queues \
  --header 'X-Client-Key: <api-key>' \
  --header 'X-Consumer-Key: <api-key>'
{
  "data": {
    "intake": [
      {
        "id": 2982,
        "email": "perrin@getmeadow.com",
        "firstName": "Perrin",
        "lastName": "Aybara",
        "phone": null,
        "hashId": "e35rkb",
        "birthday": null,
        "isFirstTime": true
      }
    ],
    "pos": [
      {
        "id": 2983,
        "email": "rand@getmeadow.com",
        "firstName": "Rand",
        "lastName": "Al'Thor",
        "phone": "+18145551234",
        "hashId": "gn6xpb",
        "birthday": "1990-01-01",
        "isFirstTime": false
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://api-docs.getmeadow.com/llms.txt

Use this file to discover all available pages before exploring further.

There are two queues used in the waiting rooms: Intake Queue The intake queue is used to track which customers are currently waiting at intake, the front desk, or a waiting room, generally prior to being admitted to the shop floor where the POS stations are located. It also shows the intake station if the customer has a pending order, for example a pickup, in case there are special instructions for such customers. POS Queue The POS queue is used to track which customers are currently waiting in the shop floor where the POS stations are located. Any user with a POS station can view and select customers from the queue to start a new order or (following a prompt) process any existing order, for example a pickup.

Authorizations

​
X-Consumer-Key
string
header
required

The key assigned to your company and provided via Meadow

​
X-Client-Key
string
header
required

The key generated and provided by our mutual client

Response

Instore queue response

​
intake
object
​
pos
object