Twitter Reg and Unlock Active, Thank you to those who helped during the test phases. 💪 You can use high thread⚡️
❤1
there will be a momentary interruption on the main server. unfortunately, the tasks you have thrown due to this interruption will be deleted from memory and you need to create them again. sorry for the inconvenience, we are working to serve you better.
❤2
*** NEW END POİNT ***
🌟 API Documentation 🌟
---
## 📌 General Information
- Base URL: http://136.243.62.184:5000/api/Token/
- API Key: Each request must include the apiKey parameter.
- Response Format: All responses are in JSON format.
---
## 1. Create a New Task
🔗 URL:
http://136.243.62.184:5000/api/Token/createTask?ApiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- ApiKey (string, required): The user's API key.
📥 Successful Response:
{
"message": "Token request without proxy added to queue.",
"sessionId": "5a627e54-c9bc-4261-9a94-bcb67896374f",
"taskType": "SUCCESS"
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid or missing API key.
- ERROR_API_SERVICE: API is under maintenance.
- ERROR_RATE_LIMIT: Rate limit exceeded.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_INVALID_TASK_DATA: Invalid task data.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 2. Get Token by Session ID
🔗 URL:
http://136.243.62.184:5000/api/Token/getTask/SESSIONID?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- sessionId (string, required): The session ID of the task.
- apiKey (string, required): The user's API key.
📥 Successful Response (Token Ready):
{
"success": true,
"taskType": "SUCCESS",
"token": "token_value"
}
📥 Processing Response (Token Not Ready Yet):
{
"success": false,
"taskType": "PROCESSING",
"message": "The token is not ready yet."
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_INVALID_TASK_DATA: Invalid session ID.
- ERROR_WRONG_ENDPOINT: Wrong endpoint usage.
- ERROR_NOT_FOUND_USER: User not found.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 3. Submit Unlock Request
🔗 URL:
http://136.243.62.184:5000/api/Token/createUnlockTask?apiKey=APIKEY
🛠 Method:
POST
📋 Parameters:
- apiKey (string, required): The user's API key.
📥 Request Body:
- If no blob: Leave the body empty.
- If blob is required:
{
"blob": "blablabla"
}
📥 Successful Response:
{
"Message": "Task Created Successfully.",
"SessionId": "session_id_value",
"taskType": "SUCCESS"
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_API_SERVICE: API is under maintenance.
- ERROR_RATE_LIMIT: Rate limit exceeded.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_BLOB_MISSING: Required blob value not provided.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 4. Retrieve Unlock Token by Session ID
🔗 URL:
http://136.243.62.184:5000/api/Token/getUnlockTask/SESSIONID?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- sessionId (string, required): The session ID of the unlock task.
- apiKey (string, required): The user's API key.
📥 Successful Response:
{
"success": true,
"taskType": "SUCCESS",
"token": "unlock_token_value"
}
📥 Processing Response:
{
"success": false,
"taskType": "PROCESSING",
"message": "No available tokens at the moment."
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_INVALID_TASK_DATA: Invalid session ID.
- ERROR_WRONG_ENDPOINT: Wrong endpoint usage.
- ERROR_TASK_TIMEOUT: Session timed out.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 5. Check Your Balance
🔗 URL:
http://136.243.62.184:5000/api/Token/getBalance?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- apiKey (string, required): The user's API key.
📥 Successful Response:
{
"success": true,
"taskType": "SUCCESS",
"creditToken": 99997
}
📥 Possible Error Response:
- ERROR_API_KEY: Invalid or missing API key.
---
## 🚨 Error Statuses
Possible values for taskType in responses:
🌟 API Documentation 🌟
---
## 📌 General Information
- Base URL: http://136.243.62.184:5000/api/Token/
- API Key: Each request must include the apiKey parameter.
- Response Format: All responses are in JSON format.
---
## 1. Create a New Task
🔗 URL:
http://136.243.62.184:5000/api/Token/createTask?ApiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- ApiKey (string, required): The user's API key.
📥 Successful Response:
{
"message": "Token request without proxy added to queue.",
"sessionId": "5a627e54-c9bc-4261-9a94-bcb67896374f",
"taskType": "SUCCESS"
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid or missing API key.
- ERROR_API_SERVICE: API is under maintenance.
- ERROR_RATE_LIMIT: Rate limit exceeded.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_INVALID_TASK_DATA: Invalid task data.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 2. Get Token by Session ID
🔗 URL:
http://136.243.62.184:5000/api/Token/getTask/SESSIONID?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- sessionId (string, required): The session ID of the task.
- apiKey (string, required): The user's API key.
📥 Successful Response (Token Ready):
{
"success": true,
"taskType": "SUCCESS",
"token": "token_value"
}
📥 Processing Response (Token Not Ready Yet):
{
"success": false,
"taskType": "PROCESSING",
"message": "The token is not ready yet."
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_INVALID_TASK_DATA: Invalid session ID.
- ERROR_WRONG_ENDPOINT: Wrong endpoint usage.
- ERROR_NOT_FOUND_USER: User not found.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 3. Submit Unlock Request
🔗 URL:
http://136.243.62.184:5000/api/Token/createUnlockTask?apiKey=APIKEY
🛠 Method:
POST
📋 Parameters:
- apiKey (string, required): The user's API key.
📥 Request Body:
- If no blob: Leave the body empty.
- If blob is required:
{
"blob": "blablabla"
}
📥 Successful Response:
{
"Message": "Task Created Successfully.",
"SessionId": "session_id_value",
"taskType": "SUCCESS"
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_API_SERVICE: API is under maintenance.
- ERROR_RATE_LIMIT: Rate limit exceeded.
- ERROR_NO_BALANCE: Insufficient balance.
- ERROR_BLOB_MISSING: Required blob value not provided.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 4. Retrieve Unlock Token by Session ID
🔗 URL:
http://136.243.62.184:5000/api/Token/getUnlockTask/SESSIONID?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- sessionId (string, required): The session ID of the unlock task.
- apiKey (string, required): The user's API key.
📥 Successful Response:
{
"success": true,
"taskType": "SUCCESS",
"token": "unlock_token_value"
}
📥 Processing Response:
{
"success": false,
"taskType": "PROCESSING",
"message": "No available tokens at the moment."
}
📥 Possible Error Responses:
- ERROR_API_KEY: Invalid API key.
- ERROR_INVALID_TASK_DATA: Invalid session ID.
- ERROR_WRONG_ENDPOINT: Wrong endpoint usage.
- ERROR_TASK_TIMEOUT: Session timed out.
- ERROR_UNKNOWN: An unknown error occurred.
---
## 5. Check Your Balance
🔗 URL:
http://136.243.62.184:5000/api/Token/getBalance?apiKey=APIKEY
🛠 Method:
GET
📋 Parameters:
- apiKey (string, required): The user's API key.
📥 Successful Response:
{
"success": true,
"taskType": "SUCCESS",
"creditToken": 99997
}
📥 Possible Error Response:
- ERROR_API_KEY: Invalid or missing API key.
---
## 🚨 Error Statuses
Possible values for taskType in responses:
SUCCESS // Task completed successfully.
PROCESSING // Task is being processed or token not ready yet.
ERROR_API_KEY // Invalid or missing API key.
ERROR_API_SERVICE // API is under maintenance.
ERROR_PROXY_ADDRESS // Proxy address issue.
ERROR_PROXY_USERNAME_PASSWORD // Incorrect proxy credentials.
ERROR_RATE_LIMIT // Rate limit exceeded.
ERROR_NO_BALANCE // Insufficient balance.
ERROR_INVALID_TASK_DATA // Invalid task data.
ERROR_TASK_TIMEOUT // Task timed out.
ERROR_NOT_FOUND_USER // User not found.
ERROR_WRONG_ENDPOINT // Wrong endpoint usage.
ERROR_BLOB_MISSING // Blob value required but not provided.
ERROR_NO_AVAILABLE_TASK // No available tasks.
ERROR_UNKNOWN // Unknown error.
PROCESSING // Task is being processed or token not ready yet.
ERROR_API_KEY // Invalid or missing API key.
ERROR_API_SERVICE // API is under maintenance.
ERROR_PROXY_ADDRESS // Proxy address issue.
ERROR_PROXY_USERNAME_PASSWORD // Incorrect proxy credentials.
ERROR_RATE_LIMIT // Rate limit exceeded.
ERROR_NO_BALANCE // Insufficient balance.
ERROR_INVALID_TASK_DATA // Invalid task data.
ERROR_TASK_TIMEOUT // Task timed out.
ERROR_NOT_FOUND_USER // User not found.
ERROR_WRONG_ENDPOINT // Wrong endpoint usage.
ERROR_BLOB_MISSING // Blob value required but not provided.
ERROR_NO_AVAILABLE_TASK // No available tasks.
ERROR_UNKNOWN // Unknown error.
CodeSolvers pinned «*** NEW END POİNT *** 🌟 API Documentation 🌟 --- ## 📌 General Information - Base URL: http://136.243.62.184:5000/api/Token/ - API Key: Each request must include the apiKey parameter. - Response Format: All responses are in JSON format. --- ## 1. Create…»
please contact us for any problems, questions or suggestions: @leonardoo123 and @PlusSolverSupport
We turn off the reg and unlock workers for an update and will be active again in 10-15 minutes.
🔥𝐎𝐮𝐫 𝐓𝐰𝐢𝐭𝐭𝐞𝐫 𝐆𝐞𝐧 𝐚𝐧𝐝 𝐔𝐧𝐥𝐨𝐜𝐤 𝐓𝐨𝐤𝐞𝐧 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐢𝐬 𝐀𝐜𝐭𝐢𝐯𝐞!🔥
𝐓𝐡𝐞 𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐰𝐞 𝐨𝐟𝐟𝐞𝐫 𝐲𝐨𝐮:
𝐓𝐨𝐤𝐞𝐧 𝐟𝐨𝐫 𝐓𝐰𝐢𝐭𝐭𝐞𝐫 𝐚𝐜𝐜𝐨𝐮𝐧𝐭 𝐜𝐫𝐞𝐚𝐭𝐢𝐨𝐧(𝐏𝐫𝐨𝐱𝐲𝐥𝐞𝐬𝐬)
𝐓𝐰𝐢𝐭𝐭𝐞𝐫 𝐭𝐨𝐤𝐞𝐧𝐬 𝐭𝐨 𝐮𝐧𝐥𝐨𝐜𝐤 𝐥𝐨𝐜𝐤𝐞𝐝 𝐚𝐜𝐜𝐨𝐮𝐧𝐭𝐬 (𝐏𝐫𝐨𝐱𝐲𝐥𝐞𝐬𝐬)
𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐬𝐢𝐭𝐞 𝐤𝐞𝐲: 𝟖𝟔𝟕𝐃𝟓𝟓𝐅𝟐-𝟐𝟒𝐅𝐃-𝟒𝐂𝟓𝟔-𝐀𝐁𝟔𝐃-𝟓𝟖𝟗𝐄𝐃𝐀𝐅𝟓𝐄𝟕𝐂𝟓
𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐬𝐢𝐭𝐞 𝐤𝐞𝐲: 𝟎𝟏𝟓𝟐𝐁𝟒𝐄𝐁-𝐃𝟐𝐃𝐂-𝟒𝟔𝟎𝐀-𝟖𝟗𝐀𝟏-𝟔𝟐𝟗𝟖𝟑𝟖𝐁𝟓𝟐𝟗𝐂𝟗
𝐈 𝐛𝐞𝐭 𝐢𝐭'𝐬 𝐛𝐞𝐭𝐭𝐞𝐫 𝐭𝐡𝐚𝐧 𝐚𝐧𝐲 𝐭𝐨𝐤𝐞𝐧 𝐬𝐞𝐫𝐯𝐢𝐜𝐞 𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐫𝐢𝐠𝐡𝐭 𝐧𝐨𝐰!
𝐓𝐨𝐤𝐞𝐧 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐩𝐞𝐫 𝐦𝐢𝐧𝐮𝐭𝐞: 𝟏𝟐𝟎𝟎 𝐭𝐨𝐤𝐞𝐧𝐬
𝐓𝐨𝐤𝐞𝐧 𝐕𝐚𝐥𝐢𝐝𝐢𝐭𝐲 𝐑𝐚𝐭𝐞: %𝟗𝟗
𝟏𝟎𝟎𝟎 𝐓𝐨𝐤𝐞𝐧𝐬 𝐟𝐨𝐫 𝐨𝐧𝐥𝐲 𝟏$
𝐏𝐫𝐢𝐜𝐞𝐬 𝐚𝐫𝐞 𝐯𝐞𝐫𝐲 𝐥𝐨𝐰 𝐟𝐨𝐫 𝐡𝐢𝐠𝐡 𝐩𝐮𝐫𝐜𝐡𝐚𝐬𝐞𝐬!
𝐂𝐨𝐧𝐭𝐚𝐜𝐭 𝐦𝐞 𝐨𝐧 𝐭𝐞𝐥𝐞𝐠𝐫𝐚𝐦 𝐭𝐨 𝐭𝐫𝐲 𝐢𝐭 𝐨𝐫 𝐭𝐨 𝐠𝐞𝐭 𝐢𝐧𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧: @PlusSolverSupport - @leonardoo123
𝐓𝐡𝐞 𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐰𝐞 𝐨𝐟𝐟𝐞𝐫 𝐲𝐨𝐮:
𝐓𝐨𝐤𝐞𝐧 𝐟𝐨𝐫 𝐓𝐰𝐢𝐭𝐭𝐞𝐫 𝐚𝐜𝐜𝐨𝐮𝐧𝐭 𝐜𝐫𝐞𝐚𝐭𝐢𝐨𝐧(𝐏𝐫𝐨𝐱𝐲𝐥𝐞𝐬𝐬)
𝐓𝐰𝐢𝐭𝐭𝐞𝐫 𝐭𝐨𝐤𝐞𝐧𝐬 𝐭𝐨 𝐮𝐧𝐥𝐨𝐜𝐤 𝐥𝐨𝐜𝐤𝐞𝐝 𝐚𝐜𝐜𝐨𝐮𝐧𝐭𝐬 (𝐏𝐫𝐨𝐱𝐲𝐥𝐞𝐬𝐬)
𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐬𝐢𝐭𝐞 𝐤𝐞𝐲: 𝟖𝟔𝟕𝐃𝟓𝟓𝐅𝟐-𝟐𝟒𝐅𝐃-𝟒𝐂𝟓𝟔-𝐀𝐁𝟔𝐃-𝟓𝟖𝟗𝐄𝐃𝐀𝐅𝟓𝐄𝟕𝐂𝟓
𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐬𝐢𝐭𝐞 𝐤𝐞𝐲: 𝟎𝟏𝟓𝟐𝐁𝟒𝐄𝐁-𝐃𝟐𝐃𝐂-𝟒𝟔𝟎𝐀-𝟖𝟗𝐀𝟏-𝟔𝟐𝟗𝟖𝟑𝟖𝐁𝟓𝟐𝟗𝐂𝟗
𝐈 𝐛𝐞𝐭 𝐢𝐭'𝐬 𝐛𝐞𝐭𝐭𝐞𝐫 𝐭𝐡𝐚𝐧 𝐚𝐧𝐲 𝐭𝐨𝐤𝐞𝐧 𝐬𝐞𝐫𝐯𝐢𝐜𝐞 𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐫𝐢𝐠𝐡𝐭 𝐧𝐨𝐰!
𝐓𝐨𝐤𝐞𝐧 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐩𝐞𝐫 𝐦𝐢𝐧𝐮𝐭𝐞: 𝟏𝟐𝟎𝟎 𝐭𝐨𝐤𝐞𝐧𝐬
𝐓𝐨𝐤𝐞𝐧 𝐕𝐚𝐥𝐢𝐝𝐢𝐭𝐲 𝐑𝐚𝐭𝐞: %𝟗𝟗
𝟏𝟎𝟎𝟎 𝐓𝐨𝐤𝐞𝐧𝐬 𝐟𝐨𝐫 𝐨𝐧𝐥𝐲 𝟏$
𝐏𝐫𝐢𝐜𝐞𝐬 𝐚𝐫𝐞 𝐯𝐞𝐫𝐲 𝐥𝐨𝐰 𝐟𝐨𝐫 𝐡𝐢𝐠𝐡 𝐩𝐮𝐫𝐜𝐡𝐚𝐬𝐞𝐬!
𝐂𝐨𝐧𝐭𝐚𝐜𝐭 𝐦𝐞 𝐨𝐧 𝐭𝐞𝐥𝐞𝐠𝐫𝐚𝐦 𝐭𝐨 𝐭𝐫𝐲 𝐢𝐭 𝐨𝐫 𝐭𝐨 𝐠𝐞𝐭 𝐢𝐧𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧: @PlusSolverSupport - @leonardoo123
We're fixing a small issue with the app, so some of your requests may be unresponsive for the next few minutes.
In the face of too many requests coming to the server, we sometimes experience network drops, and we will take new measures to correct this situation.