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

# Terminal49 API Reference

The Terminal 49 API offers a convenient way to programmatically track your shipments from origin to destination. Please enter your API key into the "Variables" tab before using these endpoints within Postman. The API exposes 77 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list shipments, get a shipment. Covers 77 operations with apiKey authentication.

## Scope

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

## Capabilities

- List shipments
- Get a shipment
- Edit a shipment
- Stop tracking a shipment
- Resume tracking a shipment
- Create a tracking request

## Use cases

### Communications Operations

Use the Terminal49 API Reference to perform communications operations programmatically. The API provides 77 endpoints covering core functionality including list shipments, get a shipment, edit a shipment.

Example prompt: Call GET /shipments to list shipments

### Automated Containers Management

Automate containers operations by combining multiple Terminal49 API Reference endpoints. Agents can get a shipment and then edit a shipment in a single workflow.

Example prompt: Call GET `/shipments/{id}` to get a shipment, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Terminal49 API Reference 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 apiKey tokens manually.

Example prompt: Search Jentic for 'list shipments', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/shipments` | List shipments |
| GET | `/shipments/{id}` | Get a shipment |
| PATCH | `/shipments/{id}` | Edit a shipment |
| PATCH | `/shipments/{id}/stop_tracking` | Stop tracking a shipment |
| PATCH | `/shipments/{id}/resume_tracking` | Resume tracking a shipment |
| POST | `/tracking_requests` | Create a tracking request |
| GET | `/tracking_requests` | List tracking requests |
| POST | `/tracking_requests/infer_number` | Infer Tracking Number |

## Key resources

- **Containers** — Operations related to Containers
- **Custom Field Definitions** — Operations related to Custom Field Definitions
- **Custom Field Options** — Operations related to Custom Field Options
- **Custom Fields** — Operations related to Custom Fields
- **Shipments** — Operations related to Shipments

## 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:** 55 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 53 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 41 / 100
  - Agent Usability: 90 / 100
  - Security: 50 / 100
  - AI Discoverability: 67 / 100
- **View full report:** https://jentic.com/apis/terminal49.com/terminal49/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 Terminal49 API by hand means learning its token-based Authorization header auth against the api.terminal49.com/v2 host and handling shipment and tracking-request calls yourself. Through Jentic you install once, import the Terminal49 API from the API Directory, store the API token once, and your agent calls it.
- **Permission scoping:** Terminal49 puts the shipment id in the URL path (`/shipments/{id}`), so a rule can pin your agent to one shipment: it can read and update that shipment and nothing else. You choose the operations it may call, so stopping or resuming tracking is not included unless you add it.
- **Credential handling:** Your Terminal49 API 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 'list shipments' or 'create a tracking request', and Jentic returns the matching Terminal49 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Terminal49 API Reference use?

The Terminal49 API Reference uses an API key passed 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 list shipments with the Terminal49 API Reference?

Yes. Use the GET /shipments endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Terminal49 API Reference?

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 list shipments through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list shipments'. Jentic returns the matching Terminal49 API Reference operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Terminal49 API Reference have?

The Terminal49 API Reference exposes 77 endpoints covering containers, custom field definitions, custom field options operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Terminal49 operations and credentials the agent may use. Because Terminal49 puts the shipment id in the URL path (`/shipments/{id}`), you can pin the agent to a single shipment and let it only read and edit that one. You also choose the exact operations it may call, so actions like stopping or resuming tracking stay off limits unless you explicitly grant them.