> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/advanced-features/integrations/build-your-own.md).

# Build your own

Build custom integrations with Missive's API and webhooks.

Build custom integrations using Missive's API, webhooks, and iFrame framework. Connect internal systems, automate processes, or surface business data directly inside Missive.

{% hint style="info" %}
Full developer documentation: [docs.missiveapp.com](https://missiveapp.com/docs/developers/)
{% endhint %}

## REST API

Interact with conversations, messages, contacts, labels, and more. Push or pull data between Missive and your systems.

[API documentation](/docs/developers/rest-api.md)

## Webhooks

React to events in real time - new messages, assignments, comments, or status changes. Keep external tools synchronized with inbox activity.

[Webhooks documentation](/docs/developers/webhooks.md)

## UI/iFrame integrations

Embed custom interfaces directly inside Missive. Display dashboards, CRM records, or custom action panels next to conversations.

[UI/iFrame documentation](/docs/developers/ui-iframe-integrations.md)

{% hint style="info" %}
Need help building a custom integration? Check the [Missive Partners directory](https://missiveapp.com/partners) for developers who specialize in building integrations.
{% endhint %}


---

# 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://missiveapp.com/docs/advanced-features/integrations/build-your-own.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.