> For the complete documentation index, see [llms.txt](https://suby.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suby.gitbook.io/documentation/platform-integration.md).

# Platform Integration

- [API](https://suby.gitbook.io/documentation/platform-integration/api.md): This API is event-driven and designed to let you react to payments and subscription events, not to manage billing logic or products directly.  Below is a clear overview of what is currently possible.
- [Generated My API Key](https://suby.gitbook.io/documentation/platform-integration/api/generated-my-api-key.md): This guide explains how to integrate your paid product with our Webhook-based API to accept payments and handle subscription events in your SaaS, web app, or website.
- [Paylinks (for freelancers or agencies)](https://suby.gitbook.io/documentation/platform-integration/paylinks-for-freelancers-or-agencies.md): This guide explains how freelancers and agencies can use Paylinks to accept payments and manage subscriptions for clients, without building a full payment flow.
- [Discord](https://suby.gitbook.io/documentation/platform-integration/discord.md): This guide explains how to use Suby to accept payments and manage paid access for Discord servers, without building a custom checkout or payment flow.
- [Discord Integration](https://suby.gitbook.io/documentation/platform-integration/discord/discord-integration.md): This guide explains how to use Paylinks to accept payments and manage subscriptions for Discord servers, without building a custom checkout or payment flow.
- [Notifications Set up](https://suby.gitbook.io/documentation/platform-integration/discord/notifications-set-up.md)
- [Discord Bot Commands](https://suby.gitbook.io/documentation/platform-integration/discord/discord-bot-commands.md)
- [Typical Errors](https://suby.gitbook.io/documentation/platform-integration/discord/typical-errors.md)
- [How To Give Discord Permissions](https://suby.gitbook.io/documentation/platform-integration/discord/how-to-give-discord-permissions.md)
- [Migrate: Payments Bot -> Suby](https://suby.gitbook.io/documentation/platform-integration/discord/migrate-payments-bot-greater-than-suby.md): Follow this guide to migrate your members and subscriptions from Payments Bot to Suby. Estimated time: 2 min.
- [Migrate: IsoSubs -> Suby](https://suby.gitbook.io/documentation/platform-integration/discord/migrate-isosubs-greater-than-suby.md): Follow this guide to migrate your members and subscriptions from IsoSubs to Suby. Estimated time: 2 min.
- [Telegram](https://suby.gitbook.io/documentation/platform-integration/telegram.md): This guide explains how to use Suby to accept payments and manage paid access for Telegram groups or channels, without building a custom checkout or payment flow.
- [Telegram Integration](https://suby.gitbook.io/documentation/platform-integration/telegram/telegram-integration.md): This guide explains how to use Paylinks to accept payments and manage subscriptions for Telegram groups and channels, without building a custom checkout or payment flow.
- [Optional: Public Portal](https://suby.gitbook.io/documentation/platform-integration/telegram/optional-public-portal.md): You can optionally create a public portal that serves as a single entry point for all your paid accesses. This portal acts as a display page inside Telegram, allowing users to discover and access your


---

# 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://suby.gitbook.io/documentation/platform-integration.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.