> 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/no-api-to-manage-destinations.md).

# Is there an API to manage webhook destinations?

There is no public API to manage [webhook destinations](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations/webhooks); the dashboard endpoints are internal and session-authenticated.

For a deploy pipeline, use one of these instead:

* **Use separate dev IDs per environment**, each with its own fixed webhook destination.
* **Point Terra at a stable webhook URL**, for example a fixed subdomain that your reverse proxy routes to the active instance, so the destination never needs to change between deploys.


---

# 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/no-api-to-manage-destinations.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.