Changelog · July 16, 2026
GET /result/:token
A slow page is a wait, not a lost request.
By Roger Campos · Last updated: July 2026
TL;DR
GET /result/:token returns a stored result in its operation's usual format: 200 with the result, 202 while it is still processing, 422 for a failed analysis, 404 for an unknown token and 410 once it is past the 30-day retention window. A sync request that outlives its 60-second wait answers 504 with a token, so a slow analysis is never lost.
Free plan, no credit card. 1,000 credits a month.
Tokens are scoped to the project that made the request: a token from another project reads as 404. Sync responses carry their token in the X-Result-Token header, so any request can be fetched again later without paying for it twice.
curl https://urlpipe.dev/result/TOKEN \
-H "Authorization: Bearer YOUR_API_KEY"FAQ
Frequently asked questions
30 days. After that the token answers 410.
The analysis is still running; ask again shortly.
It answers 504 with a token, and the analysis carries on; collect it with GET /result/:token.
Try it on the free plan.
Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.