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.
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
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
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
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.
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/
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: http://www.hyves-developers.nl/documentation/data-api/content-encoding/.
extra
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@hyves.nl.
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
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
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
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
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.
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)
Errornumber 16
responseheader
HTTP/1.1 401 Unauthorized
message
OAuth timestamp is invalid.
cause
The oauth_timestamp variable is invalid. For more information, see oauth_timestamp parameter.
solution
Supply a correct value for oauth_timestamp.
extra
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
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@hyves.nl.
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.
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
Errornumber 22
description
Errornumber 23
description
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 oauth_nonce parameter.
solution
Either change the oauth_timestamp or the oauth_nonce and try again.
extra
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 auth.accesstoken).
solution
Obtain a new token.
extra
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 50, and should conform to the following Regular Expression: /^[A-Za-z0-9_\[\]\"'\.]*$/ .
solution
Provide a correct ha_callback
extra
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
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
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
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
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
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
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.
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 500
solution
Results per page are limited, try a lower results per page.
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.
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.
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.
Errornumber 38
responseheader
HTTP/1.1 401 Unauthorized
message
Partner is inactive.
cause
The Api Partner is inactive.
solution
Contact us for more information.
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.
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/
Errornumber 41
description
Errornumber 42
description
Errornumber 43
description
Errornumber 44
responseheader
HTTP/1.1 401 Unauthorized
message
Owner of this api consumer is not registered as OpenSocial developer
Errornumber 45
responseheader
HTTP/1.1 400 Bad Request
message
The HTTP protocol used is invalid for this method.
Errornumber 46
responseheader
HTTP/1.1 400 Bad Request
message
Invalid language given.
Errornumber 47
responseheader
HTTP/1.1 400 Bad Request
message
This version of OAuth requires oauth_callback and/or oauth_callback_confirmed parameter
Errornumber 48
responseheader
HTTP/1.1 400 Bad Request
message
This version of OAuth requires oauth_callback to be a valid URL
Errornumber 49
responseheader
HTTP/1.1 400 Bad Request
message
The HTTP method used is invalid for this API method
Errornumber 50
responseheader
HTTP/1.1 401 Unauthorized
message
The consumer used is expired for this session.
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
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
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.
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
Errornumber 104
responseheader
HTTP/1.1 401 Unauthorized
message
Item not writeable for current OAuth token.
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.
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.
Errornumber 112
responseheader
HTTP/1.1 400 Bad Request
message
Invalid hyves type given.
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.
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.
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
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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)
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.
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.
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.
Errornumber 1017
responseheader
HTTP/1.1 400 Bad Request
message
Illegal geolocation (latitude / longitude).
Errornumber 1018
responseheader
HTTP/1.1 400 Bad Request
message
No bluetoothuid given.
Errornumber 1019
responseheader
HTTP/1.1 400 Bad Request
message
Illegal bluetoothuid.
Errornumber 1020
responseheader
HTTP/1.1 400 Bad Request
message
Illegal radius(meters) given.
Errornumber 1021
responseheader
HTTP/1.1 400 Bad Request
message
Unknown printability given.
Errornumber 1022
responseheader
HTTP/1.1 400 Bad Request
message
Already friends with this user.
Errornumber 1023
responseheader
HTTP/1.1 400 Bad Request
message
Unable to invite user.
Errornumber 1024
responseheader
HTTP/1.1 400 Bad Request
message
Unable to invite user, already invited.
Errornumber 1025
responseheader
HTTP/1.1 400 Bad Request
message
Unable to subscribe.
Errornumber 1026
responseheader
HTTP/1.1 400 Bad Request
message
Unkown buzz type given.
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.
Errornumber 1028
responseheader
HTTP/1.1 400 Bad Request
message
No rating given.
Errornumber 1029
responseheader
HTTP/1.1 400 Bad Request
message
Illegal rating given, 1-5 supported.
Errornumber 1030
responseheader
HTTP/1.1 400 Bad Request
message
No tipcategory given.
Errornumber 1031
responseheader
HTTP/1.1 400 Bad Request
message
Illegal searchterms given.
Errornumber 1032
responseheader
HTTP/1.1 400 Bad Request
message
Unkown sorttype given.
Errornumber 1033
responseheader
HTTP/1.1 400 Bad Request
message
Unkown timespan given.
Errornumber 1034
responseheader
HTTP/1.1 400 Bad Request
message
Illegal gadget url given.
Errornumber 1035
responseheader
HTTP/1.1 400 Bad Request
message
Gadget requires atleast one page to be added on.
Errornumber 1036
responseheader
HTTP/1.1 400 Bad Request
message
Number of maximum items of this type reached.
Errornumber 1037
responseheader
HTTP/1.1 400 Bad Request
message
Cannot target loggedin user.
Errornumber 1038
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported visibility filter given.
Errornumber 1039
responseheader
HTTP/1.1 400 Bad Request
message
When using visibility friendgroup a visibility filter is required.
Errornumber 1040
responseheader
HTTP/1.1 400 Bad Request
message
Unknown buzz action given.
Errornumber 1041
responseheader
HTTP/1.1 400 Bad Request
message
Invalid parameters for rectangle
Errornumber 1042
responseheader
HTTP/1.1 400 Bad Request
message
Member blocked
Errornumber 1043
responseheader
HTTP/1.1 400 Bad Request
message
Spotted limit reached
Errornumber 1044
responseheader
HTTP/1.1 400 Bad Request
message
Already spotted
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(-).
Errornumber 1046
responseheader
HTTP/1.1 400 Bad Request
message
value should be a valid JSON encoded String.
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.
Errornumber 1048
responseheader
HTTP/1.1 401 Unauthorized
message
Invalid userpassword given.
Errornumber 1049
responseheader
HTTP/1.1 400 Bad Request
message
Edit rate limit reached.
Errornumber 1050
responseheader
HTTP/1.1 400 Bad Request
message
Invalid URL provided
cause
The provided URL is invalid or malformed according to method input requirements
solution
Make sure the URL is welformed according to method input requirements
Errornumber 1051
responseheader
HTTP/1.1 400 Bad Request
message
No tryvertising found on consumer id
Errornumber 1052
responseheader
HTTP/1.1 400 Bad Request
message
member linked to tryvert. doesn't have email
Errornumber 1053
responseheader
HTTP/1.1 400 Bad Request
message
member linked to tryvert. doesn't have all required info
Errornumber 1054
responseheader
HTTP/1.1 400 Bad Request
message
No member found on tryvert.
Errornumber 1055
responseheader
HTTP/1.1 400 Bad Request
message
You cant call this method anymore, please contact hyves
Errornumber 1056
responseheader
HTTP/1.1 400 Bad Request
message
You have already voted for this poll
Errornumber 1057
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported filter found
Errornumber 1058
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported fancy layout format
Errornumber 2000
responseheader
HTTP/1.1 400 Bad Request
message
OpenId version not supported.
Errornumber 2001
responseheader
HTTP/1.1 400 Bad Request
message
OpenId mode not supported.
Errornumber 2002
responseheader
HTTP/1.1 400 Bad Request
message
OpenId extension or extension version not supported.
Errornumber 2003
responseheader
HTTP/1.1 400 Bad Request
message
OpenId extension invalid parameter.
Errornumber 2004
responseheader
HTTP/1.1 400 Bad Request
message
OpenId invalid parameter.
Errornumber 2005
responseheader
HTTP/1.1 400 Bad Request
message
Couldn't create result, invalid characters found.
Errornumber 2006
responseheader
HTTP/1.1 503 Service Unavailable
message
OpenID temporary unavailable.
Errornumber 2010
responseheader
HTTP/1.1 400 Bad Request
message
Identity-select is required at this moment.
Errornumber 2011
responseheader
HTTP/1.1 400 Bad Request
message
A realm or return_to parameter is required.
Errornumber 2012
responseheader
HTTP/1.1 400 Bad Request
message
return_to has an illegal format.
Errornumber 2013
responseheader
HTTP/1.1 400 Bad Request
message
realm has an illegal format.
Errornumber 2014
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported association type.
Errornumber 2015
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported association session type.
Errornumber 2016
responseheader
HTTP/1.1 400 Bad Request
message
Invalid association handle.
Errornumber 2017
responseheader
HTTP/1.1 400 Bad Request
message
Expired association handle.
Errornumber 2018
responseheader
HTTP/1.1 400 Bad Request
message
Untrusted return_to.
Errornumber 2019
responseheader
HTTP/1.1 400 Bad Request
message
The session has expired, please try again.
Errornumber 3010
responseheader
HTTP/1.1 400 Bad Request
message
The consumer key provided is invalid.
Errornumber 3011
responseheader
HTTP/1.1 400 Bad Request
message
The consumer key is not allowed from used domain.
Errornumber 1059
responseheader
HTTP/1.1 400 Bad Request
message
Unknown RSVP status given
Errornumber 1060
responseheader
HTTP/1.1 400 Bad Request
message
Event name must be given
Errornumber 1061
responseheader
HTTP/1.1 400 Bad Request
message
Event location must be given
Errornumber 1062
responseheader
HTTP/1.1 400 Bad Request
message
Event start date/time must be given
Errornumber 1063
responseheader
HTTP/1.1 400 Bad Request
message
Event visibility must be given
Errornumber 1064
responseheader
HTTP/1.1 400 Bad Request
message
Event date from is invalid
Errornumber 1065
responseheader
HTTP/1.1 400 Bad Request
message
Event date to is invalid
Errornumber 1066
responseheader
HTTP/1.1 400 Bad Request
message
Event date from is after date to
Errornumber 1067
responseheader
HTTP/1.1 400 Bad Request
message
Public events must have category
Errornumber 1068
responseheader
HTTP/1.1 400 Bad Request
message
Event - invalid content
Errornumber 1069
responseheader
HTTP/1.1 400 Bad Request
message
Event invite - Member not a friend, you cannot invite them
Errornumber 1070
responseheader
HTTP/1.1 400 Bad Request
message
Invite failed, member already responded to event
Errornumber 1073
responseheader
HTTP/1.1 400 Bad Request
message
Only the event organizer/moderator can invite friends
Errornumber 1074
responseheader
HTTP/1.1 200 OK
message
Member successfully invited
Errornumber 1075
responseheader
HTTP/1.1 400 Bad Request
message
Error retrieving information from url (must be reachable and not redirecting)
Errornumber 1076
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported nickname
Errornumber 1077
responseheader
HTTP/1.1 400 Bad Request
message
Unsupported target
Errornumber 1078
responseheader
HTTP/1.1 400 Bad Request
message
Unable to unsubscribe.