parcelLab
parcelLab is a Munich-headquartered post-purchase experience platform (parcelLab GmbH) used by retailers including IKEA, Hugo Boss, Dyson, Puma, and John Lewis to turn delivery and returns into a branded, revenue-generating part of the customer journey. The platform spans four modules — Convert (pre-checkout delivery promise), Engage (multichannel post-purchase communications), Retain (Returns Portal and returns experience), and Insights (analytics, benchmarking, control tower) — layered with AI agents (WISMO/R, Insights, Fraud & Abuse) and exposed via the parcelLab API v4 Enhanced. Global, EU, and US regional endpoints are available; the same data backs a Model Context Protocol server at agents.parcellab.com/mcp/ for agentic clients.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles parcelLab the way a machine reads it — 77 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — parcelLab scores 72.1/100 (exemplar), with a separate agent-readiness read of 56/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile parcelLab
Each block below is one kind of artifact we hold for parcelLab. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
parcelLab MCP Server
Hosted Model Context Protocol server exposing the parcelLab order tracking and returns registration workflow to MCP-compatible agents, authenticated via OAuth 2.1 bearer tokens ...
parcelLab Campaigns API
Evaluate campaign targeting and redirect analytics events.
parcelLab Events API
Send custom shop or warehouse events into the tracking timeline.
parcelLab Orders API
Create, update, and inspect orders and their trackings.
parcelLab Place Info API
Look up nearby pickup and drop-off (PUDO) locations.
parcelLab Promise API
Pre-checkout delivery date predictions.
parcelLab Returns API
Return registrations, configurations, and document templates.
parcelLab Surveys API
Retrieve survey definitions and submit responses.
Scroll within the panel for all 8 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
parcelLab API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
parcelLab API
OPEN COLLECTIONArazzo Workflows 11
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
parcelLab Create and Fetch Return
Create a return registration and immediately read it back by external id.
ARAZZOparcelLab Evaluate Campaign and Log Redirect
Evaluate campaign targeting for a tracking, then record a redirect analytics event.
ARAZZOparcelLab List and Get Return
List return registrations for an account, then fetch the first one in detail.
ARAZZOparcelLab Predict Delivery and Create Order
Get a pre-checkout delivery prediction, then create the order it describes.
ARAZZOparcelLab PUDO Lookup and Register Return
Find a nearby drop-off point, then open a return registration for the order.
ARAZZOparcelLab Register Return and Collect Survey
Create a return registration, then submit a survey response tied to it.
ARAZZOparcelLab Resolve Config and Register Return
Resolve a return configuration for an account, then register a return with it.
ARAZZOparcelLab Send Event and Refresh Status
Push a warehouse or shop event into the timeline, then refresh the order status.
ARAZZOparcelLab Survey Fetch and Submit
Load a survey, fetch its prefilled answers for a reference, then submit a response.
ARAZZOparcelLab Track and Target Campaign
Read an order's tracking status, then evaluate a campaign for that tracking.
ARAZZOparcelLab Create Order and Track
Create or update an order, then retrieve its latest tracking and checkpoints.
ARAZZOScroll within the panel for all 11 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Parcellab Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Parcellab Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Delivery Promise
Pre-checkout delivery date prediction (Promise API) to drive cart conversion.
Order & Tracking Ingestion
Idempotent v4 Orders API with mutations to add/cancel trackings or amend line items.
Carrier Network
Integrations with 450+ carriers worldwide via direct carrier interfaces.
Returns Portal
Branded self-service returns portal with refund options, exchanges, retention offers, split returns, and claims.
Multichannel Communications
Email, SMS, Push, Webhook, and Order Status Page delivery of branded post-purchase messages.
Apple Wallet Tracking
Native Apple Wallet passes for order tracking.
AI Agents
WISMO/R Agent, Insights Agent, and Fraud & Abuse Insights powered by ML over post-purchase data.
Insights & Benchmarking
Trackings Insights, Communication Insights, Control Tower, Logistics Analysis, and Benchmarking dashboards.
Surveys & NPS
Embedded surveys and NPS feedback tied to deliveries or return registrations.
MCP Server
Hosted Model Context Protocol server (agents.parcellab.com/mcp/) for agentic order tracking and return registration workflows.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Parcellab Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
parcelLab API Rules
SPECTRALparcelLab API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
parcelLab Address
JSON SCHEMAparcelLab Line Item
JSON SCHEMAparcelLab Order
JSON SCHEMAparcelLab Promise Prediction
JSON SCHEMAparcelLab Return Registration
JSON SCHEMAparcelLab Tracking
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Parcellab Order Structure
JSON STRUCTUREParcellab Return Registration Structure
JSON STRUCTUREExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
WISMO Reduction
Cut "Where Is My Order" support contacts by proactively communicating tracking updates.
Returns as Retention
Convert returns into exchanges, store credit, or retention offers to keep revenue.
Cart Conversion
Display a delivery promise at checkout to reduce abandonment.
Cross-Border Returns
Provide customs handling and Global-e integration for unified cross-border returns.
Carrier Performance Benchmarking
Compare lead-times, exceptions, and on-time rates across the carrier portfolio.
Marketing in the Delivery Window
Embed branded campaigns and product recommendations in delivery communications.
Integrations 12
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Shopify
Native Shopify integration for tracking, communications, and returns.
Magento 2
Webhook extension for Magento 2 storefronts.
Shopware
Embedded Order Status Page for Shopware shops.
Klaviyo
Route post-purchase email through Klaviyo journeys.
Postscript
Route post-purchase SMS through Postscript.
Zendesk
Customer service ticket sidebar with parcelLab tracking data.
Gorgias
Helpdesk widget displaying order and tracking data.
Kustomer
Helpdesk app for parcelLab delivery context.
Salesforce Service Cloud
Customer Service Integration surfacing parcelLab data in SFSC.
Global-e
Unified cross-border returns experience.
Apple Wallet
Native order tracking passes in Apple Wallet.
Poshmark
List non-returnable items directly from the Returns Portal onto Poshmark.
Scroll within the panel for all 12 ·
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Convert
Pre-checkout delivery promise module.
Engage
Multichannel post-purchase communication module.
Retain
Returns Portal and returns experience module.
Insights
Analytics, benchmarking, and control tower module.
AI Agents
Add-on autonomous agents for WISMO/R, insights, and fraud.
Resources
Every other property we hold for parcelLab — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/parcellab · machine-readable index on apis.io