Error Messages

If you cause an error on the API related to authentication, verification or limits we will return a HTTP code of 401 unauthorized along with error messages. Your application can look for errors documented below. Other errors will come in the "meta" array/object of data returned along with your call. Rate limit errors will almost always be passed in the "meta" object of your call.

HTTP 401 Errors

Format for the errors is the following:

"error" => (string) error_id "error_string" => (string) descriptive error

The following is a list of error_ids with error strings that might be returned:

//The following is an application error and you should never get it //If you do, please contact support "error" => "invalid-auth-object", "error_string" => "Error: Wrong Authentication Objects Called" //These are for future use when we add new versions of the API "error" => "invalid-version", "error_string" => "Error: Incorrect Basic Auth Version or No Version Set" //If you pass along an APIKEY you will get the following error "error" => "invalid-api-key", "error_string" => "Error: Application must send in a valid API key" //If you pass along an invalid APIKEY you will get the following error "error" => "invalid-api-key", "error_string" => "Error: Application Consumer Key is incorrect" //If invalid credentials (username and/or password) are passed in "error" => "invalid-cred", "error_string" => "Error: Incorrect credentials or non-existant credentials" //Too many failed attempts on a particular user account "error" => "too-many-failed-attempts", "error_string" => "Error: Too Many Failed Attempts On This User" //If your application has been blocked for suspected abuse "error" => "application-blocked", "error_string" => "Error: Application is currently blocked" //If your application has been blocked by the user "error" => "application-user-blocked", "error_string" => "Error: Application is blocked by user"