POST Orders Pickup Times

Returns the store's raw serving windows for an order type.

For the Cart 2.0 flow, use Orders Filtered Pickup Times instead. This endpoint does not apply preparation time, does not look at the cart, and does not filter out slots that order throttling has already filled — so a time it offers can still be rejected at checkout. It is kept for the simple case where you only want to show a store's opening windows, for example on a store information screen.

No customer token is required.

Headers

Accept
Type: string
required

Type of content accepted by the API (application/json in most cases)
Application
Type: string
required

Application key for specific client app
Content-Type
Type: string
required

Content-Type header
API-VERSION
Type: string
required

Version of the API to be used
Authorization
Type: string

Authorization header
X-Request-ID
Type: string
required

Unique request identifier

Body

application/json

singular_point_id
Type: stringFormat: uuid
required

UUID of the singular point for the order type, taken from the venue's areas.
in_advance_date
Type: stringFormat: date

A later calendar day, where the store allows ordering days in advance. Omit for today.
order_type_id
Type: integer

Flat order type id. Only affects catering takeout; this endpoint otherwise returns the store's own serving windows. Note the filtered endpoint takes a nested order_type.id instead.

Responses

application/json

post/orders/pickup-times

curl https://api-public-demo.menu.app/api/orders/pickup-times \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Application: application-key' \
  --header 'Content-Type: application/json' \
  --header 'API-VERSION: ' \
  --header 'X-Request-ID: c10b4a70-6274-490d-80a0-03e7bb826937' \
  --data '{
  "singular_point_id": "9254eb1c-ce27-4fa5-993e-c39096e7141d"
}'

Show Schema

{
  "status": "OK",
  "code": 200,
  "data": {
    "pickup_times": [
      "2023-05-25 07:15:00"
    ]
  }
}

Example response