APIErrors – hyves_api

Context Navigation

Errors

Errors

Errornumber 1

Responseheader

HTTP/1.1 500 Internal Server Error

Message

Unknown error occurred.

Cause

The cause for this error is unknown, it is most likely an internal failure in the Hyves architecture. Try again later, or, if the problem persists, contact us with a clear description

Solution

Unknown.

Extra

Errornumber 2

Responseheader

HTTP/1.1 400 Bad Request

Message

Hyves Api method does not exist.

Cause

You are trying to call a method that doesn't exist in this version of the API. Some oauth_consumer_keys have access to less methods than other.

Solution

Check that your ha_version and ha_method parameters are correct. Also check that you are using the correct oauth_consumer_key.

Extra

This error may also be a result of incorrect url parameter escaping.

Errornumber 3

Responseheader

HTTP/1.1 400 Bad Request

Message

Hyves Api version does not exist.

Cause

The version you supplied in the ha_version parameter is not valid. Valid versions at the moment are "1.0" and "experimental".

Solution

Supply a valid Hyves API version number in the ha_version variable

Extra

Errornumber 4

Responseheader

HTTP/1.1 400 Bad Request

Message

OAuth version does not exist.

Cause

The supplied oAuth version in the oauth_version variable is invalid. At the moment only version 1.0 is valid

Solution

Give the oauth_version variable the value "1.0" (without quotes), or remove the oauth_version variable at all (this implies oauth_version=1.0)

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 5

Responseheader

HTTP/1.1 503 Service Unavailable

Message

Hyves Api temporary unavailable.

Cause

The Hyves API is temporarily unavailable. This is probably because we need to do some maintenance work

Solution

Try again at a later moment.

Extra

Errornumber 6

Responseheader

HTTP/1.1 403 Forbidden

Message

Hyves Api IP range restriction.

Cause

You are trying to do a call from an IP address that is not allowed to do this call. For security reasons we bind an oauth_consumer_key to specific ranges of ip addresses.

Solution

First, make sure that you are using the correct oauth_consumer_key (in case you have multiple, or, when you have a Desktop Application, make sure you use the Desktop Application key), and check that you have requested this key to be valid from the ip address you are on (the extended errormessage prints out the ip address the call comes from). If you require the key to be valid for more ip addresses you can change these settings yourself at http://www.hyves.nl/api/manage/

Extra

Errornumber 7

Responseheader

HTTP/1.1 400 Bad Request

Message

An illegal character was encountered.

Cause

The parameters that you supplied cannot be decoded to latin-1. Since we use latin-1 (ISO-8859-1) internally, we cannot accept any parameters that cannot be transcoded into latin-1.

Solution

Alter the parameters so that only latin-1 characters occur in them. The extended error should tell you which parameter causes the problem. Another solution might be to convert to UTF-8 since the API expects the UTF-8 charset, more info: <a href='http://www.hyves-developers.nl/documentation/data-api/content-encoding/'>http://www.hyves-developers.nl/documentation/data-api/content-encoding/</a>.

Extra

This error may also be a result of incorrect url parameter escaping.

Errornumber 8

Responseheader

HTTP/1.1 400 Bad Request

Message

Request-limit is exceeded for this IP address.

Cause

The request limit is exceeded for the requesting IP-address. This only occurs for ApiConsumer? registered as Desktop application.

Solution

Either wait a little while until the period the limit is for is over (hourly limits are per 60 minutes, daily limits per 24 hours, not necessarily until the next whole hour, or midnight). If you believe that your limit is too low, please contact us at hyves-api@….

Extra

Errornumber 10

Responseheader

HTTP/1.1 401 Unauthorized

Message

Invalid OAuth Consumer key.

Cause

The oauth_consumer_key you supplied is unknown.

Solution

Check your oauth_consumer_key. If you do not have an oauth_consumer_key, you can request one.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 11

Responseheader

HTTP/1.1 400 Bad Request

Message

OAuth signature method is unsupported.

Cause

The oauth_signature_method you supplied is unknown. At the moment we only support HMAC-SHA1 as oauth_signature_method. Please note that the HMAC-SHA1 should be put in capitals.

Solution

Give the oauth_signature_method the value "HMAC-SHA1" (without the quotes).

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 12

Responseheader

HTTP/1.1 401 Unauthorized

Message

OAuth signature is invalid.

Cause

The oauth_signature you supplied is not correct.

Solution

