twitter register speed has been increased. maintenance work for unlock is in progress.

Please send a blob for unlocking, unfortunately we cannot provide a solution because you do not send a blob!

please send blobs for unlock tasks. find an example and it should be like the one below.

{
“blob“:”uHe5t1slR9uwC1q7. DlnWho9+Syhc1nYaZYPqMJwYnUPvnF1Q3W0pTptSlt5yE7oYRy80nUK7O/z6vlXVNVSWzTk7pG939r0ecQDZ/tx/PgrwcqtHIfT+OyzBA9VEseiV17LR0pUn83pRdY2hiFbLoR+Nt/Ukl35KsKLFTaUNx4dLpKPMx0jbgpqFvOQVU7elJEzstW79fBDtmQaMZMASFcCcDnKybuOzOxGsH08GCw2CmeqgEDIi1TVHY+4M+HZF1v8WN8XLccDMWeh+oVF+7H/DbOvR0XqXAn/QQfdcK7MMVGsXUzBQORGxMgmwcsnulXXqi9FpNp0O2cgTmL3BhYhe9yuFfMic0VpUhVlCWZWRnSzir4IDb15EGl0aJnFChZlzD+9DrcgV/R9v1d2PQs8w8Adclzqsqp/5FnO2xUynWcd78vyGmK/KL8/KTiR1FW1gOMK+LssjKXXvy0sLlFq7xGHKgDs4wsccwF2WjFj4uXBIm6Z/8Xmfax0w6YV3T0rqzE8IGXqWy/eLGBV931iIqqsudM1zqEw4gYvLXaT2n5qv6aTZn+36gA==”
}

Twitter reg and unlock proxyless solver speed has been improved. 💪🔥

Unlock has been taken back into maintenance due to instability⛔️

Our work for unlocking continues. 🧑‍💻

Reg Service is now much faster⚡️ Those who want to use high threads should contact us. ✅

There will be a short update. interruptions may occur⛔️

Reg service is active as low thread. Within 1 hour you can use High Thread. Thank you for your patience🫡

✅Reg system speed has been increased. You can use high thread⚡️

✅Reg system speed has been increased. You can use high thread⚡️

Our work for unlocking continues. 🧑‍💻

We are still working on twitter unlock.

✅Reg system speed has been increased. You can use high thread⚡️

Reg system speed has been increased. You can use high thread⚡️

Twitter Reg and Unlock Active, Thank you to those who helped during the test phases. 💪 You can use high thread⚡️

🔥Twitter reg and unlock proxyless solver speed has been improved🔥

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.

*** 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: