Token API Quick Guide
---
### General Rules
- The UserAgent field must begin with a string from the *AllowedUserAgents* list configured on the server.
- If a *SiteKeyUserAgents* list exists for a given SiteKey, the supplied UserAgent must match one of those entries exactly.
---
## 1.
Starts a token‑generation task.
### Request Body
### Example cURL
### Possible Error Responses
| Code | Meaning |
|------|---------|
| ERROR_API_KEY | API key missing or invalid |
| ERROR_MISSING_BLOB • ERROR_MISSING_USER_AGENT • ERROR_MISSING_SITE_KEY • ERROR_MISSING_SITE_URL | Required field is missing |
| UNSUPPORTED_USER_AGENT | UA not in AllowedUserAgents |
| UNSUPPORTED_SITE_KEY | Unsupported SiteKey |
| SITEKEY_USER_AGENT_MISMATCH | UA does not match the list for that SiteKey |
| ERROR_NO_BALANCE | No remaining credit |
| ERROR_RATE_LIMIT | Too many createTask requests |
---
## 2.
Checks the status of an existing task.
### Parameters
- sessionId – ID returned from
- apiKey (query) – the same API key used to create the task
### Example cURL
### Responses
- Still processing
- On success
- On failure
> ERROR_INVALID_TASK_DATA or ERROR_API_KEY_MISMATCH are returned if the session ID is unknown or the API key does not match.
---
## 3.
Returns the remaining credit for the specified API key.
### Query Parameter
- apiKey – the user's API key
### Example cURL
### Notes (applies only to getBalance)
- If the X‑Forwarded‑For header is present, the request is rejected with ERROR_FORBIDDEN_HEADER.
- Requests from the same IP are limited to one per second (ERROR_RATE_LIMIT).
---
## Common Error Codes
| Code | Meaning |
|------|---------|
| ERROR_API_KEY | Invalid or missing API key |
| ERROR_NO_BALANCE | Insufficient credit |
| ERROR_RATE_LIMIT | Rate limit exceeded |
| UNSUPPORTED_USER_AGENT | UA not whitelisted |
| UNSUPPORTED_SITE_KEY | SiteKey not supported |
| SITEKEY_USER_AGENT_MISMATCH | UA does not match SiteKey list |
| ERROR_INVALID_TASK_DATA | Unknown session ID |
| ERROR_API_KEY_MISMATCH | Session does not belong to provided key |
| FAILED | Solver reported failure (see message) |
---
### General Rules
- The UserAgent field must begin with a string from the *AllowedUserAgents* list configured on the server.
- If a *SiteKeyUserAgents* list exists for a given SiteKey, the supplied UserAgent must match one of those entries exactly.
---
## 1.
POST /api/token/createTaskStarts a token‑generation task.
### Request Body
{
"ApiKey": "string", // required
"Blob": "string", // URL‑encoded challenge blob
"UserAgent":"string", // must satisfy the rules above
"Proxy": { // optional
"Address": "host:port",
"Username": "proxyUser",
"Password": "proxyPass"
},
"SiteKey": "string", // one of SupportedSiteKeys
"SiteUrl": "https://example.com"
}### Example cURL
curl -X POST http://37.27.240.144:5000/api/token/createTask -H "Content-Type: application/json" -d '{
"ApiKey": "YOUR_API_KEY",
"Blob": "BASE64_OR_URL_ENCODED_BLOB",
"UserAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64)...",
"SiteKey": "2CB16598-CB82-4CF7-B332-5990DB66F3AB",
"SiteUrl": "https://example.com"
}'### Possible Error Responses
| Code | Meaning |
|------|---------|
| ERROR_API_KEY | API key missing or invalid |
| ERROR_MISSING_BLOB • ERROR_MISSING_USER_AGENT • ERROR_MISSING_SITE_KEY • ERROR_MISSING_SITE_URL | Required field is missing |
| UNSUPPORTED_USER_AGENT | UA not in AllowedUserAgents |
| UNSUPPORTED_SITE_KEY | Unsupported SiteKey |
| SITEKEY_USER_AGENT_MISMATCH | UA does not match the list for that SiteKey |
| ERROR_NO_BALANCE | No remaining credit |
| ERROR_RATE_LIMIT | Too many createTask requests |
---
## 2.
GET /api/token/getTask/{sessionId}Checks the status of an existing task.
### Parameters
- sessionId – ID returned from
createTask- apiKey (query) – the same API key used to create the task
### Example cURL
curl "http://37.27.240.144:5000/api/token/getTask/<SESSION_ID>?apiKey=YOUR_API_KEY"
### Responses
- Still processing
{ "success": false, "taskType": "PROCESSING" }
- On success
{ "success": true, "taskType": "SUCCESS", "token": "<token>" }
- On failure
{ "success": false, "taskType": "FAILED", "message": "<error>" }
> ERROR_INVALID_TASK_DATA or ERROR_API_KEY_MISMATCH are returned if the session ID is unknown or the API key does not match.
---
## 3.
GET /api/token/getBalanceReturns the remaining credit for the specified API key.
### Query Parameter
- apiKey – the user's API key
### Example cURL
curl "http://37.27.240.144:5000/api/token/getBalance?apiKey=YOUR_API_KEY"
### Notes (applies only to getBalance)
- If the X‑Forwarded‑For header is present, the request is rejected with ERROR_FORBIDDEN_HEADER.
- Requests from the same IP are limited to one per second (ERROR_RATE_LIMIT).
---
## Common Error Codes
| Code | Meaning |
|------|---------|
| ERROR_API_KEY | Invalid or missing API key |
| ERROR_NO_BALANCE | Insufficient credit |
| ERROR_RATE_LIMIT | Rate limit exceeded |
| UNSUPPORTED_USER_AGENT | UA not whitelisted |
| UNSUPPORTED_SITE_KEY | SiteKey not supported |
| SITEKEY_USER_AGENT_MISMATCH | UA does not match SiteKey list |
| ERROR_INVALID_TASK_DATA | Unknown session ID |
| ERROR_API_KEY_MISMATCH | Session does not belong to provided key |
| FAILED | Solver reported failure (see message) |
CodeSolvers pinned «Token API Quick Guide --- ### General Rules - The UserAgent field must begin with a string from the *AllowedUserAgents* list configured on the server. - If a *SiteKeyUserAgents* list exists for a given SiteKey, the supplied UserAgent must match one of those…»
CodeSolvers
Token API Quick Guide --- ### General Rules - The UserAgent field must begin with a string from the *AllowedUserAgents* list configured on the server. - If a *SiteKeyUserAgents* list exists for a given SiteKey, the supplied UserAgent must match one of those…
I felt the need to share this documentation again, because I see that some people are still sending incorrect requests (every request to the api is logged.) Please read this api documentation well when sending requests.
Solver will be updated, this process takes about 30 minutes and during this time you may receive late or no response to some of your requests.
As of today, the bonus rates for balance top-ups have changed.
300-600$ + %5
600-900$ + %10
1000$> + %20
For special offers please contact the Developer or @leoo312
300-600$ + %5
600-900$ + %10
1000$> + %20
For special offers please contact the Developer or @leoo312
"0152B4EB-D2DC-460A-89A1-629838B529C9": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
]
Super Fast 💪
"AllowedUserAgents": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36"
]
The user agent support list has been updated due to a change in the solver.
"867D55F2-24FD-4C56-AB6D-589EDAF5E7C5": [
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36"
]
Twitter mobile register user agent.
❤1
twitter register has been taken into maintenance. integrations will be provided by solver as we have previously discussed on the group.
👏2
Today there will be some changes in the rest api. The solver side is being improved.
👍1
🚨 REST API Update – New Feature!
We’ve made it easier for users having trouble generating BLOB values during Twitter registrations!
🎯 This update applies to the following SiteKeys:
- 867D55F2-24FD-4C56-AB6D-589EDAF5E7C5 → Twitter Mobile Register
- 2CB16598-CB82-4CF7-B332-5990DB66F3AB → Twitter Web Register
Now, by simply using the createTask method as shown below, the system will automatically generate the BLOB for you:
🧠 The solver will generate the BLOB internally and return a response like this:
✅ Important Note:
If you're having trouble generating your own BLOB, just set "Blob": "TWITTER_REGISTER" and the system will handle the rest automatically.
For any questions, feel free to reach out to our support team.
We’ve made it easier for users having trouble generating BLOB values during Twitter registrations!
🎯 This update applies to the following SiteKeys:
- 867D55F2-24FD-4C56-AB6D-589EDAF5E7C5 → Twitter Mobile Register
- 2CB16598-CB82-4CF7-B332-5990DB66F3AB → Twitter Web Register
Now, by simply using the createTask method as shown below, the system will automatically generate the BLOB for you:
{
"ApiKey": "YOUR_API_KEY",
"Blob": "TWITTER_REGISTER",
"UserAgent": "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36",
"Proxy": null,
"SiteKey": "867D55F2-24FD-4C56-AB6D-589EDAF5E7C5",
"SiteUrl": "https://x.com/i/flow/signup"
}🧠 The solver will generate the BLOB internally and return a response like this:
{
"success": true,
"taskType": "SUCCESS",
"token": "...",
"solverDetails": {
"flow_token": "...",
"cookie": "{...}",
"useragent": "...",
"sec-ch-ua": [...]
}
}✅ Important Note:
If you're having trouble generating your own BLOB, just set "Blob": "TWITTER_REGISTER" and the system will handle the rest automatically.
For any questions, feel free to reach out to our support team.
Restapi and Solver are currently being updated, this update will take about 20 minutes.
main server restarted. waiting for client servers to complete their transfers.
important announcement
For those who use “TWITTER_REGISTER” in the blob section, please start your requests with the callbacks that come after the first task.json after transferring the cookies to your software. then continue with the begin verification url, this would be my advice :)
For those who use “TWITTER_REGISTER” in the blob section, please start your requests with the callbacks that come after the first task.json after transferring the cookies to your software. then continue with the begin verification url, this would be my advice :)
"AllowedUserAgents": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Mobile Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36"
],
"SiteKeyUserAgents": {
"2CB16598-CB82-4CF7-B332-5990DB66F3AB": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
],
"0152B4EB-D2DC-460A-89A1-629838B529C9": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
],
"867D55F2-24FD-4C56-AB6D-589EDAF5E7C5": [
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Mobile Safari/537.36",
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36"
]
}
update solver has been updated to work with a wide variety of user agents.
There will be more updates tomorrow.
also solver is now freed to solve long game waves.
all client servers will be restored soon.
"Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Mobile Safari/537.36"
this useragent seems to be working very healthy now. with the improved bda gen, we will continue our way to more flawless service in 1-2 days, stay tuned
"0152B4EB-D2DC-460A-89A1-629838B529C9": [
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
]
problem fixed.