post/v1/admin/applications/{id}/status-check

Ask the portal about this application now

Operation: adminBringStatusCheckForward
Authentication: API key

Moves this application’s status check to the front of the queue the worker sweeps.

**Nothing is looked up by this call.** The worker owns the browser, so this only makes the row due; a 202 means the check is scheduled, not done, and what comes back lands on the application detail as an observation or a decision.

For an applicant on the phone asking where their visa is. It is refused with a 409 when a decision is already recorded — re-checking one risks a second email about something they already know — or when a worker is running that check right now.

Request

Parameters

idpathrequiredstring

Responses

202Due now. The worker has not run yet.

statusstringrequired

Always `queued`: the check is now due, and the worker has not run it yet.

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/applications/<id>/status-check \
  -H "Authorization: Bearer $HAAVISA_API_KEY"

More in Admin

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