Qapla'
Log in
Qapla'

APIs and webhooks for shipments, labels and tracking

REST API with one key per channel and a sandbox. Webhooks notify your systems at every status change, with the same statuses for all couriers. And if your AI writes the integration, there is the qapla-api skill.

Public documentation Sandbox for every channel Webhooks in all plans
Animation: a request to the Qapla' API reads a Courier 1 shipment and receives the normalised status; shortly after, a webhook arrives with the change to Out for delivery.
REST and JSON
HTTPS calls, JSON responses.
One key per channel
Every store or channel has its own API key.
Sandbox
The same endpoint, with the test flag.
9 standard statuses
The same for 450+ couriers.

What you can do with the Qapla' APIs

The whole shipment cycle, from order to delivery. For each group of endpoints, you can see the plan it is available on.

AreaWhat you doExamplesPlan

Tracking

Read the status of every shipment, with the same statuses for all couriers and the event history.

getShipmentgetQaplaStatus All plans

Webhook

Receive a call at every status change, without querying the couriers.

status_change All plans

Quotes and rates

Compare the rates in your courier contracts before creating the shipment.

quote From Plus

Shipments and labels

Create shipments and labels with the courier you choose, as PDF or ZPL.

pushShipmentlabel Qapla' One

Order import

Bring orders into Qapla' from custom channels, business software and ERP.

pushOrder Qapla' One

Pickup points and addresses

Find pickup points near your customer and check addresses before shipping.

pickupPointsaddress Pay per use

Method names and full parameters are in the API 1.3 documentation.

Webhooks: the status comes to you, already translated

You register a URL and Qapla' calls it at every status change. You do not query 450+ couriers with different formats: you always receive one of the 9 standard statuses, with the detail when there is an exception.

  • Waiting for pick-up
  • Departed
  • In transit
  • Out for delivery
  • Failed delivery attempt
  • Delay
  • Exception
  • Pickup point
  • Delivered

Business software, ERP, marketplaces or helpdesks update themselves. For the status inside tickets there is also Qapla' Companion, with no code.

Webhook documentation
POST https://yourstore.com/qaplaapplication/json
{
"event": "status_change",
"reference": "10493",
"courier": "Courier 1",
"courierStatus": "Delivery attempt failed: recipient absent",
"qaplaStatus": "On hold",
"exception": "recipient absent",
"date": "2026-10-16 09:12"
}

From sandbox to production, without rewriting

Test everything with the sandbox flag, then change the key. The endpoints and responses stay the same.

Sandbox

For testing
Key
Channel API key
Flag
sandbox on
Shipments
No real shipments
Webhook
Sent to your test URL

Production

Live
Key
Production API key
Flag
sandbox off
Shipments
Real, under your contracts
Monitoring
Calls and errors from the panel
Animation: in the terminal, Claude is asked to integrate Qapla' tracking; the assistant reads the qapla-api skill, creates the client, sets up the webhook and passes the sandbox tests.

Your AI can write the integration

Two tools, for two different jobs.

Skill qapla-api
A public skill that explains endpoints, authentication, examples and errors to your assistant. You give it the task, and it writes the client and the tests.
MCP server
The open standard for connecting Claude, ChatGPT or your own agents to the data in your Qapla’ account, with its own credentials. From the Plus plan.
Explore AI and Agents

Frequently asked questions

Are Qapla' APIs included in the plans?

Tracking and webhooks are included in all plans. Comparing rates via API starts with the Plus plan; creating shipments and labels and importing orders via API are in Qapla’ One. Searching for pickup points and checking addresses are pay per use.

Yes. Each channel has its own API key, and with the sandbox flag you test calls without creating real shipments. In production only the key and the flag change: the endpoints stay the same.

You register a URL and Qapla' calls it at every shipment status change, with the status already normalised for all couriers. Your business software, ERP or helpdesk updates without querying the couriers.

Yes. The public qapla-api skill explains endpoints, authentication, examples and errors to your AI assistant. With the MCP server, Claude, ChatGPT or your own agents read your account data with its own credentials.

No. With the 16 native eCommerce platforms you connect your store without writing code. The APIs are for custom channels, business software, ERP or workflows you want to automate.

Integrate Qapla’ this afternoon

Public documentation, a sandbox for every channel, a skill for your AI.

Several brands, ERP or high volumes? Talk to the Qapla' One team