How long does a reCAPTCHA token last?
A reCAPTCHA response token expires two minutes after it is issued and is single-use. Classic tokens can be verified once; Enterprise website tokens can be assessed once.
On this page
Request the token last
Don't prewarm a pool of tokens or cache them for later. Time spent waiting in your application uses up their short validity window.
- 1.
Prepare the protected request
Finish the work that doesn't need a token before requesting a solve.
- 2.
Wait for a ready task
Only a ready task contains a usable solution. Task creation alone isn't enough.
- 3.
Submit promptly
Use the returned token and browser identity with the successful proxy.
Don't consume it in a test
An extra verification or Enterprise assessment just to check whether a token works can consume its one use. Send it through the intended protected request instead. For another protected request, obtain a fresh token rather than replaying the previous one—even if two minutes haven't passed.
Task retention is a different clock
solvethree retains completed task results for a bounded period. That storage window doesn't extend the token's lifetime: retrieving a ready task again doesn't refresh its token, and saving the response doesn't make it reusable.
HTTP 410 when retrieving a task means the stored result has expired. That's separate from Google rejecting an expired or already-used token. A stored result can still be available after its token is no longer usable.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.