Contact
Overview
Wink API 30.49.0
Section titled “Wink API 30.49.0”Welcome to the Wink API — a programmer-friendly way to manage, sell and book travel inventory on the Wink platform. See the Overview page (under API) for the full introduction, intended audience, testing, and versioning.
Channel Manager API
Wink exposes a secured REST-based, JSON API to its channel manager partners. The connection is “channel-wide”. Partners are free to integrate with the REST-based API using any programming language.
Intended Audience
This document is intended for external channel partners who wish to integrate with Wink.
Requirements
- Active account with Wink. Sign up for your Channel Manager account:
- Staging: https://staging-app.wink.travel.
- Production: https://app.wink.travel.
- Active application. An application provides you with Oauth2 credentials you can pass to our endpoints. One is already created for you upon account creation.
- Your production IP numbers. They need to be whitelisted before you can talk to our production environment.
Performance
A particular attention to performance should be given when integrating with this API. A few things to be aware of:
- Enable gzip compression to make payloads smaller.
- Fewer large REST calls are preferred to many small ones. E.g. It is better to update many dates instead of individual dates.
- It is possible to update both rate and availability with a single request.
- Request only date ranges that you will use. There is no need to request an entire year if you will only be working with the first seven days.
Reservation notification (PUSH)
Wink supports PUSH notifications to communicate reservations. We also support BASIC AUTH to your endpoint. If you want to enable PUSH, add your PUSH endpoint and credentials (optional) to your account.
Authentication
Section titled “ Authentication ”oauth2ClientCredentials
Section titled “oauth2ClientCredentials ”Every endpoint is protected with OAuth2 client credentials. Create an
Application in your account to obtain a clientId and clientSecret, then
exchange them for a short-lived bearer token.
1. Request an access token
POST to the Token URL below with Content-Type: application/x-www-form-urlencoded
and a body of grant_type=client_credentials (optionally scope=<space-separated scopes>).
Send your credentials as HTTP Basic auth:
Authorization: Basic base64(clientId + ":" + clientSecret).
2. Call the API
Pass the returned token on every request: Authorization: Bearer <access_token>.
Tokens carry only the scopes granted to your Application — request the least privilege you need. There is no interactive authorize step and no refresh token for this flow; request a new token when the current one expires.
Security scheme type: oauth2
Flow type: clientCredentials
Token URL: https://iam.wink.travel/oauth2/token
Scopes:
- integrations.read - View your channel manager integrations.
- integrations.write - Create and update your channel manager integrations.
- integrations.remove - Delete your channel manager integrations.