Source

cerberus-docs / docs / updater / response-codes.rst

Cerberus Library Response Codes

The status shows whether the update will be accepted or rejected by the API.

200 Ok

Status: Accepted/Rejected

{"code": 200, "message": "Ok"}

If async mode is on you will always see this response even if there might be an error.

402 Resource exists

Status: Rejected

{"code": 402, "message": "Resource exists"}

Each host is only allowed to update a set of member data once.

403 Not allowed

Status: Rejected

{"code": 403, "message": "Not allowed"}

You may get this response if your account has not been activated yet.

404 Resource does not exist

Status: Rejected

{"code": 404, "message": "Resource does not exist"}

If you've modified the library then make sure that the API endpoints are correct.

501 Incorrect user agent

Status: Rejected

{"code": 501, "message": "Incorrect user agent"}

You must use Cerberus Updater 1.0 as the user agent. The library does set this automatically but if you use your own cURL method then you should set this appropriately.

502 Invalid remote host

Status: Rejected

{"code": 502, "message": "Invalid remote host"}

Make sure that your hostname matches the one you registered. Subdomains are counted as separate hosts. For example, www.domain.com requires a different access key from domain.com.

503 Unable to find access key

Status: Rejected

{"code": 503, "message": "Unable to find access key"}

You may see this response if there is a problem with Cerberus or if your account has been disabled.

504 Data too long

Status: Rejected

{"code": 504, "message": "Data too long"}

You can only send a maximum of 100 members at any one time. You may also see this response if you are using the test method and you try and send a message of more then 500 characters.

505 Unable to decrypt

Status: Rejected

{"code": 505, "message": "Unable to decrypt"}

Make sure that you use the correct access key for you host.

506 Invalid POST data

Status: Rejected

{"code": 506, "message": "Invalid POST data"}

You must make sure that you send an array of arrays of member data.

507 Invalid data format

Status: Rejected

{"code": 507, "message": "Invalid data format"}

You must send username, screen_name, email, ip_address and url keys in the member array.

508 Duplicate host update

Status: Rejected

{"code": 508, "message": "Duplicate host update"}

509 Unknown error

Status: Rejected

{"code": 509, "message": "Unknown error"}

This indicates a problem with the Cerberus network. Please try sending your data again.

510 Invalid member data

Status: Rejected

{"code": 510, "message": "Invalid member data"}

If you are sending data without validating it as a valid member registration then you may find that the member keys have invalid data.

511 Unable to base64 decode

Status: Rejected

{"code": 511, "message": "Unable to base64 decode"}

If you are encrypting and encoding the data with your own methods then you must replicate the original library functionality.

512 Unable to decode JSON

Status: Rejected

{"code" 512, "message": "Unable to decode JSON"}
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.