Groove RESTful API HTTP Status Codes

The Hypertext Transfer Protocol (HTTP) standard describes a number of status codes that are returned by the server in response to a client request. Groove API methods return HTTP protocol-compliant status codes to describe the status of the request.

The table provides a list of status codes returned by Groove API, and their typical meanings.

CodeReason phraseDescription
200OKThe request was successful.
400Bad RequestThe URL or input parameters are incorrect.
401UnauthorizedThe request requires user authentication.
403ForbiddenThe request is not allowed for the user or service.
404Not FoundThe specified resource could not be found.
406Not AcceptableResource version is not supported.
408Request TimeoutThe request took too long to complete.
409ConflictThe request was not completed due to a conflict with the current state of the resource.
410GoneThe requested resource is no longer available.
412Precondition FailedThe server does not meet one of the preconditions that the requester put on the request.
416Requested Range Not SatisfiableThe requested range is not available.
429Too Many Requests The caller has exceeded the service throttling limit and needs to wait before sending another request.
500Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
501Not ImplementedThe server does not support the functionality required to fulfill the request.
502Bad GatewayA backend dependency is unavailable or returning errors.
503Service UnavailableThe server is refusing the request due to excessive load.

Some resources and methods provide specific information about the meaning of particular status codes in the context of that resource or method. For more details, refer to the documentation for the resources or methods that you are using.