# AMQP integration

[AMQP](https://www.amqp.org) integrations enable you to automatically forward events that occur in Ably to AMQP-compatible brokers.

## Create an AMQP integration 

<Tabs>
<Tab value="dashboard" label="Dashboard">

On the [Integrations](https://ably.com/accounts/any/apps/any/integrations) page of your app:

1. Click **New Integration Rule**.
2. Choose **Firehose**.
3. Choose **AMQP**.
4. Configure the AMQP [settings](#settings).
5. Click **Create**.

</Tab>
<Tab value="control-api" label="Control API">

Create an AMQP rule using the Control API by sending a `POST` request to [`/apps/{app_id}/rules`](https://ably.com/docs/api/control-api.md?source=llms.txt):

<Code>

### Shell

```
curl -X POST https://control.ably.net/v1/apps/{APP_ID}/rules \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "ruleType": "amqp/external",
    "requestMode": "single",
    "source": {
      "channelFilter": "",
      "type": "channel.message"
    },
    "target": {
      "url": "amqps://username:password@broker.example.com/vhost",
      "routingKey": "my-routing-key",
      "mandatoryRoute": false,
      "persistentMessages": true,
      "format": "json",
      "enveloped": true
    }
  }'
```
</Code>

</Tab>
</Tabs>

### Settings 

The following settings are available when creating an AMQP integration:

| Setting | Description |
| ------- | ----------- |
| URL | Specifies the AMQP connection URL in the format `amqps://username:password@host.name/vhost`. |
| Headers | Allows the inclusion of additional information in key-value format. |
| [Source](https://ably.com/docs/platform/integrations/streaming.md?source=llms.txt#sources) | Specifies the event types being sent to AMQP. |
| [Channel filter](https://ably.com/docs/platform/integrations/streaming.md?source=llms.txt#filter) | Filters the source channels based on a regular expression. |
| Encoding | Specifies the encoding format of messages. Either JSON or MsgPack. |
| [Enveloped](https://ably.com/docs/platform/integrations/streaming.md?source=llms.txt#enveloped) | Checkbox to set whether messages should be enveloped or not. Enveloped is the default. |
| Routing key | Specifies the [routing key](https://ably.com/docs/messages.md?source=llms.txt#routing) used by the AMQP exchange to route messages to a physical queue. Supports interpolation. |
| Exchange | An optional RabbitMQ exchange. Supports interpolation. |
| Route mandatory | Messages are rejected if the route does not exist when set to `true`. Fails silently otherwise. |
| Route persistent | Messages are marked as persistent, instructing the broker to write them to disk if the queue is durable. |
| Optional TTL (minutes) | Override the default queue time to live (TTL), in minutes, for messages to be persisted. |

## Related Topics

- [Overview](https://ably.com/docs/platform/integrations/streaming.md?source=llms.txt): Outbound streaming integrations enable you to stream data from Ably to an external service for realtime processing.
- [Kafka](https://ably.com/docs/platform/integrations/streaming/kafka.md?source=llms.txt): Send data to Kafka based on message, channel lifecycle, channel occupancy, and presence events.
- [Kinesis](https://ably.com/docs/platform/integrations/streaming/kinesis.md?source=llms.txt): Send data to Kinesis based on message, channel lifecycle, channel occupancy, and presence events.
- [SQS](https://ably.com/docs/platform/integrations/streaming/sqs.md?source=llms.txt): Send data to SQS based on message, channel lifecycle, channel occupancy, and presence events.
- [Pulsar](https://ably.com/docs/platform/integrations/streaming/pulsar.md?source=llms.txt): Send data to Pulsar based on message, channel lifecycle, channel occupancy, and presence events.
- [DataDog](https://ably.com/docs/platform/integrations/streaming/datadog.md?source=llms.txt): Connect Ably and Datadog to monitor messages, channels, and connections in realtime, integrating your Ably statistics with your existing Datadog setup.

## Documentation Index

To discover additional Ably documentation:

1. Fetch [llms.txt](https://ably.com/llms.txt?source=llms.txt) for the canonical list of available pages.
2. Identify relevant URLs from that index.
3. Fetch target pages as needed.

Avoid using assumed or outdated documentation paths.