Direct API Integration - Delivery Only

Modified on Fri, 31 Oct at 12:38 PM

This page explains the high-level path to integrate your system directly with Quiqup for last-mile delivery only. It’s a lightweight overview for non-developers. Your engineers should use our public API documentation for full details.

Developer docs: api-docs.quiqup.com

Who is this for?

Merchants who only need delivery (you handle your own pick/pack/warehouse).
Teams with an in-house or partner dev who can call REST APIs and consume webhooks. :contentReference[oaicite:2]{index=2}

What you get

Create delivery requests by API.
Labels & tracking links returned via API.
Live status updates via webhooks (e.g., ready_for_collection → out_for_delivery → delivery_complete).

Environments & Base URLs

Build and test in staging; switch to production when ready.

Purpose	Base URL	Notes
Staging / Sandbox	`https://api-staging.quiqup.com`	Mirrors production features, no real drivers or invoices. Ideal for test orders.
Production (UAE)	`https://api-ae.quiqup.com`	Switch here when you’re ready to ship live.

How the flow works (30-second version)

Order In – Your system creates a delivery request via API.
Label & Tracking – Fetch label and show customers the tracking link.
Status Updates – We push status changes to your webhook URL.

Heads-up: Events you’ll typically handle include ready_for_collection, collected, at_depot, out_for_delivery, delivery_complete, and delivery_failed. See full payloads in the API docs.

Onboarding checklist

Introduce your team – Email apisupport@quiqup.com with your store/brand, tech stack, target go-live date, loop in your account manager and contact emails.
Get sandbox credentials – We’ll reply with test keys and access notes.
Build & test in staging – Place a few test orders and share the test IDs.
Go live – We issue production keys and you switch the base URL to production.

When to choose another integration path

Shopify / WooCommerce: fastest self-serve connectors for SMBs. See their dedicated pages below.
Middleware (e.g., Carriyo): if you already route multiple carriers via a CMS/TMS.
Fulfilment API: if you also want storage and pick/pack (full-stack fulfilment). Page coming soon.

Support

API Support: apisupport@quiqup.com
Status & incidents: We’ll update you via email if any sandbox changes affect testing.

This page is a high-level guide only. Engineers should use api-docs.quiqup.com for endpoints, payloads, and examples.