Drop developers

Integration paths

Use a store connector when Shopify or Wix is the source of customer orders. Use the native API when you own the website, app, marketplace or backend that creates delivery requests.

Connectors are configured from the Drop portal. Native integrations create an API app there, then use the OAuth and Orders API shown in this guide. Both paths keep delivery status, account ownership and tracking in Drop.

Preview a delivery price before checkout

bash

curl -X POST https://api.dropsa.co.za/v1/pricing/quote \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "pickupLat": -26.107,
    "pickupLng": 28.056,
    "dropoffLat": -26.083,
    "dropoffLng": 28.045,
    "serviceType": "SAME_DAY",
    "packageSize": "SMALL",
    "packageWeightKg": 1.2
  }'

Quote response shape

json

{
  "request_id": "req_01HXYZ...",
  "quote": {
    "merchantPrice": 89.5,
    "driverPayout": 63.0,
    "currency": "ZAR"
  }
}

Implementation notes

Shopify and Wix connectors use your verified pickup store and are configured in the Drop portal.
Native API integrations use the same order model regardless of whether the source is a custom store, marketplace, POS or mobile app.
Do not expose client secrets or bearer tokens in browser checkout code.