Why did my API request fail?
An API request step fails if the request can't be built, the sign-in fails, or the other system responds with anything other than a 2xx status.
Errors appear on the process's Test tab, in the step details on the History tab (click a red step badge), and on the dashboard (hover over the ! pill). In the messages below, … stands for a name, address or value from your own set-up.
The other system said no
API request … failed with status code 400. means the request was sent but the other system didn't accept it. The status tells you why:
- 400: the body or address wasn't accepted. Preview the request on the Test tab and compare it with what the API expects.
- 401 or 403: sign-in refused. AutomatedOn retries once with a fresh sign-in on a 401. Use Test Connection on the API Request.
- 404: the address doesn't exist, often a token in the endpoint with the wrong value.
- 409: the record may already exist or be in the wrong state.
- 500 or above: the other system had a problem.
The request wasn't sent
| Message | What to do |
|---|---|
Unresolved parameter(s) … in API request '…' (…). The request was not sent. | A token has no value. See What does "One or more aoParams were not provided." mean? |
Request body is not valid JSON, so body field expressions could not be evaluated. … | The body contains a condition but isn't valid JSON. Check quotes, commas and brackets. |
A body field expression failed to evaluate. … | A condition is incomplete, for example a ? without a :, or an unclosed quote. The message includes the expression. |
requestType is not configured (raw value: …). | Choose a Request Type. |
apiEndpoint is not configured on the content node. | Fill in API Endpoint. |
Content item … must have an API auth profile selected. | Pick an API Auth Profile. |
API request … not found. | The API Request picked on the step has been deleted. Pick another. |
Sign-in (API Auth Profile) messages
You'll see these in run history or when you click Test Connection.
| Message | What to do |
|---|---|
API credential '…' must define ClientId and ClientSecret. | The client credentials for that key aren't stored yet. Contact Three 17 support. |
API credential '…' must define Token. or No credential configured for key '…'. | The token or API key for that key isn't stored. Check the profile's Credential Key, then contact Three 17 support. |
Token request failed with status …. | The token endpoint refused the sign-in. Check Token Endpoint and Scope on the profile; if they're right, the stored credentials may be wrong or expired. |
API auth profile token endpoint is required for client credentials auth. | Fill in Token Endpoint on the profile. |
API auth profile '…' must define auth mode. | Choose an Auth Mode on the profile. |
No API Auth Profile selected. | Pick a profile before clicking Test Connection. |