Skip to main content

Data Management | Getting Started

The process to get started with Data Management API is outlined in the table. Note that each step is its own process.

Step

Topic

Description

1

Getting Started with APIs

Steps to obtain an integrator token and additional information about our APIs.

2

Confidentiality Statement

Information about our non-disclosure agreement (NDA) terms and conditions regarding endpoints.

3

API Prerequisites

A list of prerequisites to complete before starting the integration development process.

4

Query Parameters

Use Data Management's endpoint query parameters.

5

Master, Current, and List Endpoints

Use different filters to retrieve data.

Data Management | Next Steps

After the initial set up is completed, review these additional topics on Data Management menu creation:

Topic

Description

Operation Definitions

Lists and describes Data Management's endpoints and data models.

Create a Menu Using Data Management Menu Features

Describes the methods used to retrieve menu data and define the data objects Data Management uses for menu elements.

Create a Menu from Data Management Product Objects

Describes how to use the Online Ordering product resource to get details about products and how to organize those products into a typical online menu structure.

For information on Sequential Cart Deployment, see Enable Sequential Cart Deployment.

Query Parameters

Data Management API endpoint query parameters are listed below:

Parameter

Description

effective_date

Defines the valid, effective date of returned entities. For /current routes, the effective_date returns entities dated on the specified date. For /list routes, the effective_date returns entities dated after the specified date.

Example:

effective_date=20YY-07-26T14:04:42.766Z

$filter

The response only includes entities matching the criteria defined by the $filter.

Example:

$filter=product_entity_id eq objectid(586e6e9fc21cbd000119bd14)

$top

Defines the number of returned entities. Useful for navigating large data sets.

Example:

$top=10

$skip

Defines the number of entities to skip before returning entities. Useful for navigating large data sets.

Example:

$skip=10

$orderby

Defines the data sorting property. Useful for locating recent updates or new menu items.

Example:

$orderby=last_updated desc

include_entities

Defines the properties of the returned entities. Useful for retrieving specific entities. For example, using include_entities['product_price'] in a /product request returns the product definition and price details.

Example:

include_entities=['product-price','time-period']

entity_ids

Defines the ID of the returned entities. Useful for locating specific menu pages or add-on items.

Example:

entity_ids=['5a591e77fcacfe00019a8067','5a591ae8fcacfe00019a802e']

Master, Current, and List Endpoints

Each resource includes /master, /current, and /list endpoints that retrieve data with different filters:

Endpoint

Description

/master

The /master route returns a list of valid entities independent of site. Sometimes, variations of the entities are displayed based on specific dates. The example is a request to the /product/master endpoint:

{{dm_url}}/product/master

/current

The /current route returns a list of valid entities dated on the requested date, for specified sites. The example is the expected date format for the /current route:

{{dm_url}}/product/current?effective_date=20YY-07-26T14:04:42.766Z

/list

The /list route returns a list of valid entities dated after the specified date. An effective_date parameter is required. Use the /list route to get properties required to build menus that take effect in the future, such as upcoming promotions. The example is a /list route request with the required effective_date parameter:

{{dm_url}}/product/list?effective_date=20YY-07-26T14:04:42.766Z