> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/integrations-and-automation/why-am-i-receiving-a-400-bad-request-error-with-my-autotask-integration-in-ilert.md).

# Why am I receiving a "400 Bad Request" error with my Autotask integration in ilert?

This article explains the common causes and solutions for receiving a "400 Bad Request" error when setting up or using the Autotask integration with ilert.

A "400 Bad Request" error typically occurs when ilert cannot successfully communicate with Autotask. This may happen due to incorrect user credentials or insufficient permissions for the Autotask API user.

**Solution:** Follow these steps to resolve the issue:

1. **Verify the Autotask API User:**
   * Ensure you have set up an API user in Autotask specifically for ilert integration (this must be an API user, not a regular user).
2. **Check User Credentials:**
   * Confirm the username and password combination entered for your ilert alert source matches exactly with your Autotask API user's credentials.
3. **Check User Status and Permissions:**
   * Verify that the Autotask API user is active and not locked out.
   * Ensure the user has proper API permissions to access tickets and other necessary resources in Autotask.
4. **Trigger and Review the Error:**
   * After verifying or updating your credentials, trigger the integration again.
   * Record the exact timestamp of your test trigger if errors persist and contact ilert support for further log analysis.

**Additional Notes:**

* Regularly review and confirm the API user status in Autotask, as locked accounts are a frequent cause of integration issues.
* If issues continue, reach out directly to ilert support for detailed assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/knowledge-base/integrations-and-automation/why-am-i-receiving-a-400-bad-request-error-with-my-autotask-integration-in-ilert.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.