Need Help?

Analytics API Error Codes

Last Updated: Oct 30, 2015
This page lists most of the possible error codes that can be returned by the Luminoso Analytics API, along with their corresponding messages and the situations in which they occur. (There are a few other error codes that are not listed because it is unlikely that they would ever occur in practice.)



Message: User credentials missing from login request.

Either the "username" or the "password" parameter was not included in the form data posted to the login endpoint.


Message: User credentials invalid (incorrect username and/or password).

The username or password was incorrect when trying to log in or change your password.


Message: Signature has expired.

The expiration specified in the request has passed. Expirations are used in cases where a person receives an email that needs to be acted on within a set amount of time, such as accepting an invitation to an account, or resetting your password.


Message: Signature didn't match the request contents.

The signature specified on the request was not what it should have been given the request contents. Signatures are used for verifying parameters that come from email links (see SIG_EXPIRED above).

Token Authentication


Message: No authorization token was provided.

No token was provided in the "Authorization" header of the request. Refer to the API Guide for an explanation of token authentication.


Message: That token (<token>) does not exist.

A token doesn't exist (possibly it used to exist but has since expired); this can refer either to the token that was specified in the auth header or, for the /user/tokens/<token>/ endpoint, the token that was trying to be retrieved/deleted.


Message: Each user can only have one long-lived token at a time.

You tried to create a long-lived token but you already have one.


Message: A token cannot be used to authenticate its own deletion using this endpoint.

You tried to delete a token using the /user/tokens/<token>/ endpoint, but the request was authenticated with the token trying to be deleted. To delete a short-lived token, POST /user/logout/ should be used; to delete a long-lived token, you must authenticate using a short-lived token.



Message: You don't have <permission-level> permission on that resource (<resource>).

You tried to do something you are not allowed to do (for example, modify a project that you don't have "write" permission on, view an account that you don't have "read" permission on, etc.). It is possible that the reason you don't have permission on the resource is that it doesn't exist, so if you think it's something you should have permission on, check that you typed it correctly.


Message: A user with that username (<username>) already exists.

There already exists a user with the same username (email address) as the one you are trying to create.


Message: That user (<username>) already has permissions on that account (<account>).

You tried to invite some user to join an account, but the user already has permission on the account. To modify an existing user's permissions on an account, use PUT /accounts//users/<email>/permissions/. 


Message: That group (<group>) already has permissions on that resource (<resource>).

You tried to grant a sharing group permission on something it already has permission on.


Message: No account with that ID (<account>) exists.

You tried to do something to an account (for example, set it as your default account) that doesn't exist (or that you don't have permission on).


Message: No group with that name (<group>) exists.

You tried to do something to a sharing group that doesn't exist (or that you don't have permission on).

Type of input


Message: That content type (<content_type>) is not supported.

For example, you tried to upload documents but the content-type was not specified to be JSON.


Message: We were unable to decode the contents of the parameter <parameter>.

A request parameter was supposed to be JSON but was not valid JSON. Note that all request parameters that aren't numbers or strings (i.e., parameters that are lists, dictionaries, or booleans) should be JSON-encoded.


Message: The parameter <parameter> should be a list of dictionaries.


Message: The parameter <parameter> should be a list of strings.


Message: The parameter <parameter> should be a single dictionary.


Message: The parameter <parameter> should be a number.

Expected/unexpected inputs


Message: The command received an unexpected parameter (<parameter>).


Message: An invalid value (<value>) was supplied for a parameter (<parameter>).

For example, the parameter's value was a number that was larger than the maximum allowed.


Message: A required parameter (<parameter>) was missing from your call.

State of project


Message: This version of the database cannot be modified.

There is a storage format change in progress and this project has not been transitioned yet. You should wait a while (on the order of hours) and try again. This should never happen in production, because projects visible on production should have already been transitioned.


Message: That <resource-type> (<ID>) does not seem to exist.

You tried to access some object (such as a project, dashboard, worksheet, or widget) that doesn't exist (or that you don't have permission on).


Message: That topic (<topic-id>) does not seem to exist.


Message: That document (<document-id>) was not found in the database.


Message: That command will not work until the project has been fully built.

The project is currently building or rebuilding. Wait until it's done.


Message: The project does not contain any documents with timestamps.

You tried to get topic timeline correlations for a project that doesn't actually have any time information.  See the Document Fields page for how to specify dates.


Message: The project is currently being modified. Please try again later.

You tried to do something to the project while someone else was modifying its documents (adding, removing, etc). This should not happen very often, because modifying documents doesn't take very long; if it happens, just try again.


Message: A serious error has occurred in this project. Please contact Luminoso for technical assistance.



Message: That doesn't seem to be a known job number (<job-id>).


Message: There is another job (<job-id>) currently running. Please try again when it has finished.

You can only run one job (rebuilding the project or training the predictors) at a time.

External services


Message: There was an error sending the email.


Message: The maximum number of emails of that type (<email-type>) have already been sent to that address in the past 24 hours.

Our system limits the number of emails that it will send to any email address per day; this is primarily for the sake of password-recovery, which sends an email without requiring you to be logged in, and we don't want people to be able to use this to spam other people with password-recovery emails.

HTTP errors


Message: That endpoint (<path>) does not seem to exist.


Message: The method you tried is not allowed for that endpoint.

For example, POSTing to an endpoint that only allows GET.


Message: POST does not work for the /projects/ endpoint. Perhaps you meant to POST to /projects/<account>/?



Message: There was an error.
Some unexpected internal server error occurred.

More Support
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found