Skip to content
WincoradevelopersBack to Wincora
API v1
DocumentationTenant API
Tenant API

Build a tenant integration

Connect intelligence, order creation, and traveler access through one integration.

6 min read·Wincora API v1
On this page

Before you start

Use a server-side tenant key for Visa Intelligence and Tenant operations. Give customer-facing applications a scoped customer token for the Traveler API.

During onboarding, configure integration grants, resource access, delegation permissions, environment, and customer login mode. Tenant API keys stay on your server.

01. Discover your capabilities

Start with your integration resource. Read the effective grants, environment, limits, and enabled capabilities before showing an action to a customer.

Example
curl 'https://api.wincora.com/api/v1/tenant/integration' \
  --header 'X-Api-Key: YOUR_API_KEY'
Integration reference

02. Understand the trip

Read the supported intent and country codes. Resolve free-text purpose only when necessary, then create a visa determination with actual travel dates.

Render the visa conclusion separately from commercial availability. An unavailable service does not mean a traveler needs no visa.

Determine visa requirements

03. Quote and create an order

Create or locate the permitted customer and traveler records using your external references. Select an available product and service level, then create a quote for those exact inputs.

Create the order using the quote ID and a stable idempotency key. Store the returned order and case IDs in your system.

Example
{
  "quoteId": "quote_example",
  "externalReference": "booking-4387",
  "tripName": "November trip"
}
Create an order

04. Connect the signed-in identity

Provision a customer identity using a stable subject from your authentication system, then create explicit case or traveler relationships. Corporate account membership does not grant blanket access.

Use your backend to create a customer session, or enroll the identity for Wincora-managed sign-in. Both yield a token restricted to the Traveler API.

Authentication and access

05. Collect and submit

On the Traveler surface, fetch authorized case requirements and render the typed fields and document requirements in your UI. Upload evidence and poll its processing operation with the customer token.

Complete the configured payment flow, check readiness, and explicitly submit. A successful handoff to Wincora is not the same as filing with an authority.

Build a collection flow

06. Follow through to the result

Subscribe to events and retain a replay cursor. Your application can show progress, request more information, and retrieve the released deliverables.

If further information is requested, update the required data or documents. Resubmit when the case indicates that resubmission is required.

Handle events reliably
Search the developer documentation
↑↓ NavigateEnter OpenEsc Close
Explore documentation