How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Delivery Hero OrdersEstimation API

The OrdersEstimation API from Delivery Hero — 2 operation(s) for ordersestimation.

Delivery Hero OrdersEstimation 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 OrdersEstimation. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 2 operations across 2 paths, and defines 17 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.

2 operations 2 paths 17 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.1.1
Base URL
https://ondemand-api-glovoapp.deliveryhero.io/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Delivery Hero OrdersEstimation 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 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

OrdersEstimation 2
POST
/orders/fee
Estimate Fee for an Order
1 param body → 200400422500
POST
/orders/time
Estimate Time for an Order
1 param body → 200400422500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are EstimateOrderRequest (7 properties), EstimateOrderTimeResponse (6 properties), Sender (5 properties), ContactWithOptionalFields (4 properties). Each schema is shown below with its type and property counts.

Latitude
number
PostalCode
string
Vendors in Singapore alone should use this attribute. If an accurate postal code is provided for Singapore orders, vendor does not need to provide address or l…
Sender
object
There are two type of payloads accepted: [PREFERRED] Outlet reference Please provide clientvendorid attribute Unique ID for the Outlet, retrieved from the Outl…
5 properties
PaymentMethod
string
Supported Payment Methods: PAID - Order has been fully paid already and courier will not collect any amount from the end customer CASHONDELIVERY - Courier will…
Price
number
Location
object
4 properties 3 required
ContactWithOptionalFields
object
Please provide location attribute The name and phonenumber attributes are optional. NOTE for vendors in Finland, Norway, and Sweden: Vendors in the the named c…
4 properties 1 required
ErrorResponse
object
1 property 1 required
EstimateOrderTimeResponse
object
6 properties
Boolean
boolean
ClientVendorID
string
Address
string
Description
string
EstimateOrderFeeResponse
object
3 properties
PhoneNumber
string
Phone number in E.164 standard (https://en.wikipedia.org/wiki/E.164) libphonenumber is used for phone number validation
Longitude
number
EstimateOrderRequest
object
7 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

delivery-hero-ordersestimation-api-openapi.yml Raw ↑

Other APIs Delivery Hero publishes across the network.

Delivery Hero Authentication API
Delivery Hero Callback API
Delivery Hero OrdersManagement API
Delivery Hero Outlets API
Delivery Hero Proofs API
Delivery Hero RiderPosition API
Where this information came from

This is an independent, third-party profile of Delivery Hero OrdersEstimation 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.