API Integration Endpoints

Environment	URL
Production	`https://prod.store-management.glovo.alb.app.onlineservice.io`

Integration, including testing against test stores, runs against this endpoint. Test stores are allocated in the same environment and are distinguished by configuration, not by address.

Partner Name (`partner_name`)

This field in the JSON payload identifies the POS solution in relation to the integration middleware.

Typically represents the name of the POS solution
Use a single partner_name within the system
Allocated when creating an account in the integration portal

Store ID (`store_id`) / LID

Uniquely identifies a Store in the Glovo system. Stores are defined at specific addresses.

LID Format: partner_name__store_id

partner_name — allocated by the portal at registration
store_id — provided by the POS solution when activating integration

Glovo location management:

Store — one per city
Store addresses — one for each physical location

Authorization Header

All requests to the integration APIs require an Authorization Header found in the integration portal.

http

Authorization: <api-key-value>

POS Endpoints

The integration solution can send various types of notifications. Endpoints are configured in the portal → POS Endpoint Management.

Marketplace Orders

Order delivery can be handled by a Glovo courier or by the restaurant. When Glovo is not involved in delivery, these stores are identified as "marketplace" type.

API Integration Endpoints ​

Partner Name (partner_name) ​

Store ID (store_id) / LID ​

Authorization Header ​