canonical: https://jentic.com/apis/wink.travel/wink-travel

# Wink Travel Wink API

APIs Not every integrator needs every APIs. For that reason, we have separated APIs into context. - [Affiliate](https://api.wink.travel): All APIs related to selling travel inventory as an affiliate. - [Analytics](https://api.wink.travel): All APIs related to tracking metrics across a wide variety of data source segments including, more entertaining, leaderboard metrics. - [Booking](https://api.wi. The API exposes 129 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically show link, update link. Covers 129 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Show Link
- Update link
- Delete Link
- Remove Curated List
- Copy Item to List
- Move List Item

## Use cases

### Analytics Operations

Use the Wink API to perform analytics operations programmatically. The API provides 129 endpoints covering core functionality including show link, update link, delete link.

Example prompt: Call GET `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` to show link

### Automated Inventory Grids Management

Automate inventory grids operations by combining multiple Wink API endpoints. Agents can update link and then delete link in a single workflow.

Example prompt: Call PUT `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` to update link, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` | Show Link |
| PUT | `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` | Update link |
| DELETE | `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` | Delete Link |
| PUT | `/api/company/{companyIdentifier}/static/list/{listIdentifier}` | Update Curated List |
| DELETE | `/api/company/{companyIdentifier}/static/list/{listIdentifier}` | Remove Curated List |
| POST | `/api/company/{companyIdentifier}/static/list/{listIdentifier}/item/{itemIdentifier}` | Copy Item to List |
| PUT | `/api/company/{companyIdentifier}/static/list/{listIdentifier}/item/{itemIdentifier}` | Move List Item |
| DELETE | `/api/company/{companyIdentifier}/static/list/{listIdentifier}/item/{itemIdentifier}` | Delete List Item |

## Key resources

- **Inventory Grids** — Grids are made up of 3 categories of lists: 

- Cured lists
- Saved searches
- Ranked lists

The way
- **Syndication Entry Publisher** — Manage curated list entries and categories for your various Wink accounts.
- **Discover** — Before you can sell travel inventory, you need to find it. Discover travel inventory that fits your
- **Maps** — Configure and manage maps, map data and overlays that you wish to display to your users.
- **Company** — Manage companies.

## Why Jentic

- **Setup:** Wiring the Wink API by hand means running its client-credentials OAuth flow, picking the right production, sandbox, or developer host, and threading company and list identifiers through every path yourself. Through Jentic you install once, import the Wink API from the API Directory, store the OAuth client once, and your agent calls it.
- **Permission scoping:** Wink puts the company and list ids in the URL path (`/api/company/{companyIdentifier}/static/list/{listIdentifier}`), so a rule can pin your agent to one company and the lists within it. You choose the operations it may call, so destructive ones like deleting a list or a supplier URL are not included unless you add them.
- **Credential handling:** Your Wink OAuth client 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 'read a company's supplier link' or 'add an item to a list', and Jentic returns the matching Wink 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 Wink API use?

The Wink API uses OAuth 2.0 for authorization. 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 show link with the Wink API?

Yes. Use the GET `/api/company/{companyIdentifier}/supplier-url/{supplierUrlIdentifier}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wink 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 show link through Jentic?

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

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

The Wink API exposes 129 endpoints covering inventory grids, syndication entry publisher, discover operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Wink operations and OAuth credentials the agent can use. Because Wink puts the company and list ids in the URL path, such as `/api/company/{companyIdentifier}/static/list/{listIdentifier}`, you can pin the agent to a single company and the lists within it. You also choose the exact operations it may call, so destructive ones like deleting a curated list or removing a supplier URL stay off limits unless you explicitly add them.