> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/integrations/custom-api-endpoint.md).

# Custom Endpoint

Send Brewfather batch JSON exports to your own custom HTTPS endpoint for automation.

Custom Endpoint lets you send a Brewfather **Batch JSON** export directly to your own URL.

## Enable it

1. Open **Settings → Power-ups**.
2. Enable **Custom Endpoint**.
3. Enter your endpoint URL in **Https URL to receive Batch JSON Export POST**.
4. (Optional) Enable **Send method DELETE before POST**.

## Endpoint requirements

* Use an **HTTPS** endpoint URL.
* The endpoint should support **CORS** ([Cross-Origin Resource Sharing](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)).
* Brewfather sends JSON containing full batch and recipe data.
* This is useful for custom automation (for example, an [IFTTT](https://ifttt.com/) webhook).

## Send batch JSON

After enabling Custom Endpoint, Brewfather adds send options in the batch view:

* Header button: **Send JSON**
* Export action sheet: **Send Batch JSON**

Brewfather sends the payload to your configured URL with `Content-Type: application/json`.

If **Send method DELETE before POST** is enabled, Brewfather will call `DELETE` first, then `POST`.

## Notes

* Custom Endpoint is Premium-gated in the current app flow.
* If no endpoint URL is set, Brewfather skips sending.
* Success/failure is shown in-app with toast messages.

## Related docs

* [Webhooks](/webhooks.md)
* [Node-RED](/integrations/node-red.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brewfather.app/integrations/custom-api-endpoint.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 `build a script that syncs our docs to a CMS` 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.