> For the complete documentation index, see [llms.txt](https://docs.graspil.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graspil.com/en/connect-bot/upload.md).

# Connecting outbound data

Outbound data refers to all requests the bot sends to the user. Connecting the processing of this data gives you access to new reports and lets you see the full conversation history between the user and the bot (on the relevant plans).

## How do I connect it?

Similar to connecting inbound traffic, there are 2 ways to connect.

1. [Proxying](#proksirovanie)
2. [API](#api)

## Proxying

#### If the bot runs via Webhook

You'll need to add a bit of code. You need to change the URL from <https://api.telegram.org> to the address our system provides you. The platform will proxy absolutely all requests to Telegram's servers.

Most libraries used to build bots allow you to change this address. We have instructions for connecting getUpdates bots, and they're similar for connecting outbound traffic for webhook bots. The only difference is that you don't need to send getUpdates-type requests. You'll find all the instructions for specific libraries in [this section](/en/connect-bot/get-update.md).

If your library isn't on our list or you run into trouble connecting, please contact support.

#### If the bot runs via getUpdates

If you've connected your bot (inbound traffic) to graspil, you don't need to do anything else. All proxied requests will be processed.

{% hint style="info" %}
If you only send **getUpdates** requests through our servers and exclude all other requests, outbound data won't be processed.
{% endhint %}

## API

The method for sending data via API isn't ready yet. We'll add it soon.

You'll need to take the request and response from the Telegram API and forward them to graspil.