Drop developers
Errors
Drop integrations should handle validation, account, billing, and operational errors clearly.
Validation issues
Invalid addresses, missing contacts, incomplete package data, and unsupported service areas should be corrected before dispatch.
Account restrictions
Some actions require verified account ownership, active credentials, or approved merchant setup.
Payment and billing gates
Delivery creation may pause until payment, invoice approval, or account billing rules are satisfied.
Operational exceptions
Driver, pickup, delivery, and customer-contact issues should be surfaced through authenticated support workflows.
Access notes
Public docs do not publish internal error codes or implementation-specific response structures.
Approved integrations receive the error handling contract privately.
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.