canonical: https://jentic.com/apis/easypack24.net/easypack24

# Easypack24 InPost ShipX API

The InPost ShipX API creates and manages parcel shipments routed through InPost's automated parcel lockers and pickup-drop-off points. It finds nearby points, creates locker-to-locker, hub-to-locker, and label-less shipment variants for an organization, edits a shipment's reference, generates shipping labels, and tracks a parcel by its tracking number. It also returns the full set of tracking statuses a shipment can move through. It is aimed at online stores and logistics tools that offer InPost delivery at checkout and need to automate label generation and tracking.

## For AI agents

Create and track InPost parcel shipments: search lockers and pickup points, create shipments for an organization, edit references, generate labels, and track parcels by tracking number.

## Scope

Does not handle payment collection, warehouse inventory, or returns refunds. Use for InPost parcel shipments, labels, and tracking only.

## Capabilities

- Find InPost parcel lockers and pickup-drop-off points, optionally filtered by postal code
- Create locker-to-locker, hub-to-locker, and label-less shipments for an organization
- Generate a shipping label for a created shipment
- Track a parcel by its tracking number and read its current delivery status
- Edit a shipment's reference after it has been created
- List the full set of tracking statuses a shipment can move through

## Use cases

### Agent-driven checkout fulfillment

An AI agent handling order fulfillment can call the InPost ShipX API through Jentic to look up the locker a customer chose at checkout, create the shipment for the store's organization, and generate the label to hand to the warehouse. Jentic returns the create-shipment operation from a natural-language query, so the agent builds the shipment without reading the ShipX reference first.

Example prompt: Find the InPost point matching the customer's chosen locker, create a locker-to-locker shipment for the organization, and generate its shipping label.

### Parcel tracking and status updates

Track a parcel by its tracking number and map its current state against the full list of tracking statuses the API publishes. Stores use this to push accurate delivery updates to customers and to flag parcels stuck in a locker before a return is auto-triggered.

Example prompt: Look up the parcel by its tracking number, compare its state against the published tracking statuses, and report whether it has been collected.

### Locker selection at checkout

Search for InPost parcel lockers and pickup-drop-off points near a delivery address, optionally narrowing by postal code, so a storefront can show the customer the closest collection options. The points lookup is a public endpoint, so the map can load before the shopper signs in.

Example prompt: Search the points endpoint for lockers near the delivery postal code and return the three closest collection points.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/points` | Search for parcel lockers and pickup-drop-off points |
| POST | `/v1/organizations/{organization_id}/shipments` | Create a shipment for an organization |
| GET | `/v1/organizations/{organization_id}/shipments` | List an organization's shipments |
| PUT | `/v1/shipments/{shipment_id}/attributes` | Edit a shipment's reference |
| GET | `/v1/shipments/{shipment_id}/label` | Generate a shipping label for a shipment |
| GET | `/v1/tracking/{tracking_number}` | Track a parcel by its tracking number |
| GET | `/v1/statuses` | List the available shipment tracking statuses |

## Key resources

- **Points** — Search for parcel lockers and pickup-drop-off points, optionally by postal code
- **Shipments** — Create organization shipments in locker-to-locker, hub-to-locker, and label-less variants and edit their references
- **Labels** — Generate the shipping label for a created shipment
- **Tracking** — Track a parcel by tracking number and read the available tracking statuses

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 56 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 46 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 41 / 100
- **View full report:** https://jentic.com/apis/easypack24.net/easypack24/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the InPost ShipX API by hand means handling its bearer token, choosing the staging or production ShipX host, and coding the different locker-to-locker and hub-to-locker shipment variants yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** ShipX puts the organization and shipment ids in the URL path, so a rule can bound your agent to the operations it needs, such as point lookup and tracking. You choose which operations it may call, so the create-shipment and label operations are not included unless you add them.
- **Credential handling:** Your InPost token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a parcel shipment' or 'track a parcel', and Jentic returns the matching InPost ShipX operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Shippo external API** — Multi-carrier shipping API for rates, labels, and tracking
- **AfterShip Shipping API** — Cross-carrier tracking and delivery notifications
- **DHL Shipment Tracking - Unified API** — DHL's unified parcel tracking across its networks

## FAQ

### Is there an InPost ShipX API MCP server?

You do not need an MCP server to give your agent the InPost ShipX API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the point lookup, shipment, label, and tracking operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

### What authentication does the InPost ShipX API use?

The shipment, label, and organization operations require a bearer token per the OpenAPI spec, while the point lookup, tracking, and status endpoints are public and need no credential. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an authenticated call runs, so it never reaches the agent's context.

### Can I track a parcel with the InPost ShipX API?

Yes. The tracking endpoint returns the current state of a parcel by its tracking number, and a separate statuses endpoint lists every state a shipment can move through so you can interpret the result. Both are public, so tracking lookups work without a token.

### What are the rate limits for the InPost ShipX API?

The OpenAPI spec does not specify rate limits. Limits depend on your InPost organization agreement, so confirm the per-second and daily caps for your account in the InPost ShipX developer documentation at https://docs.inpost.pl.

### Can I limit what my agent is allowed to do with the InPost ShipX API?

Yes. Write a rule that permits only the read operations, point lookup and tracking, when the agent should quote and track deliveries, and add the create-shipment and label operations only for workflows that actually dispatch parcels, with every call logged.

### How do I create an InPost shipment through Jentic?

Search Jentic for 'create a parcel shipment' to surface the shipment operations, load the input schema, pass the organization, sender, and chosen point, and execute, then call the label operation for the returned shipment. To run it on your own infrastructure, install Jentic One from its GitHub repo.