Delivery Hero OrdersManagement API
The following sections provide a complete summary of all available endpoints and features connected with the Orders API.Please review the documentation carefully. When selecting an endpoint, note the information on the right-hand side of the screen, which details the following critical elements:- **Request Attributes: Mandatory formatting** for specific attributes (e.g., phone numbers, coordinates, addresses) is outlined here. **Pay close attention to these requirements.**- **Request Examples:** Illustrative examples of successful requests.- **Request Responses:** Examples of successful and failed responses, including common error codes and messages.
Delivery Hero OrdersManagement API is one of 7 APIs that Delivery Hero publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include OrdersManagement. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 4 operations across 2 paths, and defines 47 schemas. It is described by OpenAPI 3.0.0, at version 1.1.1.
Requests are made against 4 base URLs: https://pandago-api-sandbox.deliveryhero.io/sg/api/v1, https://api-infra-eu-central-1.stg.ondemandrider.net/{country code}/api/v1, https://ondemand-api-glovoapp.deliveryhero.io/{country code}/api/v1, https://ondemand-api-glovoapp.deliveryhero.io/pt/api/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Delivery Hero OrdersManagement API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (Bearer_Token).
By default, every request must be authenticated.
Bearer_Token— Provide the access token in the format: Bearer {access-token}. You can obtain the access token from the [Authentication endpoint](tag/Authentication).
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
The following sections provide a complete summary of all available endpoints and features connected with the Orders API. Please review the documentation carefully. When selecting…
Schemas 47
The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are OrderResponse (29 properties), CreateOrder (18 properties), CreateOrderRequest (16 properties), UpdateOrder (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Delivery Hero 6
Other APIs Delivery Hero publishes across the network.
This is an independent, third-party profile of Delivery Hero OrdersManagement API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.