post/v1/admin/visa-data/{destination}/requirements

Publish a new version of a destination’s document requirements

Operation: adminPublishVisaRequirements
Authentication: API key

Requirements carry a source URL and the date they were verified against it, and publishing bumps the version rather than editing in place: a partner reading the old version is reading what we told them, and the audit log keeps both.

Request

Parameters

destinationpathrequiredstring

Body

requirementsobjectrequired

source_urlstringrequired

verified_onstringrequired

Responses

201Requirements published.

Free-form JSON object.

400The request body or query failed validation.

errorobjectrequired

401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.

errorobjectrequired

403`projects:write` is required. No partner key is ever issued this scope.

errorobjectrequired

404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.

errorobjectrequired

Example

curl

curl -X POST https://api.haavisa.com/v1/admin/visa-data/<destination>/requirements \
  -H "Authorization: Bearer $HAAVISA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requirements": "<requirements>",
    "source_url": "<source_url>",
    "verified_on": "<verified_on>"
  }'

More in Admin

Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.