List of TinEye API error messages

Here is a list of possible error messages returned from the TinEye API and a brief explanation of their causes.

You have no more searches available. Please purchase another bundle if you wish to make more searches.

You’ve run out of TinEye searches. This problem is very easy to fix: buy another search bundle and your searches will start working again. It’s also easy to prevent: if you buy a new bundle before your previous bundle is used up, TinEye will use the old bundle first and then seamlessly switch over to using the newer bundle.

Please provide a valid API key

The server did not receive a valid public API key, which must be included in each request. Common mistakes are using the private API key or making a copy-and-paste error with the public API key, such as adding spaces or other characters before or after the key, or accidentally missing some part of the key.

Must include valid API key in request

The server did not receive a valid public API key, which must be included in each request. Common mistakes are using the private API key or making a copy-and-paste error with the public API key, such as adding spaces or other characters before or after the key, or accidentally missing some part of the key.

Must provide nonce value for request

Nonce means a “number used once”, which for the API means a unique random string used to identify a request. The nonce must be a unique random string between 8 and 128 characters long. The nonce is used to prevent a “man in the middle attack”, where someone tries to repeat a request that a client has already made.

For more information please see the documentation on authentication.

Must provide a longer nonce value

The nonce value must be at least 8 characters long.

Must provide a shorter nonce value

The nonce value can not be longer than 128 characters.

Client nonce already used

The nonce value must be unique for each request.

Failed to find API request date/time

API requests must have a timestamp to prevent third parties from intercepting and repeating the request. The date value is the Unix epoch timestamp, the whole number of seconds since January 1, 1970 00:00:00 GMT. Requests must be made within 15 minutes of the server time or a “Request time is too skewed from server time” error will occur.

For more information please see the documentation on authentication.

Date format not supported, must be number of seconds since unix epoch

The date value should be an integer: the Unix epoch timestamp, the whole number of seconds since January 1, 1970 00:00:00 GMT.

Request time is too skewed from server time

The timestamp of the request is more than 15 minutes old.

Date format not recognized

The date value should be an integer: the Unix epoch timestamp, the whole number of seconds since January 1, 1970 00:00:00 GMT.

Please supply an image or a URL for searching

Search requests must include either an image file or an image URL, otherwise we have nothing to search for!

Couldn’t download URL

There was an error retrieving the image from the URL you searched for. This could happen for a number of reasons, the most common being that the image was removed or that you need to be logged in to access the image. If you are able to manually get the image from the URL, you could try uploading the data directly, rather than using the URL.