GetGo API HTTP Status Codes
This page provides GetGo API status code explanations. For a general overview, or if you encounter codes not documented here, see the WWW3 organization’s Hypertext Transfer Protocol.
|200 OK||Confirms successful receipt of GET calls.|
|201 Created||Confirms successful POST calls.|
|204 No Content||Confirms DELETE or PUT calls.|
IMPORTANT: The error codes you receive can depend on the data and data formats included in the call. For instance, the key values such as organizerKey, webinarKey, etc., are all numeric. Passing an incorrect key value may return different error messages than if you include alphabetic characters or non-numeric characters.
|400 Bad Request||The request is invalid. This can be caused by an incorrect argument such as "time" instead of "times” or may be caused by trying to book sessions that overlap in time, dates beyond one year, and if the calls fail to find the requested data.|
|401 Unauthorized||This response alerts you that there is a problem with your account. The account_token could be incomplete or incorrect, your account could be expired, or the authorization token (oauth_token) may be invalid.|
|403 Forbidden||The user making this call is not authorized to make the call.
|404 Not Found||Occurs when an incorrect key value, a non-existent or deleted data key, or a key for an event in the past is passed.|
|405 Invalid Method||Can occur if your calls pass through an ISP that does not allow POST methods. If this error arises, contact your ISP.|
|409 Conflict||This occurs if you attempt to create a duplicate of a unique resource.|
|422 Unprocessable Entity||The request was formed correctly but was unable to be followed due to semantic errors.|
|429 Too Many Requests||The broker returns this code if, for a given user account, too many requests are received in a specific time frame. Calls can be tried again later.|
|500 InternalError||There is an internal server error. This could be caused by a failed or partial connection, or other transitory conditions. The request may be retried, but it may have the same result.|
|502 Bad Gateway||The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. Simplify the data request and ensure post requests are within available periods.|
|502 Illegal Account||Accounts without billing IDs for which tollFreeProvisioned is true. This is a hard error on the account. Contact firstname.lastname@example.org to clear the error and reset your account.|
|504 Gateway Timeout||The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.|