n8n · HTTP Request node
Bad request - please check your parameters
Short answer
This n8n HTTP Request error displays when the node receives a 400 error indicating a bad request. Review the API documentation for your service to format your query parameters.
VerifiedLast verified
01Error text
Bad request - please check your parameters02Likely causes
- You're using an invalid name or value in a Query Parameter.
- You're passing array values in a Query Parameter but the array isn't formatted correctly.
03How to fix it
- Review the API documentation for your service to format your query parameters.
- For array values, try the Array Format in Query Parameters option.
04Official documentation
→Related errors
- The resource you are requesting could not be foundThis n8n HTTP Request error displays when the endpoint URL you entered is invalid. Refer to your service's API documentation to verify you have a valid endpoint.
- Connection refused (ECONNREFUSED)ECONNREFUSED in the n8n HTTP Request node means the node reached a host but the target port has no listener, most often because of Docker networking on self-hosted n8n. Address the target by a name the container can route to, such as host.docker.internal or the Compose service name.
- JSON parameter need to be an valid JSONThis n8n HTTP Request error displays when you pass a parameter as JSON and it is not formatted as valid JSON. Test your JSON in a JSON checker or syntax parser to find errors.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for n8n work:Open n8n jobsn8n rates and salaries