I would assume the token will expire at one time, I'm not sure how far
in the future. If it doesn't expire, then this is a pretty obvious
security hole that should get patched quickly.
For your case, CAPTCHAs are not designed for web services. You're
trying to build an automated (or semi-automated) system that can fill
in a web form in place of a human. This is exactly the use case that
CAPTCHAs are trying to stop.
I don't understand why do you need to protect a web API against
non-human request? Web API is built to be called by a program.
--
Adrian Godong
adrian...@gmail.com