# Callbacks in Beacon

Many a times, command executions may not be as simple as a click action or a link redirection, you may want to hit an API or execute a custom function/callback instead. To handle these scenarios, beacon offers Callback option to write your own logic for the command executions.

{% content-ref url="/pages/pWortmLaBHsQRd2zAjht" %}
[Add Callbacks in Beacon](/callbacks-in-beacon/add-callbacks-in-beacon.md)
{% endcontent-ref %}

{% content-ref url="/pages/a9vN7TyfnuUqLHF8Hk6Q" %}
[Remove Callbacks in Beacon](/callbacks-in-beacon/remove-callbacks-in-beacon.md)
{% endcontent-ref %}

{% content-ref url="/pages/zxMHsSTaXBSCZx0UfVcL" %}
[React Example for Callbacks](/callbacks-in-beacon/react-example-for-callbacks.md)
{% endcontent-ref %}


---

# Agent Instructions: 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://api.beacon.li/callbacks-in-beacon.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.