canonical: https://jentic.com/apis/shippify.co/shippify

# Shippify API

Shippify provides powerful logistics tools with the most advanced technology on the market to deliver and track your shipments. The API allows creating deliveries, getting quotes, managing routes, and tracking shipments. The API exposes 12 endpoints secured with basic authentication.

## For AI agents

Programmatically get countries, create deliveries. Covers 12 operations with basic authentication.

## Scope

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

## Capabilities

- Get countries
- Create deliveries
- Modify delivery dropoff
- Change delivery status
- Monitor Shippify API operational status and events

## Use cases

### Analytics Operations

Use the Shippify API to perform analytics operations programmatically. The API provides 12 endpoints covering core functionality including get countries, create deliveries, get delivery information.

Example prompt: Call GET `/v1/country` to get countries

### Automated Deliveries Management

Automate deliveries operations by combining multiple Shippify API endpoints. Agents can create deliveries and then get delivery information in a single workflow.

Example prompt: Call POST `/v1/deliveries` to create deliveries, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Shippify 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/country` | Get countries |
| POST | `/v1/deliveries` | Create deliveries |
| GET | `/v1/deliveries/{id}/complete` | Get delivery information |
| PATCH | `/v1/deliveries/dropoff` | Modify delivery dropoff |
| PATCH | `/v1/deliveries/{id}/status` | Change delivery status |
| GET | `/v1/deliveries/token/{id}` | Get delivery tracking link |
| POST | `/v2/pricing/quotes/available` | Get delivery quotation |
| POST | `/v2/integrations/deliveries/labels` | Print delivery labels |

## Key resources

- **Deliveries** — Create, modify, and manage deliveries
- **Pricing** — Delivery quotation and pricing
- **Routes** — Create and manage delivery routes
- **Tracking** — Delivery tracking and labels
- **Health** — API health and connectivity checks

## 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:** 40 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 72 / 100
- **View full report:** https://jentic.com/apis/shippify.co/shippify/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 Shippify API by hand means handling its basic auth, pointing at the api.shippify.co host, and threading credentials through delivery creation and status calls yourself. Through Jentic you install once, import the Shippify API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Shippify puts the delivery id in the URL path (`/v1/deliveries/{id}/...`), so a rule can pin your agent to one delivery for actions like completing it or updating its status. You choose the operations it may call, so anything else is left out unless you add it.
- **Credential handling:** Your Shippify credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a delivery' or 'get a delivery quote', and Jentic returns the matching Shippify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Shippify API use?

The Shippify API uses HTTP Basic authentication with username and password. 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 get countries with the Shippify API?

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

### What are the rate limits for the Shippify 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 get countries through Jentic?

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

### How many endpoints does the Shippify API have?

The Shippify API exposes 12 endpoints covering deliveries, pricing, routes operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Shippify operations and credentials the agent may use. Since Shippify carries the delivery id in the URL path, such as `/v1/deliveries/{id}/status` and `/v1/deliveries/{id}/complete`, you can pin the agent to a single delivery for actions like updating its status or completing it. You also choose the exact operations it may call, so anything you do not grant, such as creating deliveries or printing labels, stays out of reach.