Connect Telegram to Slurp

Before you start

Telegram downloads use Telegram’s client API rather than a browser companion. You need an existing Telegram account and your own API ID and API hash from my.telegram.org. These are Telegram application credentials, not a bot token.

Slurp does not ship shared Telegram API credentials. Telegram’s official setup instructions are available at Creating your Telegram Application.

1. Get your Telegram API credentials

1. Sign in to my.telegram.org with the phone number linked to your Telegram account.
2. Open API development tools.
3. If Telegram asks you to create an API application, complete its application form for your own use.
4. Copy the api_id and api_hash values Telegram gives you.

Keep the API hash private. Slurp stores it in macOS Keychain.

2. Save the credentials in Slurp

1. Open Slurp → Settings → Integrations.
2. Expand Telegram.
3. Enter the numeric API ID and your API hash.
4. Choose Save.

Slurp stores the API hash in macOS Keychain. The Telegram session itself stays on this Mac in Slurp’s Application Support folder.

3. Authorize your Telegram account

1. Enter your Telegram phone number including its country code, for example +45….
2. Choose Send Code.
3. Enter the login code Telegram sends to your account.
4. Choose Connect Telegram.

If your Telegram account uses two-step verification, Slurp asks for that password after the login code. When authorization succeeds, the Telegram integration changes to Ready and shows the connected account.

4. Download Telegram media

Paste a Telegram link that points to a specific message, such as a supported t.me message link. Slurp resolves that message through the connected Telegram account and shows downloadable media when the message contains it.

Private-channel message links can work when the connected account already has access to that channel. Slurp cannot use a generic channel/profile link as a substitute for a specific message link.

What Slurp can access

Slurp can only request Telegram content that the connected account can already access. It does not bypass private-channel membership, deleted-message state, Telegram permissions, or other access controls.

Use Slurp only for media you are authorized to save and follow Telegram’s terms and the rights attached to the content.

If setup does not complete

• API ID rejected: copy only the numeric api_id from my.telegram.org. Slurp rejects values outside Telegram’s supported API-ID range.
• No login code: check the Telegram account connected to that phone number and request a new code from Slurp if needed.
• Two-step verification required: enter your Telegram two-step verification password when Slurp asks for it.
• Message unavailable: confirm that the connected account can open the exact message in Telegram and that the link points to a specific message.
• Wrong account: choose Disconnect Telegram in Slurp, then connect the account that has access to the media.

Local storage and privacy

The API hash is stored in macOS Keychain. Slurp’s Telegram session remains under ~/Library/Application Support/Slurp/Telegram. Telegram login and media requests go directly between Slurp’s Telegram integration and Telegram; Slurp does not proxy your Telegram media through a Slurp server.

You can choose Disconnect Telegram in Settings → Integrations to log Slurp’s Telegram session out. Read Slurp’s Privacy Policy for the broader product privacy model.