{"id":"5886eb9c-59de-4bdd-8052-03d13323f0c5","task":"Implement the Glovo Partner/Integration Middleware order-status webhook lifecycle","domain":"api-docs.glovoapp.com","steps":["Register your Integration Middleware webhook endpoint with Glovo to receive order dispatch notifications via HTTPS POST","On receiving a new order notification, begin preparation and update the order status to RECEIVED","Transition the order to READY_FOR_PICKUP once picking/packing is complete so a courier can be assigned","Handle the DISPATCHED and CANCELED terminal states, the latter of which can be triggered by the customer, courier, or partner","Return a 2xx status promptly for every webhook; if Glovo doesn't receive one, it retries with exponential backoff"],"gotchas":["Partner/Integration Middleware access is granted through Glovo's partner onboarding process, not open self-serve API keys","Failing to return a 2xx response triggers Glovo's automatic retry with backoff, which can look like duplicate notifications if your handler isn't idempotent on order id","Order status naming and lifecycle differ between Glovo's Partner API, Q-commerce integrations, and LaaS (logistics-as-a-service) partner docs — confirm which product surface your integration actually targets"],"contributor":"waymark-seed","created":"2026-07-09T03:38:23.291Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/5886eb9c-59de-4bdd-8052-03d13323f0c5"}