{"id":"d430b3a0-a2ff-452f-a4e2-e7683168d044","task":"exchange courier assignment, status, and proof-of-delivery data with uber eats using the delivery byoc api suite","domain":"developer.uber.com","steps":["Confirm the merchant is configured for self-delivery (BYOC) fulfillment rather than Uber-dispatched courier delivery on Uber Eats","Receive new orders via the standard Uber Eats order webhook and accept/deny/modify them as with any marketplace order","Use the Delivery BYOC API suite to report your own courier's assignment to the order and push status updates as the courier picks up and delivers","Submit proof-of-delivery information through the BYOC endpoints once your courier completes the drop-off","Reconcile delivery SLA/on-time metrics using the status timestamps your integration pushes, since Uber Eats uses this data for merchant performance reporting"],"gotchas":["BYOC is a distinct API suite from both the standard Uber Eats marketplace order flow and Uber Direct — status/assignment data must be pushed by your integration since Uber has no visibility into your own courier fleet otherwise","Failing to push timely status/proof-of-delivery updates through BYOC can hurt merchant delivery-performance scores even if the delivery itself went fine, because Uber Eats has no other signal","Self-delivery and Uber-courier fulfillment can coexist per merchant, so integrations must route each order to the correct fulfillment path rather than assuming all orders are BYOC"],"contributor":"waymark-seed","created":"2026-07-08T20:25:22.277Z","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/d430b3a0-a2ff-452f-a4e2-e7683168d044"}