Ship24 Tracking API
67
AI ReadinessAI-Aware (B+)67/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsProject Managementbearer10 EndpointsREST
For Agents
Programmatically create a tracker, list trackers. Covers 10 operations with bearer authentication.
Use for: I need to a tracker, I want to trackers, Search for bulk create trackers (up to 100), Find all a specific tracker
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Ship24 multi-carrier shipment tracking API. Track packages across 700+ couriers globally. The API exposes 10 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Ship24 Tracking API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ship24 Tracking 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fship24.com%2Fship24" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fship24.com%2Fship24" | 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.
Capabilities
What an agent can do with Ship24 Tracking API.
Create a tracker
List trackers
Bulk create trackers (up to 100)
Get a specific tracker
Update a tracker
Use Cases
Patterns agents use Ship24 Tracking API for, with concrete tasks.
★ Developer Tools Operations
Use the Ship24 Tracking API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including create a tracker, list trackers, bulk create trackers (up to 100).
Call POST /public/v1/trackers to create a tracker
Automated Couriers Management
Automate couriers operations by combining multiple Ship24 Tracking API endpoints. Agents can list trackers and then bulk create trackers (up to 100) in a single workflow.
Call GET /public/v1/trackers to list trackers, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Ship24 Tracking API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create a tracker', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
10 endpoints — ship24 multi-carrier shipment tracking api.
METHOD
PATH
DESCRIPTION
POST
/public/v1/trackers
Create a tracker
GET
/public/v1/trackers
List trackers
POST
/public/v1/trackers/bulk
Bulk create trackers (up to 100)
GET
/public/v1/trackers/{trackerId}
Get a specific tracker
PATCH
/public/v1/trackers/{trackerId}
Update a tracker
POST
/public/v1/trackers/track
Create tracker and fetch results synchronously
GET
/public/v1/trackers/{trackerId}/results
Get tracking results for a tracker
GET
/public/v1/trackers/search/{trackingNumber}/results
Search tracking results by tracking number
POST
/public/v1/trackers
Create a tracker
GET
/public/v1/trackers
List trackers
POST
/public/v1/trackers/bulk
Bulk create trackers (up to 100)
GET
/public/v1/trackers/{trackerId}
Get a specific tracker
PATCH
/public/v1/trackers/{trackerId}
Update a tracker
POST
/public/v1/trackers/track
Create tracker and fetch results synchronously
GET
/public/v1/trackers/{trackerId}/results
Get tracking results for a tracker
GET
/public/v1/trackers/search/{trackingNumber}/results
Search tracking results by tracking number
Jentic AI Readiness Score
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.
S
Ship24 Tracking API
- AI-Aware (B+)67/100
93
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ship24 Tracking API by hand means setting its bearer token, pointing at the api.ship24.com host, and managing tracker creation and result polling yourself. Through Jentic you install once, import the Ship24 Tracking API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Ship24 puts the tracker id in the URL path (/public/v1/trackers/{trackerId}/...), so a rule can pin your agent to one tracker. You choose the operations it may call, so a write like updating a tracker is not included unless you add it.
Credential isolation
Your Ship24 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.
Intent-based discovery
Agents search Jentic by intent such as 'create a tracker' or 'get tracking results', and Jentic returns the matching Ship24 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Ship24 Tracking API through Jentic.
What authentication does the Ship24 Tracking API use?
The Ship24 Tracking API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a tracker with the Ship24 Tracking API?
Yes. Use the POST /public/v1/trackers endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Ship24 Tracking API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a tracker through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a tracker'. Jentic returns the matching Ship24 Tracking API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Ship24 Tracking API have?
The Ship24 Tracking API exposes 10 endpoints covering couriers, trackers, tracking operations.
Can I limit what my agent is allowed to do with the Ship24 Tracking API?
Yes. Because you run Jentic One yourself, your own rules decide which Ship24 operations and credentials the agent may use. You can allow read-only calls such as GET /public/v1/trackers/{trackerId}/results while withholding writes like POST /public/v1/trackers or PATCH /public/v1/trackers/{trackerId} until you add them. Since Ship24 puts the tracker id in the URL path, a rule can also pin the agent to a single tracker rather than your whole account.
GET STARTED