Supply the correct oauth_signature.

Extra

This error may also be a result of incorrect url parameter escaping.

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

See our example implementation

Errornumber 13

Responseheader

HTTP/1.1 400 Bad Request

Message

Required parameter(s) are missing.

Cause

You omitted a required parameter.

Solution

Check in the extended error message which parameter you omited, and supply it.

Extra

This error may also be a result of incorrect url parameter escaping.

Errornumber 14

Responseheader

HTTP/1.1 400 Bad Request

Message

Unknown parameter(s) given.

Cause

You supplied a parameter that was not expected.

Solution

Check in the extended error message which parameter was unexpected and remove it.

Extra

Errornumber 15

Responseheader

HTTP/1.1 400 Bad Request

Message

Hyves Api format is not available.

Cause

You supplied an unknown return format in the ha_format parameter. The value of ha_format should be either "xml" or "json" (without the quotes). Note that the value should be lowercase. If you supply an ha_callback, the result will transformed to xmlp or jsonp automatically.

Solution

Give the ha_format the value "xml" or "json" (without quotes)

Extra

Errornumber 16

Responseheader

HTTP/1.1 401 Unauthorized

Message

OAuth timestamp is invalid.

Cause

The oauth_timestamp variable is invalid. For more information, see <a href='http://www.hyves-developers.nl/documentation/data-api/oauth-parameters-hyves-api#oauth_timestamp'>oauth_timestamp parameter</a>.

Solution

Supply a correct value for oauth_timestamp.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 17

Responseheader

HTTP/1.1 401 Unauthorized

Message

OAuth token is invalid.

Cause

The oauth_token supplied is not valid. This can have several reasons, either we do not recognize the token, or the token is not valid. The token may loose its validity when a user revokes the token. Also see Errornr 25 and 31

Solution

Make sure the supplied token is correct. You may need to request a new token.

Extra

This error may also be a result of incorrect url parameter escaping.

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 18

Responseheader

HTTP/1.1 400 Bad Request

Message

OAuth Consumer request-limit is exceeded.

Cause

The ApiConsumer? has exceeded its limit. The Hyves API has hourly and daily limits for consumers.

Solution

Either wait a little while until the period the limit is for is over (hourly limits are per 60 minutes, daily limits per 24 hours, not necessarily until the next whole hour, or midnight). If you believe that your limit is too low, please contact us at hyves-api@….

Extra

Errornumber 19

Responseheader

HTTP/1.1 403 Forbidden

Message

OAuth token doesn't have permission for this method.

Cause

The auth_token you have supplied is not valid for the method you call. You probably requested an accesstoken with limited functionality.

Solution

Get an accesstoken which includes the called method, or call another method.

Extra

Errornumber 20

Responseheader

HTTP/1.1 503 Service Unavailable

Message

Hyves Api method temporary unavailable.

Cause

The method you requested in temporarily unavailable. We occasionally switch off specific methods for maintenance.

Solution

Try again at a later moment

Extra

Errornumber 21

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 22

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 23

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 24

Responseheader

HTTP/1.1 401 Unauthorized

Message

Request replay: a request with the provided timestamp/nonce combination was made before for this oauth_consumer_key

Cause

Each request should have a unique timestamp-nonce combination (either the oauth_timestamp, or the oauth_nonce (or both) should be different). This error indicates that the provided oauth_timestamp-oauth_nonce combination was used in a previous request. We suggest choosing your nonce so that the likely hood of getting this error is extremely small. See also <a href='http://www.hyves-developers.nl/documentation/data-api/oauth-parameters-hyves-api#oauth_nonce'>oauth_nonce parameter</a>.

Solution

Either change the oauth_timestamp or the oauth_nonce and try again.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 25

Responseheader

HTTP/1.1 401 Unauthorized

Message

The supplied token has expired

Cause

The supplied oauth_token has expired. Request tokens expire after 600 seconds. Access tokens are valid for 21600 seconds normally, and 3153600000 if an infinite token was requested (and obtained). The user may have changed the validity of an accesstoken when approving it. You have received the expiredate when the accesstoken was first obtained (through <a href='http://trac.hyves-api.nl/wiki/APIMethods/2.0/auth.accesstoken'>auth.accesstoken</a>).

Solution

Obtain a new token.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 26

Responseheader

HTTP/1.1 400 Bad Request

Message

The ha_callback variable has an illegal format.

Cause

