Delivery Hero

Delivery Hero SE is a Berlin-based multinational online food-delivery and quick-commerce company operating in 70+ markets through local brands including foodpanda, Talabat, Glovo, PedidosYa, Yemeksepeti, Hungerstation and Pandamart. Its public developer surface exposes logistics and partner-integration APIs. The flagship On Demand Rider (ODR) API lets merchants request on-demand courier delivery across brands such as Glovo and pandago — registering outlets, estimating delivery fees and times, creating and tracking orders, retrieving proof of pickup/delivery/return, and receiving order-status, courier-location and refund webhooks. Additional Q-Commerce and Restaurant (POS) integration APIs handle order transmission and grocery assortment/promotion sync for restaurant and quick-commerce partners.

Delivery Hero publishes 7 API contracts indexed on the APIs.io network, including Authentication API, Callback API, OrdersEstimation API, and 4 more. Tagged areas include Company, Technology, Food Delivery, Logistics, and Quick Commerce.

The Delivery Hero catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Delivery Hero’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, authentication, sandbox, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.3/100 developing ▬ flat Agent 33/100 agent ready Heartbeat 78/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Technology Food Delivery Logistics Quick Commerce Last Mile Delivery On-Demand Order Restaurant Delivery

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Supply Chain Management

BC-520

OrdersManagementRiderPosition

POST /orders DELETE /orders/{order_id} GET /orders/{order_id}/coordinates

Transport Operations Management

BC-2420

Proofs

GET /orders/proof_of_delivery/{order_id}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 39.3/100 · developing

Contract Quality 11.2 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 0.0 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.0 / 15

Create-or-Update Ergonomics 5.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/delivery-hero/"><img src="https://apis.io/badge/delivery-hero/card.svg" alt="Delivery Hero on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 37.5 — up to +12.5 composite points
Operational Transparency scores 10.5 — up to +11.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/delivery-hero/apis.yml: open an issue on github.com/api-evangelist/delivery-hero to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Regulated Retail (cannabis track-and-trace, delivery marketplaces)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Delivery Hero Authentication API

