domain: glovoapp.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API access and credentials through your Glovo account manager or via the Glovo QCommerce integration portal at qcommerce-integrations.glovoapp.com
Use the provided credentials to authenticate against the Glovo Partner API production base URL https://glovo.partner.deliveryhero.io
Implement the order receive webhook on your end; Glovo POSTs incoming orders to your registered endpoint in real time
Acknowledge each received order by calling POST /v2/orders/{order_id} with a status update (e.g., accepted) within the required response window
Keep your product catalog current by using the catalog management endpoints to create, update, and delete products and categories
Handle cancellation and error events from Glovo's webhook stream; respond with HTTP 200 to all webhook deliveries regardless of internal processing status
Known gotchas
Glovo's partner integration is operated under the Delivery Hero infrastructure since the acquisition; some documentation and base URLs reference deliveryhero.io — this is expected
Failing to acknowledge an order within Glovo's acceptance window causes it to be marked as rejected automatically, which negatively impacts the restaurant's reliability metrics
Catalog updates may not be immediately reflected on the customer-facing app; allow for propagation time and do not assume real-time consistency after a catalog write
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?