Drop developers
Idempotency
Delivery integrations should be retry-safe so network issues do not create duplicate operational work.
Retry-safe creation
Order creation should include a stable business reference so retries can be reconciled safely.
Duplicate prevention
Drop expects integrations to avoid repeated delivery requests for the same checkout or operational action.
Consistent reconciliation
Merchant systems should keep their own references aligned with Drop delivery references.
Support clarity
Stable references help support teams resolve issues without exposing unnecessary internal details.
Access notes
The exact retry headers and reference handling are part of the private implementation guide.
Do not place secrets or customer-private data in external references.
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.