Drop developers
Create order
Approved integrations can create delivery requests using Drop-controlled validation, pricing, and operational rules.
Validated delivery details
Drop expects clear pickup, delivery, package, contact, and channel information before a delivery can move forward.
Pricing and payment gates
Delivery creation follows Drop pricing, account, billing, and payment rules instead of bypassing dispatch controls.
Idempotent submission
Integrations should be designed so retries do not accidentally create duplicate delivery requests.
Operational ownership
Every order belongs to a verified Drop account so support, tracking, and billing stay accountable.
Access notes
Public docs do not publish request bodies or production endpoint examples.
Approved merchants receive field-level guidance after integration access is enabled.
Private implementation
Need the full integration guide?
Detailed request examples, credentials, webhook verification material, and production setup steps are shared only inside verified Drop accounts.
