Delivery Hero Callback API
**▶️ READ THIS FIRST ◀️*** Those are NOT actual endpoints. They are callback from ODR to your endpoint* This is used to represent the payload ODR will sent* This is an optional feature and it requires your callback URL to be registered with your ClientID---**Description*** The Callback URL will need to be HTTPS with a valid SSL certificate.* Body posted by this feature is stripped of any Personally Identifiable Information (PII).* Full Order body can be fetched using the Get Specific Order feature.* If there is an error, we retry sending the request three times. If the response status code is 2xx, it means that there was no error and the callback was successful in sending order status.
Delivery Hero Callback 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 Callback. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 3 operations across 3 paths, and defines 14 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 Callback 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 3
Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.
▶️ READ THIS FIRST ◀️ Those are NOT actual endpoints. They are callback from ODR to your endpoint This is used to represent the payload ODR will sent This is an optional feature a…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are CallbackRequest (15 properties), RefundCallbackRequest (8 properties), RefundCallbackProduct (5 properties), CallbackDriver (4 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 Callback 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.