Common HTML Response Codes
|200||OK||The request succeeded.|
|201||Created||The request succeeded and resulted in the creation of new resources.|
|204||No Content||The server fulfilled the request and does not need to return an entity-body.|
|400||Bad Request||The request could not be understood due to malformed syntax.|
|401||Unauthorized||The request requires user authentication.|
|403||Forbidden||The server understood the request, but is refusing to fulfill it.|
|404||Not Found||The server has not found anything matching the Request-URI|
|409||Conflict||The request could not be completed due to a conflict with the current state of the resource.|
Authorization and Authentication Errors
Below are examples of error codes raised when an authorization request fails.
Verify client_id matches exactly to the one specified in client registration. Verify client_secret matches exactly to the one specified in client registration. client_secret is only necessary when exchanging an authorization code access token.
Verify both client_id and client_secret are present in the parameters.
Verify grant_type is not missing or empty . It must be specified for every call to token endpoint.
Verify redirect_uri is not empty or missing.
Verify redirect_uri matches exactly to the one specified during client registration.
Validate the format of your query parameters. For example, make sure redirect_uri is in correct format.