Last modified
On this page
Overview
This page lists the response messages that you may get when making calls to the OAuth dynamic client registration API.
Response messages
| HTTP status | Error name | Error description |
| 400 | Invalid_request | The {attribute} field is required |
| 400 | Invalid_request | {attribute} is read-only |
| 400 | Invalid_request | {attribute} is not valid or expired |
| 400 | Invalid_request | {attribute} is expired |
| 400 | Invalid_request | {attribute} must contain a jwks_uri OR x509_certificate |
| 400 | Invalid_request | More than one {attribute} provided |
| 400 | Invalid_request | Selected grant_type cannot be used with {attribute} value |
| 400 | Invalid_request | Selected grant_type requires valid {attribute} value |
| 400 | Invalid_request | invalid client id for {attribute} |
| 400 | Invalid_request | {attribute} cannot be TRUE when {attribute} = "NULL" |
| 400 | Invalid_request | More than one {attribute} provided |
| 400 | Invalid_redirect_uri | Selected grant_type cannot be used with {attribute} value |
| 400 | Invalid_redirect_uri | {attribute} contains invalid {attribute} |
| 400 | Invalid_redirect_uri | The {attribute} field is required with selected grant_type |
| 400 | Invalid_client_metadata | {attribute} is invalid |
| 400 | Invalid_client_metadata | {attribute} exceeded characters limit |
| 400 | Invalid_client_metadata | Format for {attribute} is not supported |
| 400 | Invalid_client_metadata | {attribute} has exceed number the number of {attribute} |
| 400 | Invalid_client_metadata | More than 5 {attribute} provided |
| 400 | Invalid_client_metadata | {attribute} is not supported |
| 400 | DCR.00001 | ato_api_key is not the same as the apiKey in the header. |
| 401 | Invalid_token | Unauthorised |
| 403 | Insufficient_scope | The scope provided is invalid for this operation |
Go back to OAuth dynamic client registration API