Endpoint

POST /menus Ingest menu(s) - creating a baseline per menu received

How it works

The JET Connect (Flyt) Platform API allows anyone with a Skip account to automatically publish menus from their POS to the respective delivery partner. For this to work, client applications need to:

Extract menu data from their POS
Use this data to create an HTTP request in JSON format (see format details below)
Send the request to the menu API endpoint: https://api.flytplatform.com/menus

The API endpoint will validate the incoming request and, if checks are successful, publish the new menu to the delivery partner. We recommend checking the delivery partner page to see if the new menu has been updated as intended.

Changes from Version 1

Version 2 of the Menus API offers the following benefits over the existing API:

Static endpoints for publishing menus. These endpoints do not include brand and location references in the endpoint URL, making it easier for operations teams to onboard new restaurants.
Ability to update menus for multiple restaurants using a single request.

Request format

Endpoint to call

POST <https://api.flytplatform.com/menus>

Headers

X-Flyt-API-Key: the API key you received from JET Connect. This API key can be reused across the Menus and Item Availability endpoints. You should not share this API key with anyone outside your organisation.

Content-Type: specified the content type of your request. Should always be set to application/json.