> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/webhook/destinations-and-routing-setup/multiple-destinations-per-env.md).

# Can one environment send data to two webhooks?

The dashboard self-serves **one webhook destination per dev ID**.

The cleanest pattern for UAT vs production is **separate dev IDs, each with its own fixed destination**, configured independently. You can set a separate webhook in your [Testing environment](https://docs.tryterra.co/health-and-fitness-api/integration-setup/understanding-terra-environments) and use the Data Generator there to populate a test account.

To send the **same** user data to more than one destination (for example prod plus UAT, or two internal apps), point Terra at a **single endpoint that forwards payloads** to your internal apps, keeping one Terra webhook decoupled from your apps. See [setting up data destinations](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations).

For advanced multi-destination setups, contact support to discuss options.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/webhook/destinations-and-routing-setup/multiple-destinations-per-env.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.