Once you followed above steps from [Getting started](#section/Getting-Started) and that you have your signed JWT token, you can request the access token.

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 option...

Delivery Hero OrdersEstimation API

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

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 selectin...

Delivery Hero Outlets API

The Outlets API from Delivery Hero — 2 operation(s) for outlets.

Delivery Hero Proofs API

The Proofs API from Delivery Hero — 3 operation(s) for proofs.

Delivery Hero RiderPosition API

The RiderPosition API from Delivery Hero — 1 operation(s) for riderposition.

Scroll for all 7

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

On Demand Rider Authentication API

OPEN COLLECTION

On Demand Rider Authentication Callback API

OPEN COLLECTION

On Demand Rider Authentication OrdersEstimation API

OPEN COLLECTION

On Demand Rider Authentication OrdersManagement API

OPEN COLLECTION

On Demand Rider Authentication Outlets API

OPEN COLLECTION

On Demand Rider Authentication Proofs API

OPEN COLLECTION

On Demand Rider Authentication RiderPosition API

OPEN COLLECTION

Scroll for all 7

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Cancel an order and retrieve delivery proofs

AGENT SKILL

Create and track an On Demand Rider delivery

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Delivery Hero On Demand Rider Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Delivery Hero API Rules

61 rules · 51 errors 6 warnings 4 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Delivery Hero On Demand Rider Overlay

1 action · update · delivery-hero-on-demand-rider-openapi.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Delivery Hero Authentication

apiKey/oauth2 · 2 schemes

SECURITY

Delivery Hero Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Delivery Hero Scopes

1 scope

1 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: delivery-hero
name: Delivery Hero
description: Delivery Hero SE is a Berlin-based multinational online food-delivery and quick-commerce company operating in
  70+ markets through local brands including foodpanda, Talabat, Glovo, PedidosYa, Yemeksepeti, Hungerstation and Pandamart.
  Its public developer surface exposes logistics and partner-integration APIs. The flagship On Demand Rider (ODR) API lets
  merchants request on-demand courier delivery across brands such as Glovo and pandago — registering outlets, estimating delivery
  fees and times, creating and tracking orders, retrieving proof of pickup/delivery/return, and receiving order-status, courier-location
  and refund webhooks. Additional Q-Commerce and Restaurant (POS) integration APIs handle order transmission and grocery assortment/promotion
  sync for restaurant and quick-commerce partners.
url: https://raw.githubusercontent.com/api-evangelist/delivery-hero/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- hongshan
- hv-capital
- insight-partners
- point-nine
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: images/delivery-hero-on-demand-rider-logo.svg
x-docs-platform: swagger-ui
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-25
tags:
- Company
- Technology
- Food Delivery
- Logistics
- Quick Commerce
- Last Mile Delivery
- On-Demand
- Order
- Restaurant
- Delivery
tags_raw:
- Company
- Technology
- Food Delivery
- Logistics
- Quick Commerce
- Last Mile Delivery
- On Demand
- Orders
- Restaurant
- Delivery
apis:
- aid: delivery-hero:delivery-hero-authentication-api
  name: Delivery Hero Authentication API
  description: Once you followed above steps from [Getting started](#section/Getting-Started) and that you have your signed
    JWT token, you can request the access token.
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-authentication-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-callback-api
  name: Delivery Hero Callback API
  description: '**▶️ 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.'
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - Callback
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-callback-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-ordersestimation-api
  name: Delivery Hero OrdersEstimation API
  description: The OrdersEstimation API from Delivery Hero — 2 operation(s) for ordersestimation.
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - OrdersEstimation
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-ordersestimation-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-ordersmanagement-api
  name: Delivery Hero OrdersManagement API
  description: '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.'
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - OrdersManagement
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-ordersmanagement-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-outlets-api
  name: Delivery Hero Outlets API
  description: The Outlets API from Delivery Hero — 2 operation(s) for outlets.
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - Outlets
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-outlets-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-proofs-api
  name: Delivery Hero Proofs API
  description: The Proofs API from Delivery Hero — 3 operation(s) for proofs.
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - Proofs
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-proofs-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
- aid: delivery-hero:delivery-hero-riderposition-api
  name: Delivery Hero RiderPosition API
  description: The RiderPosition API from Delivery Hero — 1 operation(s) for riderposition.
  humanURL: https://on-demand-rider-docs.deliveryhero.io/
  baseURL: https://ondemand-api-glovoapp.deliveryhero.io/
  tags:
  - RiderPosition
  properties:
  - type: OpenAPI
    url: openapi/delivery-hero-riderposition-api-openapi.yml
  - type: APIReference
    url: https://on-demand-rider-docs.deliveryhero.io/
  - type: Documentation
    url: https://on-demand-rider-docs.deliveryhero.io/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.deliveryhero.com/newsroom/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/delivery-hero-capability-edges.yml
  name: Delivery Hero Business Capability Map
- type: Overlay
  url: overlays/delivery-hero-on-demand-rider-overlay.yaml
- type: Website
  url: https://deliveryhero.com
- type: DeveloperPortal
  url: https://developers.deliveryhero.com/
- type: Documentation
  url: https://on-demand-rider-docs.deliveryhero.io/
- type: APIReference
  url: https://on-demand-rider-docs.deliveryhero.io/
- type: GettingStarted
  url: https://on-demand-rider-docs.deliveryhero.io/
- type: GitHubOrganization
  url: https://github.com/deliveryhero
- type: Blog
  url: https://www.deliveryhero.com/newsroom/
- type: Support
  url: https://developers.deliveryhero.com/
- type: Authentication
  url: authentication/delivery-hero-authentication.yml
- type: OAuthScopes
  url: scopes/delivery-hero-scopes.yml
- type: Conventions
  url: conventions/delivery-hero-conventions.yml
- type: ErrorCatalog
  url: errors/delivery-hero-problem-types.yml
- type: Lifecycle
  url: lifecycle/delivery-hero-lifecycle.yml
- type: Conformance
  url: conformance/delivery-hero-conformance.yml
- type: DataModel
  url: data-model/delivery-hero-data-model.yml
- type: Sandbox
  url: sandbox/delivery-hero-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/delivery-hero-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Webhooks
  url: asyncapi/delivery-hero-on-demand-rider-webhooks.yml
- type: DomainSecurity
  url: security/delivery-hero-domain-security.yml
- type: LLMsTxt
  url: llms/delivery-hero-llms.txt
- type: AgentSkill
  url: skills/delivery-hero-create-and-track-order.md
- type: AgentSkill
  url: skills/delivery-hero-cancel-and-proof.md
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Delivery Hero API — frequently asked questions

Does Delivery Hero have an API?

Yes. APIs.io lists 7 APIs from Delivery Hero, including Delivery Hero Authentication API, Delivery Hero Callback API and Delivery Hero OrdersEstimation API, and 4 more.

Is there an OpenAPI specification for the Delivery Hero API?

Yes. APIs.io indexes 7 OpenAPI specifications for Delivery Hero, each linked for download from this page.

How do I authenticate with the Delivery Hero API?

Delivery Hero uses bearer-token authentication (apiKey/oauth2 · 2 schemes). The details are profiled on APIs.io as Delivery Hero Authentication.

Is the Delivery Hero API ready for AI agents?

Delivery Hero has a Kin Score of 39.3 out of 100 (developing) and an Agent Readiness score of 33.4 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/delivery-hero"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/delivery-hero/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/delivery-hero/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.