canonical: https://jentic.com/apis/ship24.com/ship24

# Ship24 Tracking API

Ship24 multi-carrier shipment tracking API. Track packages across 700+ couriers globally. The API exposes 10 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a tracker, list trackers. Covers 10 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a tracker
- List trackers
- Bulk create trackers (up to 100)
- Get a specific tracker
- Update a tracker

## Use cases

### 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).

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a tracker', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Couriers** — Operations related to Couriers
- **Trackers** — Operations related to Trackers
- **Tracking** — Operations related to Tracking

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/ship24.com/ship24/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 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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.