> 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/developer-docs/readme.md).

# Developer Documentation

Developer documentation for ilert - API references, SDK guides, webhooks,  integration tutorials, and technical implementation guides.

Welcome to ilert's developer documentation. This space contains technical resources for developers, DevOps engineers, and SREs who want to integrate with ilert programmatically or build custom solutions.

## <i class="fa-books">:books:</i> What's Inside

* [REST API Reference](/developer-docs/rest-api/api-reference.md) - Complete API documentation with examples
* [Client Libraries](/developer-docs/client-libraries/client-libraries.md) - Official SDKs for Go, JavaScript, Rust, and more
* [Webhook Integration](/integrations/outbound-integrations/webhook.md) - Set up webhooks for real-time event notifications
* [OAuth2 Apps](/developer-docs/developing-ilert-apps/developing-ilert-apps.md) - Build custom applications with ilert
* [ilagent CLI](/developer-docs/client-libraries/ilagent.md) - Command-line tool for local development and testing
* [ilert MCP server](https://github.com/iLert/mcp-ilert) – Enable AI assistants and MCP-compatible clients to interact with your ilert account using natural language
* [Terraform Provider](/developer-docs/terraform/terraform.md) - Infrastructure as code with ilert


---

# 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/developer-docs/readme.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.