Table of Contents
Any Elance Developer API Version 2 method can return the following general errors. The errors are arranged by the value of the type property used to describe them in an error response. For a description of the format of an Elance Developer API Version 2 error response, see JSON Response Format and Error Codes.
I. API Error Codes
The following errors are turned with an error type value of api.
Differences from Version 1:
- The API Version 1 error code E_API_HTTPS_REQUIRED has been removed, as all methods in Version 2 of the API require SSL. If a valid API method is called using the HTTP method instead of HTTPS, Elance.com will respond with a 301 Moved Permanently HTTP response containing a secure (HTTPS) link to the method.
- The E_API_INVALID_VERSION and E_API_VERSION_DEPRECATED error codes have been removed, as the v parameter for specifying an API version is ignored by Version 2.
- The E_API_INVALID_FORMAT error has been removed, as the fmt parameter for specifying an API version is ignored by Version 2.
|E_API_SERVICE_TEMPORARILY_UNAVAILABLE||The Elance Developer API service is temporarily offline, and will return momentarily. Issued as part of an HTTP 503 error response. Applications that receive this error should wait 30 seconds or longer before attempting the request again.|
|E_API_INVALID_HTTP_METHOD||The API was called with the wrong HTTP method (GET, POST, or HEAD). Please check the method documentation for the correct HTTP method.|
II. Authentication Error Codes
The following errors are turned with an error type value of authentication.
Differences from Version 1: The error codes in this section have been changed extensively to reflect the use of OAuth 2.0 in Version 2.
|E_API_AUTH_EXPIRED_ACCOUNT||The user account associated with the API key has expired. Please contact customer support for assistance.|
|no_token||The client access token, specified using the access_token query string parameter, is absent from the request.|
|invalid_token||The client application's Access Token has expired.|
|E_API_REQUEST_ALREADY_RECEIVED||The signature, timestamp, and nonce of the request match those of a request that was already processed.|
III. Validation Error Codes
The following general errors are returned because one or the parameters submitted in the request was incorrect or malformed. Validation errors are categorized with a type value of validation in an API error response.
Differences from Version 1: The E_VALIDATION_NOT_POSITIVE_INT, E_VALIDATION_NOT_POSITIVE_NUM, and E_VALIDATION_NOT_NUMBER error codes are not returned by Version 2 methods. In many cases where these codes were formally used, the E_API_VALIDATION_PARAM_REQUIRED error code is returned instead.
|E_API_VALIDATION_PARAM_REQUIRED||The named parameter is required.|
|E_VALIDATION_INVALID_ID||The numeric ID for the named parameter is not valid.|
|E_API_NOT_AUTHORIZED||Either the currently logged on user is not permitted to access this feature, or a user specified in a query string parameter does not have access to the underlying object (for example, a Workroom or a job posting).|
IV. Miscellaneous API Error Codes
The following errors are returned with an error type value of misc.
|E_API_INTERNAL_ERROR||A fatal internal error has occurred. Please contact Elance customer support.|
|E_API_NOT_AUTHORIZED||The client is not authorized to access this API.|