Docs/APIs/Visa Requirements

Visa Requirements

Check visa rules between any passport and destination

OperationalCredits 5 per callp50 237msTransportationStar

Overview

Covers about 200 passports and up to 235 destinations each, including territories with their own entry rules such as Hong Kong, Puerto Rico and Greenland. Pass countries as ISO 3166 two-letter codes or English names. Requirements are normalized to six categories so they compare across countries, and the allowed stay is given both as days and as the original wording, e.g. 90 days within any 180-day period. Data is checked weekly. Entry rules change, and conditions such as passport validity, onward tickets or purpose of travel still apply, so confirm with the destination's official source before booking.

Live Test Visa Requirements API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/visarequirements
curl "https://api.apiverve.com/v1/visarequirements?passport=US&destination=JP" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
passportRequiredstringThe passport's country: a two-letter ISO code such as US, or an English name such as United States
length 0–60
destinationRequiredstringThe destination country or territory: a two-letter ISO code such as JP, or an English name such as Japan
length 0–60

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "passport": "US",
    "passportName": "United States",
    "destination": "JP",
    "destinationName": "Japan",
    "requirement": "visa_free",
    "requirementLabel": "Visa not required",
    "visaRequiredInAdvance": false,
    "allowedStayDays": 90,
    "allowedStay": "90 days",
    "updatedAt": "2026-10-22T09:00:00.000Z"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
passportstring"US"Passport country, ISO 3166 two-letter code
passportNamestring"United States"Passport country name
destinationstring"JP"Destination, ISO 3166 two-letter code
destinationNamestring"Japan"Destination name
requirementstring"visa_free"visa_free, eta, evisa, visa_on_arrival, visa_required, restricted or unknown
requirementLabelstring"Visa not required"Readable form of requirement, e.g. Visa not required
visaRequiredInAdvancebooleanfalseWhether a visa must be obtained before travel; null when entry is restricted or unknown
allowedStayDaysnumber90Allowed stay in days, or null when none is set or it is not a fixed number of days
allowedStaystring"90 days"Allowed stay as stated, e.g. 90 days or 3 months
updatedAtstring"2026-10-22T09:00:00.000Z"When this passport's requirements last changed in the dataset (ISO 8601)

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Travel Booking Checkout
Booking sites warn travelers at checkout when their passport needs a visa or eVisa for the destination, before they pay for a non-refundable fare.
Corporate Travel Approval
Travel management tools flag trips where an employee's nationality needs a visa arranged weeks in advance, so the request goes to the visa team first.
Trip Planning Apps
Itinerary apps show the allowed stay next to each stop so a multi-country route stays within the visa-free days.
Relocation and HR Tools
Mobility platforms compare how many destinations each candidate's passport reaches without an advance visa when planning client visits.

Other ways to use Visa Requirements

Set up Visa Requirements on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Transportation:

Was this page helpful?