CargoMov logo
CargoMov
CargoMov Developers

Connect your business to CargoMov delivery operations.

Create delivery requests, follow live workflow status, retrieve invoices and prepare a controlled webhook destination from one integration.

Create a delivery request
curl -X POST "$CARGOMOV_API_URL/jobs" \
  -H "Authorization: Bearer $CARGOMOV_API_KEY" \
  -H "Idempotency-Key: order-4821" \
  -H "Content-Type: application/json" \
  -d '{
    "pickupLocation": "Osu, Accra",
    "dropoffLocation": "Community 25, Tema",
    "cargoType": "Packaged food",
    "requiredVehicleType": "Pickup"
  }'
Partner API routes become available after the Firebase Functions deployment. Webhook endpoints can be registered and test events can be queued, but outbound transmission remains off until CargoMov authorizes that exact destination.
CargoMov Merchant API

Build delivery directly into your online store.

Use authoritative quotations, verified payments, idempotent shipment creation, customer-safe tracking and signed delivery webhooks from one store-bound integration.

Real-time store quotations
Server-side payment verification
Duplicate-safe shipment creation
Signed webhook delivery

Create and track jobs

Post idempotent delivery requests and read account-owned tracking status.

Controlled webhook setup

Register an HTTPS destination, protect its signing secret and queue test events for review.

Scoped credentials

Approve only the permissions each integration needs and revoke access immediately.

Activation-aware queue

Inspect queued events while CargoMov keeps transmission disabled until the exact destination is authorized.

Approved access

Start securely

1

Sign in to an approved Business or Corporate account.

2

Describe the integration and request the required API scopes.

3

Wait for CargoMov Admin approval, then claim the API key once.

4

Register an HTTPS webhook endpoint and safely store its signing secret.

Webhook readiness

Prepare to verify every CargoMov event

After CargoMov activates an authorized destination, the exact request body will be signed with the endpoint secret. Verify the timestamp and HMAC-SHA256 signature before processing an event, then retain its event ID to make repeated delivery safe.

HMAC_SHA256(secret, timestamp + "." + rawBody)
Constant-time signature comparisonFive-minute replay windowIdempotent event processing
Need integration support? Contact CargoMov