Skip to main content
Every task moves through a predictable lifecycle — from creation to a retrievable result.

​
Task Flow

1

Task Creation

You send a POST /createTask request. The server validates your API key, task parameters, proxy format, and checks your balance or package quota. If everything is valid, a task ID (UUID) is returned and the task is queued for processing.
2

Validation

The server performs deep validation:
  • API key and account status
  • Task type must be FunCaptchaTask
  • Site key must be a valid UUID
  • Proxy format and port validation
  • Thread limit check
3

Session Initialization

A session is created through your proxy. The system detects the proxy’s geolocation to set the correct timezone and language, then generates the initial session token.
4

Immediate Completion Check

If the session token contains sup=1, no interactive step is required and the result token is returned immediately. This is the fastest path.
5

Interactive Processing

If an interactive step is required, the system parses the flow type, variant, and number of rounds, then processes each round until completion or timeout.
6

Result Available

Once complete, the result is stored with a 120-second TTL. Poll GET /getTaskResult/{taskId} to retrieve it.

​
Task Statuses

​
Timeouts

Results expire 120 seconds after completion. Make sure to poll frequently enough to retrieve your result token before it expires.

​
Balance & Refunds

Balance-based (FUN-) keys are charged when a task starts processing and automatically refunded if the task fails. See Authentication for billing details.

​
Polling

Poll GET /getTaskResult/{taskId} every 0.5 seconds. Results expire 120 seconds after completion — see Get Task Result for the full polling reference.