For Agents
Create, validate, and cancel FedEx shipments and manage tags for FedEx Express and Ground services through a bearer-authenticated REST API.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FedEx Ship 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 FedEx Ship API API.
Create FedEx Express and Ground shipments and receive label data
Validate a shipment payload before booking to catch address and rule errors
Retrieve the result of an asynchronous shipment job by jobId
Cancel a shipment using its tracking number
GET STARTED
Use for: I need to create a FedEx shipment and get the label, Validate a FedEx shipment request before submitting it, Cancel a FedEx shipment by tracking number, Retrieve the result of an asynchronous FedEx ship job
Not supported: Does not handle freight bookings, billing reconciliation, or rate quoting — use for FedEx Express and Ground shipment creation, validation, cancellation, and tag management only.
Jentic publishes the only available OpenAPI document for FedEx Ship API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for FedEx Ship API, keeping it validated and agent-ready. The FedEx Ship API supports creation, validation, and cancellation of shipments and tag management for FedEx Express and Ground services. Six endpoints cover synchronous and asynchronous shipment creation, address and rule validation, cancellation, and tag operations so e-commerce platforms, 3PLs, and ERPs can produce shipping labels and recover from errors without scraping the FedEx web portal.
Create and cancel FedEx tags for one-off pickups
Drive label generation from order management or ERP systems
Patterns agents use FedEx Ship API API for, with concrete tasks.
★ E-Commerce Order Fulfilment
Online stores call POST /ship/v1/shipments to create a FedEx label as soon as an order is paid, then POST /ship/v1/shipments/validate when address details are flagged uncertain. The validation step surfaces incorrect postcodes or service-incompatible weights before they fail at booking, reducing failed shipments and customer service load.
When an order is marked paid, call POST /ship/v1/shipments with the package and recipient details and store the returned tracking number on the order.
Returns and Tag Management
Retailers offer customer returns by issuing FedEx tags via POST /ship/v1/tags so the customer can hand the package to a FedEx driver without printing anything. If the return is no longer needed, DELETE /ship/v1/tags/{confirmationNumber} releases the tag, avoiding unnecessary pickup fees.
Call POST /ship/v1/tags with the customer address and parcel details, email the confirmation to the customer, and call DELETE /ship/v1/tags/{confirmationNumber} if the return is cancelled.
Asynchronous Bulk Label Generation
Warehouses processing thousands of shipments at end-of-day book asynchronously and pick up results later. After submitting batches, GET /ship/v1/shipments/async/{jobId} retrieves the job result so the WMS can attach labels to the correct outbound parcels without holding open a long-running connection.
Submit the end-of-day shipment batch and poll GET /ship/v1/shipments/async/{jobId} until each job completes, then attach labels to outbound parcels.
Agent-Driven Shipping Decisions
An AI agent assisting a small online seller can use Jentic to discover the FedEx Ship API operations, validate a draft shipment, create the booking, and cancel and rebook if a service-level error is returned — keeping the FedEx OAuth bearer credential inside the Jentic vault.
Use Jentic to search 'create a fedex shipment' and execute POST /ship/v1/shipments with the validated package and recipient payload.
6 endpoints — jentic publishes the only available openapi specification for fedex ship api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/ship/v1/shipments
Create a shipment
/ship/v1/shipments/validate
Validate a shipment payload
/ship/v1/shipments/async/{jobId}
Retrieve async shipment job result
/ship/v1/shipments/{trackingNumber}
Cancel a shipment
/ship/v1/tags
Create a FedEx tag for pickup
/ship/v1/tags/{confirmationNumber}
Cancel a FedEx tag
/ship/v1/shipments
Create a shipment
/ship/v1/shipments/validate
Validate a shipment payload
/ship/v1/shipments/async/{jobId}
Retrieve async shipment job result
/ship/v1/shipments/{trackingNumber}
Cancel a shipment
/ship/v1/tags
Create a FedEx tag for pickup
Three things that make agents converge on Jentic-routed access.
Credential isolation
FedEx OAuth 2.0 bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped reference and Jentic refreshes and injects the Authorization header at execution time, so raw client credentials never enter agent context.
Intent-based discovery
Agents search by intent (e.g. 'create a fedex shipment') and Jentic returns the matching FedEx Ship endpoint with its input schema, including the nested shipment object structure.
Time to first call
Direct FedEx integration: 5-10 days for OAuth setup, address-validation handling, async polling, and rate-limit recovery. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
DHL Shipment Tracking
Carrier alternative for international shipping with strong EU and Asia coverage
Choose DHL when shipments primarily originate or terminate outside North America.
Shippo
Multi-carrier shipping aggregator that complements direct FedEx integration
Use Shippo when you want a single integration spanning FedEx, UPS, USPS, and other carriers.
AfterShip
Branded post-purchase tracking and notifications layered on top of FedEx labels
Use AfterShip to surface tracking events to customers after FedEx has produced the shipment.
Specific to using FedEx Ship API API through Jentic.
Why is there no official OpenAPI spec for FedEx Ship API?
FedEx publishes JSON examples and reference docs on developer.fedex.com but not a unified OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FedEx Ship 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 FedEx Ship API use?
The FedEx Ship API uses OAuth 2.0 bearer tokens issued by FedEx's authorization server. Through Jentic the bearer token is stored in the vault and injected into the Authorization header at call time so the agent never sees the raw secret.
Can I validate a FedEx shipment before booking it?
Yes. POST /ship/v1/shipments/validate runs the same business rules as creation but does not commit the shipment, letting you catch address or service errors before the label is produced.
What are the rate limits for the FedEx Ship API?
FedEx applies per-account throughput limits negotiated with each contract; numeric limits are not declared in this OpenAPI spec. Apply backoff on 429 and 503 responses and check your FedEx Developer Portal account for current quota.
How do I create a FedEx shipment through Jentic?
Run pip install jentic, search 'create a fedex shipment', load POST /ship/v1/shipments, and execute it with the package and recipient details to receive the tracking number and label data.
Can I cancel a shipment after creation?
Yes. DELETE /ship/v1/shipments/{trackingNumber} cancels a shipment that has not yet been picked up by FedEx, returning the tracking number to an unused state.
/ship/v1/tags/{confirmationNumber}
Cancel a FedEx tag