ParcelParcel API

Name: ParcelParcel API API
Brand: ParcelParcel API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentLogisticsShippingapiKey4 EndpointsREST

For Agents

Compare shipping rates, create shipments, track parcels, and retrieve labels across 4 endpoints with multi-carrier support.

Connect the ParcelParcel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ParcelParcel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ParcelParcel API API.

Compare shipping options with rates and transit times from multiple carriers

Create draft shipments or book directly with carriers

Track shipments by tracking number across carriers

Retrieve shipping labels and documents (PDF, PNG, ZPL formats)

GET STARTED

Start building with ParcelParcel API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ParcelParcel API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ParcelParcel API, keeping it validated and agent-ready. The ParcelParcel API provides shipping rate comparison and shipment management for international and domestic parcel delivery across multiple carriers (FedEx, DHL, TNT, DPD, DSV, Skynet). It powers e-commerce shipping, rate shopping, label generation, and tracking workflows.

Use Cases

Patterns agents use ParcelParcel API API for, with concrete tasks.

★ Multi-Carrier Rate Shopping

Compare shipping rates and transit times from multiple carriers (FedEx, DHL, TNT, DPD, DSV, Skynet) in a single request. POST /rates accepts parcels array, origin/destination (country, zipcode, city), insurance flag, and totalValue, returning sorted shipping options with price, estimatedTransitTimeInWorkingDays, and priceBreakdown.

POST /rates with parcels, fromCountry, toCountry, and optional insurance/totalValue to compare rates

Shipment Creation with Labels

Create draft or confirmed shipments with label generation. POST /shipments accepts productId (from rates), from/to addresses, parcels array, and optional reference number, returning shipmentId, trackingNumber, carrier, and status. Retrieve labels via GET /documents/{shipmentId}.

POST /shipments with productId and addresses, then GET /documents/{shipmentId} for PDF/PNG/ZPL labels

Shipment Tracking

Track shipments across carriers by tracking number. GET /tracking/{trackingNumber} returns carrier, status, and events array with timestamp, location, and description for each tracking update. Essential for customer notifications and delivery monitoring.

GET /tracking/{trackingNumber} to retrieve status and event timeline

Pallet and Document Shipping

Support multiple parcel types (NONDOC for parcels, DOC for documents, PALLET for pallets) with type-specific requirements. PALLET requires weight, dimensions, stackable flag, and recipientType (individual/business). DOC type requires only count. NONDOC requires weight and dimensions.

POST /rates with parcels[type=PALLET] including weight, dimensions, stackable, and recipientType

Agent-Driven Shipping Automation via Jentic

An AI agent managing e-commerce fulfillment can compare rates, book shipments, and track deliveries through Jentic without exposing the X-PP-API key in agent context. Jentic resolves intents like 'get cheapest shipping' to the right ParcelParcel endpoint.

Search Jentic for 'compare shipping rates', load the POST /rates schema, and execute

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for parcelparcel api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/rates

Compare shipping options with rates and transit times

POST

/shipments

Create draft shipment or book with carrier

GET

/tracking/{trackingNumber}

Track shipment by tracking number

GET

/documents/{shipmentId}

Get shipping labels and documents

POST

/rates

Compare shipping options with rates and transit times

POST

/shipments

Create draft shipment or book with carrier

GET

/tracking/{trackingNumber}

Track shipment by tracking number

GET

/documents/{shipmentId}

Get shipping labels and documents

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ParcelParcel's X-PP-API key is stored encrypted in the Jentic vault and injected at execution time. Agents receive scoped access — the raw key never enters agent context.

Intent-based discovery

Agents search by intent (e.g. 'compare shipping rates', 'create shipment') and Jentic returns the matching ParcelParcel endpoint with the request schema pre-shaped for execution.

Time to first call

Direct ParcelParcel integration: 2-5 days including API key setup, understanding parcel types, and handling multiple carriers. Through Jentic: under 1 hour once credentials are configured — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shippo API

Multi-carrier shipping API with extensive carrier coverage and address validation

Choose Shippo API when the workflow requires US carrier coverage (USPS, UPS) or address validation features

Alternative

Easyship API

Global shipping platform with rates, labels, tracking, and customs documentation

Choose Easyship API when the workflow requires automated customs documentation or duty/tax calculation

Complementary

FedEx API

Direct FedEx integration for advanced features and negotiated rates

Use FedEx API directly alongside ParcelParcel when you need FedEx-specific features like hold-at-location

FAQs

Specific to using ParcelParcel API API through Jentic.

Why is there no official OpenAPI spec for ParcelParcel API?

ParcelParcel does not publish a complete OpenAPI specification for their Partners API. Jentic generates and maintains this spec so that AI agents and developers can call ParcelParcel API via structured tooling. Get started at https://app.jentic.com/sign-up.

What authentication does the ParcelParcel API use?

ParcelParcel API uses an API key passed in the X-PP-API header in format: api-key@api-secret. Through Jentic, the key is stored in the encrypted vault and injected at execution time so it never enters the agent's prompt context.

Which carriers does ParcelParcel support?

ParcelParcel supports FedEx, DHL, TNT, DPD, DSV, and Skynet. POST /rates returns options from all available carriers for the specified route, enabling multi-carrier rate comparison in a single request.

How does insurance work?

Set insured=true and provide totalValue (in euros) in POST /rates to include insurance costs in the returned prices. The price field includes insurance if applicable, and priceBreakdown shows insurance as a separate component.

What parcel types are supported?

ParcelParcel supports three parcel types: NONDOC (parcels with weight and dimensions), DOC (documents with count only), and PALLET (pallets requiring weight, dimensions, stackable flag, and recipientType).

What label formats are available?

GET /documents/{shipmentId} returns shipping labels in PDF, PNG, or ZPL formats. ZPL is for thermal printers, PDF for standard printers, and PNG for web display or printing.