API reference / Applications
/v1/applications/lookupLook up an application by reference and email
- Operation
lookupApplication- Authentication
- API key
For the public status tracker. The reference is not a secret — `HV-` plus six characters is about a billion combinations — so the email is the second factor and both are matched. A reference that does not exist and a reference whose email does not match return the same 404, so the endpoint cannot be used to confirm that a reference is real.
The response is an allowlist: it carries the status, the party size and the frozen total, and never `form_data`, which holds every passport number and date of birth on the application.
Request
Body
referencestringrequiredThe reference from the confirmation email.
example: HV-QYFHW6M4D8
emailstringrequiredThe address the application was made with.
Responses
referencestringrequiredgovernment_referencestringnullrequireddestination_iso3stringrequiredstatusstringrequiredone of: draftawaiting_paymentpaidsubmittedunder_reviewapprovedrejectedcancelledexpired
service_tierstringnullrequiredtravellersintegerrequiredThe party size including the lead.
currencystringrequiredtotal_centsintegerrequiredcreated_atstringrequiredsubmitted_atstringnullrequireddecided_atstringnullrequirederrorobjectrequirederrorobjectrequirederrorobjectrequirederrorobjectrequiredExample
curl -X POST https://api.haavisa.com/v1/applications/lookup \
-H "Authorization: Bearer $HAAVISA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"reference": "HV-QYFHW6M4D8",
"email": "<email>"
}'More in Applications
Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.