Skip to main content

Things to Know

This topic contains answers to frequently asked questions about onboarding new sites to Online Ordering:

How do we know when to request a new token? Do they have a default value of token expiration?

Tokens have a default of 21 days expiration time. Expiring codes will receive a 401 / 402 message that will allow for renegotiating the /token call to get a new token.

What difference in minutes between server_timestamp and last_contact_time should we treat as a threshold for when a store goes to offline status?

server_timestamp is the timestamp that our system records when receiving the site status message from the store. last_contact_time is the time that the adapter creates in the store when the message is created. Our Site Status Notification service will provide both the store online and offline messages, so calculating the threshold is unnecessary. Additionally, our system can send an https request to an applicable API to pause/unpause online ordering operation for a store.

How do we create a customer?

Send a request with all customer information, typically collected from customer login information from a merchant's website. Substitute first name and last initial for the customer's full name to avoid PII. Phone information is optional, and a customer ID is only required for services such as customer loyalty programs.

How do we send a pickup time?

pickup_date_time is part of the customer object. How this value is queued depends on whether the pickup time exceeds the current business day.

Is it possible to send a payment within the create order request?

No. Add Payments is a separate API call to the PUT order/payment endpoint.

How do we obtain a value for the pay_type_id property?

Our system will provide the pay_type_id value. Our system will also provide certain other values, such as destination and discount values that are standardized for use in the Data Management API.