Arrivalcard for travel operators

What it does and does not do

• Does: tell you exactly which forms each traveller needs, with deadlines and official links.
• Does: flag exemptions with a reason your agents can repeat to a client.
• Does not: submit anything to a government portal — for you or for your travellers.
• Does not: store passenger data. The endpoint is stateless; nothing is written or logged.

Every form we track is free on its official portal. We bill for the screening and monitoring, never for the filing.

POST /api/b2b/batch

curl -X POST https://your-host/api/b2b/batch \
  -H "x-api-key: $B2B_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "trips": [
      {
        "traveller": { "nationality": "US", "isOCI": true, "ref": "BKG-1042" },
        "legs": [{
          "destination": "IN",
          "travelStartAt": "2026-09-01T06:00:00+07:00",
          "arrivalAt": "2026-09-01T11:30:00+05:30"
        }]
      },
      {
        "traveller": { "nationality": "IN", "ref": "BKG-1043" },
        "legs": [{ "destination": "TH", "arrivalAt": "2026-09-10T14:00:00+07:00" }]
      }
    ]
  }'

The response carries summary.actionableNow — the count of travellers whose window is open or closing. That number is your ops queue. Batch limit 500 trips. Pass maxRuleAgeDays to reject stale rules rather than trust them.

Coverage