Integrate delivery operations through one API and one console.
Drop should feel like a payments-style platform for delivery: machine authentication, a unified Orders API, signed webhooks, and an operational console for credentials and visibility.
What merchants integrate
Token request
POST /oauth/token
Create order
POST /v1/orders
Retrieve order
GET /v1/orders/:id
Find by reference
GET /v1/orders?reference=...
Webhook testing
POST /v1/webhooks/test
Client credentials auth
Portal users authenticate as humans in Drop Console. Merchant systems authenticate separately through API apps and bearer tokens.
Unified Orders API
Use one POST /v1/orders endpoint for website, app, POS, marketplace, or social orders. Source differences belong in metadata, not separate APIs.
Signed webhooks
Receive asynchronous lifecycle updates back into your systems and verify signatures before processing events.
Operational visibility
Use the portal for credentials, webhook endpoints, logs, and merchant operations while the API remains the source of truth.
Client credentials auth
Portal users authenticate as humans in Drop Console. Merchant systems authenticate separately through API apps and bearer tokens.
Unified Orders API
Use one POST /v1/orders endpoint for website, app, POS, marketplace, or social orders. Source differences belong in metadata, not separate APIs.
Signed webhooks
Receive asynchronous lifecycle updates back into your systems and verify signatures before processing events.
Operational visibility
Use the portal for credentials, webhook endpoints, logs, and merchant operations while the API remains the source of truth.
Current posture
Drop Console already supports merchant onboarding, API app creation, webhook setup, and logs. The public developer surface should direct engineers into that flow instead of pretending the product is only a brochure site.