Delivery Hero POS Plugin API

Name: Delivery Hero POS Plugin API API
Brand: Delivery Hero POS Plugin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementbearer4 EndpointsREST

For Agents

Receive orders dispatched from Delivery Hero brands into a POS, update order status back to Delivery Hero, and trigger menu imports.

Connect the Delivery Hero POS Plugin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Delivery Hero POS Plugin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Delivery Hero POS Plugin API API.

Receive orders dispatched from Delivery Hero into a POS via POST /order/{remoteId}

Update the POS-side status of an order back to Delivery Hero through PUT /remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus

Trigger a menu import for a restaurant with GET /menuimport/{remoteId}

Acknowledge catalog import completion via the POST /{catalogImportCallback} hook

GET STARTED

Start building with Delivery Hero POS Plugin API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Delivery Hero POS Plugin API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Delivery Hero POS Plugin API, keeping it validated and agent-ready. The API is the contract that POS systems implement so Delivery Hero's order processing service can dispatch live orders, accept status updates, and trigger menu imports for restaurants on Foodpanda, Talabat, and other Delivery Hero brands. The surface is small but tightly scoped: orders are pushed to the POS, the POS reports back status, and menu imports are triggered on demand with a callback for completion.

Use Cases

Patterns agents use Delivery Hero POS Plugin API API for, with concrete tasks.

★ POS Integration for Delivery Hero Brands

Connect a third-party POS to Foodpanda, Talabat, and other Delivery Hero brands by implementing this plugin contract. Delivery Hero pushes each new order to POST /order/{remoteId}, the POS responds with status changes via the posOrderStatus PUT, and menu changes are pulled with the menu import endpoint. This is the canonical integration shape Delivery Hero expects from POS partners.

Implement POST /order/{remoteId} in the POS, accept the dispatched order payload, and respond with PUT posOrderStatus when the order is accepted.

Real-Time Order Status Sync

Keep Delivery Hero in sync with kitchen reality by reporting status transitions (accepted, preparing, ready, completed, rejected) through the posOrderStatus PUT endpoint. This avoids stale order screens for couriers and customers and feeds Delivery Hero's SLA dashboards.

When the kitchen marks an order ready, call PUT /remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus with the new status.

Menu Import on Demand

Refresh a restaurant's catalog on Delivery Hero by calling GET /menuimport/{remoteId} from the POS or a back-office tool. Completion is reported asynchronously via the catalog import callback, so the POS knows when the new menu is live on the storefront.

Call GET /menuimport/{remoteId} to start a menu import, then handle the catalog import callback to confirm completion.

AI Agent Integration via Jentic

An operations agent can use Jentic to push order status updates back to Delivery Hero or kick off menu imports across a fleet of restaurants. Jentic resolves the Bearer token from the vault and exposes typed schemas for each operation, so the agent can act on the integration without reading the underlying contract.

Use Jentic to search for 'update delivery hero pos order status', load the operation, and execute it with the order id and new status.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for delivery hero pos plugin api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/order/{remoteId}

Dispatch an order to the POS plugin

PUT

/remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus

Update POS order status

GET

/menuimport/{remoteId}

Trigger a menu import

POST

/{catalogImportCallback}

Receive catalog import status callback

POST

/order/{remoteId}

Dispatch an order to the POS plugin

PUT

/remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus

Update POS order status

GET

/menuimport/{remoteId}

Trigger a menu import

POST

/{catalogImportCallback}

Receive catalog import status callback

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bearer tokens issued by Delivery Hero are stored encrypted in the Jentic vault and injected at execution time, so the secret never enters the agent's prompt or memory.

Intent-based discovery

Agents search by intent (e.g. 'update delivery hero pos order status') and Jentic returns the matching operation with its full schema, removing the need to read the integration doc set.

Time to first call

Direct integration: 1-2 weeks to implement the plugin contract, callbacks, and certification. Through Jentic: outbound calls to status and menu endpoints can be wired in under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Toast POS API

Restaurant POS platform whose order data often needs to flow into Delivery Hero.

Use Toast alongside Delivery Hero POS Plugin when integrating a Toast-based restaurant with Foodpanda or Talabat marketplaces.

Complementary

Square API

Square POS and payments stack used by many restaurants on aggregator platforms.

Use Square alongside Delivery Hero when the POS or payment leg of a restaurant integration is on Square.

Complementary

Lightspeed API

Hospitality POS used by restaurants that may also serve Delivery Hero brands.

Use Lightspeed alongside Delivery Hero when bridging a Lightspeed POS to Foodpanda or Talabat order flows.

Alternative

Grubhub API

Food delivery marketplace API for the US covering similar order dispatch concerns.

Choose Grubhub when the operational scope is US restaurants on Grubhub rather than the Delivery Hero family of brands.

FAQs

Specific to using Delivery Hero POS Plugin API API through Jentic.

Why is there no official OpenAPI spec for Delivery Hero POS Plugin API?

Delivery Hero does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Delivery Hero POS Plugin API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Delivery Hero POS Plugin API use?

The Delivery Hero POS Plugin API uses HTTP Bearer token authentication. Tokens are issued by Delivery Hero to onboarded POS partners. Through Jentic, tokens are stored encrypted in the vault so they never appear in the agent's context.

Can I receive new Delivery Hero orders into my POS through this API?

Yes. POST /order/{remoteId} is the dispatch endpoint Delivery Hero calls when a new order arrives for a restaurant. The POS implements this endpoint, parses the order payload, and acknowledges with a status update.

How do I update an order's status back to Delivery Hero?

Call PUT /remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus with the new status (for example accepted, preparing, ready, or completed). Delivery Hero uses these updates to drive courier dispatch and customer-facing screens.

How do I trigger a menu import for a restaurant?

Call GET /menuimport/{remoteId} for the restaurant whose catalog needs refreshing. Completion is reported asynchronously through the POST /{catalogImportCallback} hook, which the POS implements to confirm the import finished.

How do I push order status updates through Jentic?

Run `pip install jentic`, search for 'update delivery hero pos order status', load PUT /remoteId/{remoteId}/remoteOrder/{remoteOrderId}/posOrderStatus, and execute with the order ids and new status. Jentic handles the Bearer auth from the vault.