Install
$ agentstack add skill-qapla-qapla-api-skill-qapla-api-skill ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Qapla' Public API (v1.3)
This skill teaches you to integrate with the public REST API of Qapla', a SaaS platform for e-commerce logistics (multi-carrier shipping, real-time tracking, label printing, transactional notifications).
How to use this skill
- Read
references/overview.mdfirst — it is the canonical orientation:
core facts (base URL, auth, response envelope, rate limit, sandbox, versions), the domain model, and the "which endpoint do I need?" decision rule.
- Then read
references/conventions.mdandreferences/authentication.md—
they apply to every call.
- Pick the endpoint from
references/endpoints.md(full catalog) or the
per-endpoint deep-dives (references/pushshipment.md, pushorder.md, createlabel.md, getquotes.md, getpudos.md, trackingbytimeframe.md — the pull alternative to webhooks — and apivirtual.md — the virtual courier). To receive event callbacks instead of calling an endpoint, see references/webhooks.md (Pillar 2). To interpret tracking statuses, see references/statuses.md (branch on the canonical id, never the label). For the version policy (which version to call, v1.2-only endpoints, the separate v2 generation), see references/versioning.md; to upgrade a legacy integration, see references/migration.md.
- Use the runnable example payloads in
references/examples/as a starting
point, and the dependency-free reference client in scripts/qapla_client.py when writing code.
- For the v2 API (a separate, RESTful generation with Bearer/JWT auth — the
direction the platform is heading), start at references/v2/overview.md, then references/v2/authentication.md and the resource deep-dives (references/v2/parcels.md, references/v2/sandbox.md, references/v2/couriers.md — delivery-time/efficiency-index benchmarks, references/v2/stock-release.md — release a shipment held in depot, references/v2/endpoints.md). Most integrations still target v1.3 today; use v2 when you need a resource it exposes (e.g. parcels) or its model.
> The same knowledge powers the cross-agent entrypoints in this repo > (AGENTS.md, .cursor/rules/qapla-api.mdc); all of them point back to > references/overview.md so there is a single source of truth.
> Source of truth: the live docs at . This skill > mirrors them so you can work offline; if anything drifts, trust the live docs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Qapla
- Source: Qapla/qapla-api-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.