> For the complete documentation index, see [llms.txt](https://help.starkbank.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.starkbank.com/integracao-e-apis/como-criar-um-webhook-pelo-internet-banking.md).

# Como criar um Webhook pelo Internet Banking?

Saiba como configurar webhooks para acompanhar sua integração no Stark Bank.

Os Webhooks transitam dados entre ferramentas em tempo real, utilizando para isso uma URL de destino para a entrega de eventos. Você pode criar assinaturas de Webhook para receber eventos sempre que um novo log de transação for criado.

#### Para criar pelo Internet Banking:

1. Acesse sua conta Stark Bank em <https://web.starkbank.com/signin>
2. No menu superior, clique em Integrações;
3. Em seguida, clique em Webhooks e em Novo Webhook;
4. Na janela que será aberta, insira a URL que você já gerou e selecione as assinaturas dos produtos que deseja receber eventos nessa URL. Caso queira receber eventos de cada produto em uma URL diferente, será necessário repetir esse processo para cada URL e seu respectivo produto;
5. Para finalizar a criação do Webhook, clique em Criar.

{% content-ref url="/pages/L59kVVykBcyvlIjHWsrE" %}
[Como utilizar Webhooks no Stark Bank?](/integracao-e-apis/como-utilizar-webhooks-no-stark-bank.md)
{% endcontent-ref %}


---

# 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://help.starkbank.com/integracao-e-apis/como-criar-um-webhook-pelo-internet-banking.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.