canonical: https://jentic.com/apis/track-pod.com/track-pod

# Track-POD API

Track-POD API enables ERP or any other system integration with Track-POD without need for any manual data input. Our API provides an easy HTTP interface to Track-POD functionality through JSON or XML<br><br><b>Endpoint:</b><br>https://api.track-pod.com/<br><br><b>Request headers:</b><br><b>X-API-KEY</b> - API Key. Please find the API key in the Track-POD settings <br><b>Content-Type</b> - (POST/PU. The API exposes 73 endpoints secured with apiKey authentication.

## For AI agents

Programmatically add or update address, get driver by track-pod unique identifier. Covers 73 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Add or update address
- Get driver by Track-POD unique identifier
- Delete driver by Track-POD unique identifier
- Query and filter Track-POD API records by parameters
- Monitor Track-POD API operational status and events

## Use cases

### Social Media Operations

Use the Track-POD API to perform social media operations programmatically. The API provides 73 endpoints covering core functionality including add or update address, get driver by track-pod unique identifier, delete driver by track-pod unique identifier.

Example prompt: Call POST /Address to add or update address

### Automated Address Management

Automate address operations by combining multiple Track-POD API endpoints. Agents can get driver by track-pod unique identifier and then delete driver by track-pod unique identifier in a single workflow.

Example prompt: Call GET /Driver/Id/{id} to get driver by track-pod unique identifier, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Track-POD 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 apiKey tokens manually.

Example prompt: Search Jentic for 'add or update address', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /Address | Add or update address |
| GET | /Driver/Id/{id} | Get driver by Track-POD unique identifier |
| DELETE | /Driver/Id/{id} | Delete driver by Track-POD unique identifier |
| GET | /Driver/Username/{username} | Get driver by Username |
| DELETE | /Driver/Username/{username} | Delete Driver by id. |
| POST | /Driver | Add driver |
| GET | /Driver | Get drivers |
| PUT | /Driver | Update driver |

## Key resources

- **Address** — Operations related to Address
- **Driver** — Operations related to Driver
- **Order** — Operations related to Order
- **RejectReason** — Operations related to RejectReason
- **Route** — Operations related to Route

## Why Jentic

- **Setup:** Wiring the Track-POD API by hand means setting up its X-API-KEY header auth, tracking the api.track-pod.com host, and coding your own request handling for driver and address management. Through Jentic you install once, import the Track-POD API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Track-POD puts the driver id in the URL path (/Driver/Id/{id}), so a rule can pin your agent to a specific driver and the operations it needs there. You choose which operations it may call, so destructive ones like deleting a driver are not included unless you add them.
- **Credential handling:** Your Track-POD API key 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 'add or update an address' or 'get a driver by id', and Jentic returns the matching Track-POD operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Track-POD API use?

The Track-POD API uses an API key passed in the `X-API-KEY` 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 add or update address with the Track-POD API?

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

### What are the rate limits for the Track-POD 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 add or update address through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add or update address'. Jentic returns the matching Track-POD API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Track-POD API have?

The Track-POD API exposes 73 endpoints covering address, driver, order operations.

### Can I limit what my agent is allowed to do with the Track-POD API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Track-POD operations and credentials the agent may use. Because Track-POD puts the driver id in the URL path (GET /Driver/Id/{id}), you can pin the agent to a specific driver and only the operations it needs there. You choose exactly which endpoints it may call, so destructive ones such as DELETE /Driver/Id/{id} stay out of reach unless you explicitly add them.