Every SDK has a set of error codes that can be thrown. They’re all named similarly, so this page applies to every SDK.
You can replace any instance of <app_id>.tsar.app with the app’s custom hostname or use a vanity in place of the app ID.
User-facing Errors
These are errors that are most common and can typically be fixed by the user.
Unauthorized (401)
Most of the time, this means that your HWID (or IP region) does not match the info stored on TSAR. To fix this, you must update your HWID by visiting https://<app_id>.tsar.app/auth/<new_hwid>.
Typically the SDK should automatically open your browser to that exact URL whenever this error is thrown.
Another common reason why this error could occur is if you have a subscription, but it’s tier is too low to access the software.
Other uncommon reasons why this error could occur are if your user object does not exist, or if your subscription expired. Normally these cases can be fixed by just visiting the auth link and re-subscribing.
Hash Unauthorized (403)
This simply means that the software you are running has a hash that the app does not approve of.
If you’re a user, download the latest software version at https://<app_id>.tsar.app/assets.
If you’re a developer, either upload your executable to the app’s assets page, or disable hash checks by going to https://tsar.cc/dash/<app_id> and turning off “Authenticate Software”.
App Paused (503)
This means that the app is paused.
If you’re a developer, you can unpause your app at https://tsar.cc/dash/<app_id>.
Tampered Response / State Mismatch
This either means that you’re using software that’s been tampered with, or that your local time is desynced.
Try going to your computer’s settings and syncing your clock. If this does not fix the issue, re-download the software as you may be using a bad version.
Rate Limited (429)
This error means that you’re sending requests too fast. Ensure that you dont have multiple apps open, and try again.
If you’re a developer, watch out for low-cooldown while loops; especially heart-beat checks.
A good rule of thumb is waiting at least 5 seconds before repeating a request to the same endpoint.
Server Error (500)
This means that the TSAR API returned an unusual error code. Please contact TSAR staff at https://tsar.cc/support to get help.
Request Failed
Most likely there’s an issue with the user’s network.
Here’s different methods of fixing this issue:
- Use a VPN (Temporary fix)
- Switch DNS servers (Permanant fix).
1.1.1.1 is recommended. Change DNS Tutorial
- Clear DNS cache (Permanant fix)
Developer-facing Errors
These are errors that are typically caused by developers, and need to be fixed by developers.
App Not Found (404)
This error gets thrown if the app ID that you’re passing to the SDK does not match a proper TSAR app.
Verify your app ID by going to https://tsar.cc/dash/<app_id>/configure, and copying your app ID from the top (or URL).
Bad Request (400)
This error should never happen if you’re using the SDK properly. This error is caused by not including required data in the request sent to the TSAR servers.
To fix this issue, verify that the request sent to the TSAR API contains the app ID, HWID, program hash, or session depending on the endpoint.
These values should be passed as query parameters.
Invalid App ID / Invalid Client Key
This error happens when the format of your app ID or Client Key is invalid. Verify that the formats of these values look the same as the examples.
- Example app ID:
f911842b-5b3d-4c59-b5d1-4adb8f71557b
- Example Client Key:
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEvJrwPvdeDUcV8Qr02tzgFrp+8qfCV/vG1HcQJYYV8u5vYUfGABMAYT0qOQltXEX9DTcB2fzLfwQnl7yiAaNruQ==
Failed To Decode
This error means that the SDK failed to decode a response returned by the TSAR API.
This error happens when your Client Decryption Key (client_key) or app ID are wrong.
Verify that both values are correct by visiting https://tsar.cc/dash/<app_id>/configure. Also reference the “Invalid App ID / Invalid Client Key” error above for format examples of the app ID and Client Key.
Other Rare Errors
These dont typically happen unless something is really wrong.
Failed To Get HWID
This means that the SDK failed to get your computer’s hardware ID. Ensure that you are using a supported operating system (Windows 10/11, MacOS, Linux).
If you’re a developer, make sure that the SDK you’re using is not broken. We recommend that you update your SDK regularely by visiting our GitHub.
Failed To Get Hash
This means that the SDK failed to get the program’s hash. Ensure that you are using a supported operating system (Windows 10/11, MacOS, Linux).
If you’re a developer, make sure that the SDK you’re using is not broken. We recommend that you update your SDK regularely by visiting our GitHub. 
