Trip Checker
Check whether a passport needs a visa for a destination, and whether it stays valid long enough for the trip.
- Next.js
- TypeScript
Also uses Travel Entry Requirements
Know if a traveler needs a visa, an eVisa or nothing, and how long they can stay.
Visa Requirements tells you what a passport holder needs to enter another country: no visa, an electronic travel authorization, an eVisa, a visa on arrival, a visa arranged in advance, or entry restricted. Paid plans add the allowed stay in days, every alternative route (an eVisa or a visa on arrival, say), a link to the official government portal for ETAs and eVisas, per-category counts for a passport and its full destination list.
No key required to try it. Get a key to use it in your app.
{
"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",
"options": [
"visa_free"
],
"onlineApplication": null,
"updatedAt": "2026-10-19T03:33:20.529Z"
}
}
Check whether a passport needs a visa for a destination, and whether it stays valid long enough for the trip.
Also uses Travel Entry Requirements
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 (see the Travel Entry Requirements API), onward tickets or purpose of travel still apply, so confirm with the destination's official source before booking.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Same data, same APIVerve account, same credit balance — one key works on all of them.
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
| Parameter | Type | Example | Description |
|---|---|---|---|
passportRequired | string | US | The passport's country: a two-letter ISO code such as US, an English name such as United States, UK for the United Kingdom, or a passport MRZ code such as D or GBR length 0-60 |
destinationRequired | string | JP | The destination country or territory: a two-letter ISO code such as JP, an English name such as Japan, or UK for the United Kingdom length 0-60 |
curl "https://api.apiverve.com/v1/visarequirements?passport=US&destination=JP" \
-H "x-api-key: YOUR_API_KEY"Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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",
"options": [
"visa_free"
],
"onlineApplication": null,
"updatedAt": "2026-10-22T09:00:00.000Z"
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
passport | string | "US" | Passport country, ISO 3166 two-letter code |
passportName | string | "United States" | Passport country name |
destination | string | "JP" | Destination, ISO 3166 two-letter code |
destinationName | string | "Japan" | Destination name |
requirement | string | "visa_free" | visa_free, eta, evisa, visa_on_arrival, visa_required, restricted or unknown |
requirementLabel | string | "Visa not required" | Readable form of requirement, e.g. Visa not required |
visaRequiredInAdvance | boolean | false | Whether a visa must be obtained before travel; null when entry is restricted or unknown |
allowedStayDaysPremium | number | 90 | Allowed stay in days, or null when none is set or it is not a fixed number of days |
allowedStayPremium | string | "90 days" | Allowed stay as stated, e.g. 90 days or 3 months |
optionsPremium | array | [visa_free] | Every route the destination offers this passport, primary first, e.g. ["visa_on_arrival", "evisa"] when a visa on arrival or an eVisa both work |
onlineApplicationPremium | object | null | For eta and evisa routes, the official government portal: type, scheme (e.g. ESTA, e-Visa) and officialUrl; null when there is no online route or no verified official portal |
updatedAt | string | "2026-10-22T09:00:00.000Z" | When this passport's requirements last changed in the dataset (ISO 8601) |
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Visa Requirements calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 10 | Free |
| Starter | $29.99 | 200,000 | 10,000 | $3.00 |
| Pro | $99.99 | 1,000,000 | 50,000 | $2.00 |
| Mega | $299.99 | 4,000,000 | 200,000 | $1.50 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/visarequirements" \
-H "x-api-key: YOUR_API_KEY"No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/visarequirements", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/visarequirements",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/visarequirements");
Console.WriteLine(json);No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/visarequirements", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/visarequirements");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;No SDK to install — this is a plain HTTPS call to /v1/visarequirements with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/visarequirements")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyDrop an interactive Visa Requirements form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Visa Requirements API.