Troubleshooting

Server-side verification stuck for more than 1 minute

If verification hangs, check if your HTTP request includes a keep-alive header.

Problematic headers to remove:

Connection: keep-alive
Keep-Alive: timeout=5, max=100

Remove it from the payload before verification and try again.

Working out where a verification went wrong

When a user reports that a verification "didn't work", fetch its event timeline before anything else — it tells you how far they actually got:

const { events } = await vouch.getTelemetryEvents({ requestId });
console.log(events.at(-1));

The last event is usually the answer. If the timeline stops at request creation the user never installed the Vouch Verifier extension or opened the mobile app; if it ends with a webhook failure, the verification itself succeeded and the problem is on your endpoint.

Around notarization, read the events precisely: CONSENT_DISPLAYED only means the consent screen was shown. Look for NOTARIZATION_STARTED before concluding that notarization began at all — a timeline ending at consent usually means the user closed the screen rather than that notarization stalled.

See Tracking verification progress for the full response shape.

Scrape routes return POST_* or SCRAPING_*

These come from the social engagement API when a post or profile cannot be read. 422 and 404 codes are permanent for that post; 429, 502, and 503 are transient. See Scraping errors for the full table.