For Agents
Generate shipping labels, request courier pickups, track parcels, and manage manifests across multiple Central and Eastern European couriers through a single Innoship integration.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Innoship 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: 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 | shStep 2: 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 instanceJentic 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.
What an agent can do with Innoship API.
Manage warehouse and fulfilment locations through /api/ClientLocation including courier-service availability per location
Compare and select couriers, then request pickup with /api/Courier/RequestPickup
Generate and download shipping labels by AWB number through /api/Label/by-courier/{courierId}/awb/{awb}
GET STARTED
Use for: I want to generate a shipping label for an order, Request pickup from a courier for a batch of parcels, Track the delivery status of a parcel by AWB, Compare courier prices for a shipment
Not supported: Does not handle warehouse management, inventory control, or customer-facing checkout — use for multi-courier label generation, pickup requests, parcel tracking, and shipping reconciliation only.
Jentic publishes the only available OpenAPI specification for Innoship API, keeping it validated and agent-ready. Innoship is a multi-courier shipping platform focused on Central and Eastern Europe that lets e-commerce merchants compare rates, generate AWB labels, request pickups, track parcels, and manage manifests across multiple national couriers from a single integration. The 51-endpoint API spans client locations, couriers, orders, offline orders, manifests, labels, tracking, vouchers, feedback, notifications, and pricing. Authentication is an API key in the X-Api-Key header.
Create and manage shipping orders, including offline orders for non-API origin systems
Track parcels and surface delivery status updates through the /api/Track endpoints
Generate manifests and feedback reports for reconciliation and dispute handling
Validate location details with /api/ClientLocation/Validate before generating shipments to reduce returns
Patterns agents use Innoship API for, with concrete tasks.
★ Multi-Courier Label Generation for E-Commerce
Generate AWB labels for any order against the cheapest or fastest courier from Innoship's pool, without integrating each courier's API individually. The order endpoints accept a shipment payload, return an AWB, and /api/Label/by-courier/{courierId}/awb/{awb} returns the printable label. Critical for Romanian and Central European merchants who routinely use 4-6 couriers.
Create a shipment for a 2 kg parcel from a warehouse to a Bucharest address, then GET /api/Label/by-courier/{courierId}/awb/{awb} to download the label.
Pickup Orchestration
Schedule courier pickups for batches of parcels from one or many locations. POST /api/Courier/RequestPickup tells the chosen courier to collect on the specified day from the configured client location. Saves merchants from logging into each courier's portal at end-of-day.
POST /api/Courier/RequestPickup with location ID, courier ID, and pickup date for a batch of 50 parcels.
Tracking and Customer Notifications
Surface live tracking status to customers and internal CS teams without scraping each courier's tracking site. The /api/Track endpoints return normalised statuses across the courier pool, and /api/Notifications drives delivery-event hooks. Reduces 'where is my order?' tickets and unifies the tracking experience across couriers.
GET /api/Track for AWB number 1Z999AA10123456784 and return the latest normalised delivery status.
Manifest and Reconciliation Reporting
Pull daily manifests, voucher data, and feedback (cost-vs-billed reconciliation) out of Innoship for accounting and operations review. /api/Manifest produces the daily collection record per courier; /api/Feedback/{from}/{to} returns the cost feedback between two dates. Useful for finance teams reconciling courier invoices against shipped volume.
GET /api/Feedback/2026-06-01/2026-06-30 to retrieve the previous month's shipment feedback and aggregate by courier.
AI Agent for Shipping Operations
An LLM agent acting as a logistics copilot uses Innoship to pick the right courier per order, generate labels, request pickups, and answer 'where is my parcel' from customers. Through Jentic, the agent searches by intent ('generate a shipping label', 'track a parcel') and executes — credential handling for the X-Api-Key is abstracted away.
For an order, POST a shipment to choose the cheapest courier, GET the label, and POST /api/Courier/RequestPickup for tomorrow's collection.
51 endpoints — jentic publishes the only available openapi specification for innoship api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/api/ClientLocation
Get details of client locations
/api/ClientLocation
Create a new client location
/api/Courier/RequestPickup
Request a pickup from a courier
/api/Courier/All
List all integrated couriers
/api/Label/by-courier/{courierId}/awb/{awb}
Get a shipping label by courier and AWB
/api/Feedback/{from}/{to}
Get shipment feedback between two dates
/api/ClientLocation/Validate
Validate location details before saving
/api/ClientLocation/Summary
Create a summary report for client locations
/api/ClientLocation
Get details of client locations
/api/ClientLocation
Create a new client location
/api/Courier/RequestPickup
Request a pickup from a courier
/api/Courier/All
List all integrated couriers
/api/Label/by-courier/{courierId}/awb/{awb}
Get a shipping label by courier and AWB
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Innoship X-Api-Key is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents call Innoship operations through scoped Jentic credentials and never hold the raw key, which matters for an API that can spend money by booking shipments.
Intent-based discovery
Agents search Jentic with intents like 'generate a shipping label' or 'track a parcel' and Jentic returns the matching Innoship operations with their input schemas — the agent does not have to navigate the operationId-style endpoint names like ClientLocation_createNew.
Time to first call
Direct Innoship integration: 1-2 days to handle the courier abstraction, label generation, and pickup booking flows. Through Jentic: under an hour — schema-first execution flattens the learning curve for the operationId-style API.
Alternatives and complements available in the Jentic catalogue.
Specific to using Innoship API through Jentic.
Why is there no official OpenAPI spec for Innoship API?
Innoship does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Innoship API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Innoship API use?
The Innoship API uses an API key in the 'X-Api-Key' header on every request. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at runtime so the agent never sees the raw value.
Can I generate labels and request pickups for multiple couriers from one integration?
Yes — that is Innoship's core value. /api/Courier/All lists the available couriers, the order endpoints accept the chosen courier, /api/Label/by-courier/{courierId}/awb/{awb} returns the label, and /api/Courier/RequestPickup schedules collection. One API key covers the whole courier pool.
What are the rate limits for the Innoship API?
Rate limits are not encoded in the spec; they depend on plan tier and are enforced per API key. Contact Innoship support for the per-second and daily limits applied to your account, particularly relevant during peak e-commerce seasons.
How do I track a parcel through Jentic?
Search Jentic for 'track a parcel with Innoship' to find the /api/Track endpoint. Load the schema, supply the AWB number, and execute. The response normalises status across the courier pool. Get started at https://app.jentic.com/sign-up.
Does Innoship support reconciliation against courier invoices?
Yes. GET /api/Feedback/{from}/{to} returns shipment-level cost feedback across a date range, which finance teams use to reconcile actual carrier invoices against the rates and surcharges Innoship recorded at shipment time.
/api/Feedback/{from}/{to}
Get shipment feedback between two dates
/api/ClientLocation/Validate
Validate location details before saving
/api/ClientLocation/Summary
Create a summary report for client locations