The value provided for the ha_callback parameter is invalid. The ha_callback may not be longer than 20, and should conform to the following Regular Expression: /^{[A-Za-z0-9_\[\]\"'\.]*$/ .}

Solution

Provide a correct ha_callback

Extra

This error may also be a result of incorrect url parameter escaping.

Errornumber 27

Responseheader

HTTP/1.1 401 Unauthorized

Message

A requesttoken can only be used with the method auth.accesstoken.

Cause

You provided a request token as oauth_token, for a method that does not expect a request token. The only method that may be called with a request token is auth.accesstoken.

Solution

Supply an access token (or no token at all), or call the method auth.accesstoken.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 28

Responseheader

HTTP/1.1 401 Unauthorized

Message

An accesstoken cannot be used with the methods auth.requesttoken and auth.accesstoken.

Cause

You provided an access token in oauth_token, for a method that does not expect an access token. An access token can be used for all methods except auth.requesttoken and auth.accesstoken.

Solution

Supply a request token (or no token at all), or call another method.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 29

Responseheader

HTTP/1.1 400 Bad Request

Message

The authorization header has an illegal format.

Cause

The format of the Authorization HTTP-header was illegal. Please see the extended errormessage for the exact problem.

Solution

Fix the Authorization HTTP-header, use the information from the extended errormessage.

Extra

This error may also be a result of incorrect url parameter escaping.

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 30

Responseheader

HTTP/1.1 400 Bad Request

Message

A parameter was present more than once

Cause

Each parameter may be present only once. You either doubled a parameter in the query-string or the post variables, or a parameter is present in at least two of the three contexts query-string, post and Authorization HTTP-header. See the extended error message for more information.

Note: Sometimes two variables with the same name get compacted into one by our system without raising this error, so don't depend on it.

Solution

Remove the duplicate parameter

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 31

Responseheader

HTTP/1.1 401 Unauthorized

Message

The requesttoken used to obtain an accesstoken was not authorized

Cause

The request token used to obtain an access token has not been authorized. Please see the oAuth documentation on how to authorize a token.

Solution

Have the request token authorized first

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 32

Responseheader

HTTP/1.1 401 Unauthorized

Message

The requesttoken used to obtain an accesstoken was declined by the user

Cause

The request token used to obtain an access token was declined by the User. Please see the oAuth documentation on how to authorize a token.

Solution

none

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 33

Responseheader

HTTP/1.1 400 Bad Request

Message

The requested page doesn't exist.

Cause

The requested page doesn't exist; the page number should be an integer 1 or higher

Solution

Request a page number of 1 or higher.

Extra

Errornumber 34

Responseheader

HTTP/1.1 400 Bad Request

Message

The requested results per page exceeds limits.

Cause

The requested results per page exceeds limits. There is a lower limit of 1 and an upper limit of 100

Solution

Results per page are limited, try a lower results per page.

Extra

Errornumber 35

Responseheader

HTTP/1.1 400 Bad Request

Message

The method you used does not support pagination.

Cause

The ha_page and ha_resultsperpage are optional on paginated methods, and not allowed on other methods. The method you requested does not support pagination.

Solution

Remove the ha_page and ha_resultsperpage parameters from the request.

Extra

Errornumber 36

Responseheader

HTTP/1.1 400 Bad Request

Message

A responsefield in ha_responsefields is invalid.

Cause

A responsefield in ha_responsefields is invalid.

Solution

Provide a correct ha_responsefield parameter.

Extra

Errornumber 37

Responseheader

HTTP/1.1 400 Bad Request

Message

A responsefield in ha_responsefields is not supported for this method.

Cause

One of the ha_responsefield values is unsupported for this method.

Solution

Provide correct and supported ha_responsefield values.

Extra

Errornumber 38

Responseheader

HTTP/1.1 401 Unauthorized

Message

Partner is inactive.

Cause

The Api Partner is inactive.

Solution

Contact us for more information.

Extra

Errornumber 39

Responseheader

HTTP/1.1 401 Unauthorized

Message

OAuth Consumer is inactive.

Cause

The Api Consumer is inactive.

Solution

Contact us for more information.

Extra

Errornumber 40

Responseheader

HTTP/1.1 401 Unauthorized

Message

Partner didn't accept latest terms of use.

Cause

Partner didn't accept latest Terms of Use.

Solution

Accept latest Terms of Use at http://www.hyves.nl/api/manage/

Extra

Errornumber 41

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 42

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 43

Description

This error is for internal use only. If you receive it in reply to a call, please contact us at hyves-api@….

Errornumber 44

Responseheader

HTTP/1.1 401 Unauthorized

Message

Owner of this api consumer is not registered as OpenSocial developer

Cause

Solution

Extra

Errornumber 45

Responseheader

HTTP/1.1 400 Bad Request

Message

The HTTP protocol used is invalid for this method.

Cause

Solution

Extra

Errornumber 46

Responseheader

HTTP/1.1 400 Bad Request

Message

Invalid language given.

Cause

Solution

Extra

Errornumber 47

Responseheader

HTTP/1.1 400 Bad Request

Message

This version of OAuth requires oauth_callback and/or oauth_callback_confirmed parameter

Cause

Solution

Extra

Errornumber 48

Responseheader

HTTP/1.1 400 Bad Request

Message

This version of OAuth requires oauth_callback to be a valid URL

Cause

Solution

Extra

Errornumber 49

Responseheader

HTTP/1.1 400 Bad Request

Message

The HTTP method used is invalid for this API method

Cause

Solution

Extra

Errornumber 50

Responseheader

HTTP/1.1 401 Unauthorized

Message

The consumer used is expired for this session.

Cause

Solution

Extra

Errornumber 100

Responseheader

HTTP/1.1 404 Not Found

Message

Object does not exist.

Cause

The call you did returned no objects. This usually means there is a problem the parameters you sent to the function.

Note: This error is thrown only when objects that are child of another object are requested and we cannot find the parent object. If you use users.get with unknown ids, an empty array is returned. If you search for an unknown name, an empty array is returned. If you do wwws.getByUser with an unknown userid, this error is returned

Solution

Supply correct id to the method called

Extra

This error may also be a result of incorrect url parameter escaping.

Errornumber 101

Responseheader

HTTP/1.1 401 Unauthorized

Message

No access, (other)OAuth token required.

Cause

The operation you are trying to do is not allowed on the basis of your current authorization status. You either need to get an access token, or possibly an access token from a different user.

Solution

Get the correct access token needed for the operation.

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 102

Responseheader

HTTP/1.1 400 Bad Request

Message

You are not allowed to retrieve so many objects in one request.

Cause

We limit the number of parameters that can be given to a certain method, to avoid overloading the system. Your call exceeded this number.

Solution

Supply a shorter list of parameters to the call.

Extra

Errornumber 103

Responseheader

HTTP/1.1 401 Unauthorized

Message

Item not visible for current OAuth token.

Cause

The information you are trying to retrieve is not visible on the basis of your current authorization status. You either need to get an access token, or possibly an access token from a different user.

Solution

Get the correct access token needed for the requested information

Extra

For more information on oAuth, see <a href='http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/'>http://www.hyves-developers.nl/documentation/data-api/hyves-api-oauth/</a>.

Errornumber 104

Responseheader

HTTP/1.1 401 Unauthorized

Message

Item not writeable for current OAuth token.

Cause

Solution

Extra

Errornumber 110

Responseheader

HTTP/1.1 400 Bad Request

Message

Invalid data given.

Cause

The data you supplied did not validate. This error usually occurs when trying to create an object, when for instance a required property is left empty. It is used only if we have no specific errornumber for the error. Specific errors are in the 1000-2000 range.

Solution

Check all parameters for the call to see if they are correct. The extended errormessage should give more information on what goes wrong.

Extra

Errornumber 111

Responseheader

HTTP/1.1 400 Bad Request

Message

Invalid parameter value received.

Cause

One of the parameters supplied does not have valid content. This is an errormessage for parameters that support only a limited number of values (true/false, some enumerated value), and a not supported value was found.

Solution

Check all parameters for the call to see if they are correct. The extended errormessage should give more information on what goes wrong.

Extra

Errornumber 112

Responseheader

HTTP/1.1 400 Bad Request

Message

Invalid hyves type given.

Cause

Solution

Extra

Errornumber 1000

Responseheader

HTTP/1.1 400 Bad Request

Message

No title given.

Cause

Trying to create an item where a title is required.

Solution

Add 'title' parameter.

Extra

Errornumber 1001

Responseheader

HTTP/1.1 400 Bad Request

Message

Unknown visibility given.

Cause

Trying to create an item with a visibility not supported by the item.

Solution

Use a supported visibility.

Extra

Errornumber 1002

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal gadget html given.

Cause

Trying to create an gadget with illegal(unsupported by Hyves) gadget html.

Solution

Use supported Gadgets or request the gadget by submitting it to http://www.hyves.nl/?module=widget&action=showWidgetSpecs

Extra

Errornumber 1003

Responseheader

HTTP/1.1 400 Bad Request

Message

No where given.

Cause

Trying to create a www without the parameter 'where'.

Solution

Add 'where' parameter.

Extra

Errornumber 1004

Responseheader

HTTP/1.1 400 Bad Request

Message

Unkown listener type given.

Cause

Trying to create a listener with an unsupported type.

Solution

Use a supported listener type.

Extra

Errornumber 1005

Responseheader

HTTP/1.1 400 Bad Request

Message

No callback given.

Cause

Trying to create an object without a callback (which is required).

Solution

Add a callback parameter.

Extra

Errornumber 1006

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal callback given.

Cause

Trying to create an object with an illegal callback.

Solution

Add a supported callback (uri).

Extra

Errornumber 1007

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal methods given.

Cause

The methods parameter is incorrect.

Solution

Provide a correct methods parameter.

Extra

Errornumber 1008

Responseheader

HTTP/1.1 400 Bad Request

Message

No body given.

Cause

Trying to create an item without the parameter 'body'.

Solution

Add the 'body' parameter.

Extra

Errornumber 1009

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal body given.

Cause

Trying to create an item with an invalid value for the parameter 'body'.

Solution

Some content in the 'body' parameter is invalid (might be blacklisted), try posting other content.

Extra

Errornumber 1010

Responseheader

HTTP/1.1 400 Bad Request

Message

Creation rate limit reached.

Cause

Trying to create an item which is restricted to a creation limit.

Solution

Try again later.

Extra

Errornumber 1011

Responseheader

HTTP/1.1 400 Bad Request

Message

Creation failed since a similar item already exists.

Cause

Trying to create an item which was already created for given values (e.g. respect for a parent item).

Solution

Create the item for another parent item.

Extra

Errornumber 1012

Responseheader

HTTP/1.1 400 Bad Request

Message

Unkown respect type given.

Cause

Trying to create respect with an unsupported type.

Solution

Use a supported respect type.

Extra

Errornumber 1013

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal mobilenumber given.

Cause

Trying to update user with illegal mobilenumber.

Solution

Reformat the mobile number to a valid format. (e.g. +31123456789)

Extra

Errornumber 1014

Responseheader

HTTP/1.1 400 Bad Request

Message

Mobilenumber is already in use.

Cause

Trying to update user with mobilenumber that is already in use.

Solution

Use a mobile number that is not in use.

Extra

Errornumber 1015

Responseheader

HTTP/1.1 400 Bad Request

Message

Email address of member is not confirmed.

Cause

Trying to do an operation that requires a confirmed email address.

Solution

Let the user first confirm his or her email address at http://www.hyves.nl/confirmemail.

Extra

Errornumber 1016

Responseheader

HTTP/1.1 400 Bad Request

Message

Target object(s) does not exist.

Cause

Trying to do an operation that requires a target object which doesn't exist.

Solution

Provide a target object that does exist.

Extra

Errornumber 1017

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal geolocation (latitude / longitude).

Cause

Solution

Extra

Errornumber 1018

Responseheader

HTTP/1.1 400 Bad Request

Message

No bluetoothuid given.

Cause

Solution

Extra

Errornumber 1019

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal bluetoothuid.

Cause

Solution

Extra

Errornumber 1020

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal radius(meters) given.

Cause

Solution

Extra

Errornumber 1021

Responseheader

HTTP/1.1 400 Bad Request

Message

Unknown printability given.

Cause

Solution

Extra

Errornumber 1022

Responseheader

HTTP/1.1 400 Bad Request

Message

Already friends with this user.

Cause

Solution

Extra

Errornumber 1023

Responseheader

HTTP/1.1 400 Bad Request

Message

Unable to invite user.

Cause

Solution

Extra

Errornumber 1024

Responseheader

HTTP/1.1 400 Bad Request

Message

Unable to invite user, already invited.

Cause

Solution

Extra

Errornumber 1025

Responseheader

HTTP/1.1 400 Bad Request

Message

Unable to subscribe.

Cause

Solution

Extra

Errornumber 1026

Responseheader

HTTP/1.1 400 Bad Request

Message

Unkown buzz type given.

Cause

Solution

Extra

Errornumber 1027

Responseheader

HTTP/1.1 503 Service Unavailable

Message

Chat architecture is currently unavailable.

Cause

There is no available chat server, the Hyves Chat Service could be down.

Solution

Try again later.

Extra

Errornumber 1028

Responseheader

HTTP/1.1 400 Bad Request

Message

No rating given.

Cause

Solution

Extra

Errornumber 1029

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal rating given, 1-5 supported.

Cause

Solution

Extra

Errornumber 1030

Responseheader

HTTP/1.1 400 Bad Request

Message

No tipcategory given.

Cause

Solution

Extra

Errornumber 1031

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal searchterms given.

Cause

Solution

Extra

Errornumber 1032

Responseheader

HTTP/1.1 400 Bad Request

Message

Unkown sorttype given.

Cause

Solution

Extra

Errornumber 1033

Responseheader

HTTP/1.1 400 Bad Request

Message

Unkown timespan given.

Cause

Solution

Extra

Errornumber 1034

Responseheader

HTTP/1.1 400 Bad Request

Message

Illegal gadget url given.

Cause

Solution

Extra

Errornumber 1035

Responseheader

HTTP/1.1 400 Bad Request

Message

Gadget requires atleast one page to be added on.

Cause

Solution

Extra

Errornumber 1036

Responseheader

HTTP/1.1 400 Bad Request

Message

Number of maximum items of this type reached.

Cause

Solution

Extra

Errornumber 1037

Responseheader

HTTP/1.1 400 Bad Request

Message

Cannot target loggedin user.

Cause

Solution

Extra

Errornumber 1038

Responseheader

HTTP/1.1 400 Bad Request

Message

Unsupported visibility filter given.

Cause

Solution

Extra

Errornumber 1039

Responseheader

HTTP/1.1 400 Bad Request

Message

When using visibility friendgroup a visibility filter is required.

Cause

Solution

Extra

Errornumber 1040

Responseheader

HTTP/1.1 400 Bad Request

Message

Unknown buzz action given.

Cause

Solution

Extra

Errornumber 1041

Responseheader

HTTP/1.1 400 Bad Request

Message

Invalid parameters for rectangle

Cause

Solution

Extra

Errornumber 1042

Responseheader

HTTP/1.1 400 Bad Request

Message

Member blocked

Cause

Solution

Extra

Errornumber 1043

Responseheader

HTTP/1.1 400 Bad Request

Message

Spotted limit reached

Cause

Solution

Extra

Errornumber 1044

Responseheader

HTTP/1.1 400 Bad Request

Message

Already spotted

Cause

Solution

Extra

Errornumber 1045

Responseheader

HTTP/1.1 400 Bad Request

Message

key is incorrect. It may only contain alphanumeric (A-Za-z0-9) characters, underscore(_), dot(.) or dash(-).

Cause

Solution

Extra

Errornumber 1046

Responseheader

HTTP/1.1 400 Bad Request

Message

value should be a valid JSON encoded String.

Cause

Solution

Extra

Errornumber 1047

Responseheader

HTTP/1.1 400 Bad Request

Message

Unknown category encountered.

Cause

One of the categories in the list is invalid. The list should be a comma-delimited, without spaces list of one or more of friend and famous. Note that friend is only supported in combination with a userid

Solution

Make sure there is at least one category (the category field is optional, but when present may not be empty. Also check that the list doesn't being or end in a comma, or has a double comma.

Context Navigation

TracNav

Hyves-API Home

Specs

methods

global (ha_*) parameters

oAuth

special API zones

Errors

Errornumber 1

Responseheader

Message

Cause

Solution

Extra

Errornumber 2

Responseheader

Message

Cause

Solution

Extra

Errornumber 3

Responseheader

Message

Cause

Solution

Extra

Errornumber 4

Responseheader

Message

Cause

Solution

Extra

Errornumber 5

Responseheader

Message

Cause

Solution

Extra

Errornumber 6

Responseheader

Message

Cause

Solution

Extra

Errornumber 7

Responseheader

Message

Cause

Solution

Extra

Errornumber 8

Responseheader

Message

Cause

Solution

Extra

Errornumber 10

Responseheader

Message

Cause

Solution

Extra

Errornumber 11

Responseheader

Message

Cause

Solution

Extra

Errornumber 12

Responseheader

Message

Cause

Solution

Extra

Errornumber 13

Responseheader

Message

Cause

Solution