This page explains how to connect your system directly to Quiqup’s Fulfilment API so you can send orders to our warehouses for picking, packing, and delivery. It’s a high-level overview for non-developers. Your engineering team should use the full documentation below for technical details.
Developer docs: developer-docs.quiqup.com
Who is this for?
- Merchants who store products in a Quiqup fulfilment centre (we handle storage, picking, packing, and delivery).
- Teams with an in-house or partner developer who can connect to REST APIs and handle webhooks and do not want to or can't use our default connections that we offer through Shopify or WooCommerce.
- Businesses that want to keep their product catalog, inventory, and order status in sync automatically.
What makes this different from Delivery-Only API?
- You’re not just sending a shipment request — you’re sending a fulfilment order for our warehouse to pick, pack, and ship.
- You can sync your product catalog (SKUs, HS codes, country of origin, pricing, etc.).
- You can view live inventory from our warehouse to stay aligned on stock levels.
- Delivery status webhooks remain the same — you’ll still get updates like
picked,at_depot,out_for_delivery,delivered, etc.
Key Endpoints
| Category | Purpose | Example Endpoint |
|---|---|---|
| Authentication | Get an OAuth2 access token with your client_id and client_secret. | POST /oauth/token |
| Products | Create, update, or fetch your products so we can pick and pack them. | POST /api/fulfilment/products |
| Inventory | Read current stock levels for each SKU (read-only). | GET /api/fulfilment/inventory |
| Orders | Create or update fulfilment orders that we’ll pick, pack, and ship. | POST /api/fulfilment/orders |
See full endpoint details and payload examples in our developer documentation.
Environments & Authentication
| Purpose | Base URL | Notes |
|---|---|---|
| Staging / Sandbox | https://platform-api.staging.quiqup.com | Use for testing. Tokens last ~1 hour. |
| Production | https://platform-api.quiqup.com | Use after successful staging tests. Tokens last ~7 days. |
Authentication uses OAuth2 (Client Credentials). Handle token refresh automatically.
How the flow works (overview)
- Authenticate – Get a bearer token using your client credentials.
- Sync your catalog – Create each product (SKU, barcode, HS code, country of origin, price) in Quiqup’s warehouse system.
- Check inventory (optional) – Query live stock levels if you want to display availability in your own system.
- Create a fulfilment order – Send order details (line items, quantities, customer info, delivery address, notes).
- Track order status – Receive automatic webhooks when the order status changes (Picked → At depot → Out for delivery → Delivered).
Heads-up: Webhook events mirror the delivery-only API, so you can reuse the same callback URL for both. See payload examples in the docs.
Onboarding checklist
- Introduce your team – Email apisupport@quiqup.com with your company name, tech stack, go-live target date and also that you want integrate our fulfilment API as this setup is a bit more involved so we can setup your test account properly!
- Get sandbox credentials – Our team will issue a
client_idandclient_secretfor testing. - Build & test – Use staging to create products, orders, and verify webhook delivery.
- Go live – Once validated, we’ll issue production credentials and activate your fulfilment warehouse connection.
Suggested test plan
- Create 1–2 products with barcode, HS code, and country of origin.
- Create a fulfilment order using those SKUs.
- Verify that your system receives webhook updates for each status change.
When to choose another integration path
- Delivery-Only API: If you handle your own storage and packing, and only need Quiqup for last-mile delivery.
- Shopify / WooCommerce connectors: Fastest self-serve option for small-medium e-commerce stores.
- Middleware (Shipsy, Carriyo, etc.): If you already manage multiple carriers through a single system.
Support
- API Support: apisupport@quiqup.com
- Documentation: developer-docs.quiqup.com
- Status & incidents: We’ll notify you if any sandbox changes affect integration testing.
This page is a high-level overview. Engineers should follow the full technical reference at developer-docs.quiqup.com for endpoints, payloads, and examples.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article