Error Messages
Here are some common types of errors and possible workarounds:
| Type of Error | Description | Resolution |
|---|---|---|
| Validation errors | A required parameter is missing, a value isn't supported, a value is in an invalid format, or an unexpected parameter was provided. |
Fix the invalid data and resubmit the request. Refer to the method documentation or Swagger specification to identify required parameters. |
| Resource not found errors | A resource ID you provided, such as an account ID, doesn't match anything in the database. |
Confirm your resource IDs and resubmit the request. For example, if you try to update account 1234, but accidentally enter 1235 (and no account with number 1235 exists), you get a 404 error in the response stating that the account wasn't found. Before resubmitting the request, you can use a GET request to check that 1234 was the one you intended to use instead. |
| Authentication errors | Your OAuth access token isn't correct. |
Confirm your authentication details and resubmit the request. |
| Authorization errors | You aren't authorized to make a request. |
Ask your user administrator to grant your client the missing permissions. Access to different methods on different endpoints is controlled by the scope assigned to your REST client. |
| Connection errors | A generic system or
connection error occurred. Common system errors
include:
|
Check the BRM or BI Publisher server connection and then resubmit the request. |