Read the Telegram notification status
Where the creator's sale notifications currently go: their saved handle, whether a personal chat is connected, and whether a group/channel is connected.
/api/external/v1/notificationsalso served at /api/external/notificationsWhere the creator's sale notifications currently go: their saved handle, whether a personal chat is connected, and whether a group/channel is connected.
Read-only and safe. Use it before any write in this group so you never clobber an existing setup.
Authentication
Send the creator's API key as a bearer token: Authorization: Bearer dpfn_…. See Authentication & API keys.
For a creator you manage or onboarded
GET /api/external/v1/creators/{creatorId}/notifications — an agency's own key for a creator or AI persona it manages (needs canEditProfile), or your app owner's own key for an account your app onboarded. The X-Dropfans-Account header still works but is deprecated. See Acting for a creator.
Responses
| Name | Type | Description |
|---|---|---|
telegramHandle | string | null | The creator’s saved Telegram @handle (without @), or null. |
personalConnected | boolean | True when a personal chat id is registered — sale notifications DM the creator. |
groupConnected | boolean | True when a group/channel is registered for notifications. |
groupChatId | string | null | The registered group chat id (e.g. "-100…"), or null. |
groupName | string | null | The registered group’s title, or null. |
{
"telegramHandle": "valeria_tg",
"personalConnected": true,
"groupConnected": false,
"groupChatId": null,
"groupName": null
}Errors
| Status | Body | When |
|---|---|---|
| 401 | {"error":"Unauthorized","code":"unauthorized"} | Missing or invalid API key. |
| 404 | {"error":"User not found"} | The key’s account no longer exists. |
| 400 | {"error":"X-Dropfans-Account must be an account id (from GET /api/external/agency/creators), not a username.","code":"invalid_account_header"} | `X-Dropfans-Account` is not an account id. |
| 400 | {"error":"X-Dropfans-Account names a different account than the path — send one or the other.","code":"account_mismatch"} | Called under /v1/creators/{creatorId}/ with an `X-Dropfans-Account` naming another account. |
| 403 | {"error":"This key cannot act for that account.","code":"account_not_managed"} | The creator in the path (or `X-Dropfans-Account`) is one this key cannot act for: no ACCEPTED management by your agency and not an account your app onboarded (or it no longer holds a key bound to your app), a key minted for one creator, or someone is suspended, banned or deleted. An unknown id gets the same answer. |
| 403 | {"error":"The agency does not have permission for this on that account.","code":"permission_denied","permission":"canEditProfile"} | For a managed creator: the agency lacks `canEditProfile` on that account. |
| 403 | {"error":"This app does not have the notifications API category enabled. Contact support to enable it.","code":"api_category_disabled","category":"notifications"} | Your app has the Telegram notifications [API category](/developers/concepts/api-categories) switched off. |
Rate limiting
Every response carries the X-RateLimit-Tier header and, on limited tiers, the per-minute and per-day trios — read X-RateLimit-Remaining and X-RateLimit-Reset instead of hardcoding limits. Details in Rate limits.
Code samples
curl "https://www.dropfans.io/api/external/v1/notifications" \
-H "Authorization: Bearer $DROPFANS_API_KEY"const res = await fetch(`https://www.dropfans.io/api/external/v1/notifications`, {
headers: {
Authorization: `Bearer ${process.env.DROPFANS_API_KEY}`,
},
});
console.log(await res.json());import os
import requests
res = requests.get(
"https://www.dropfans.io/api/external/v1/notifications",
headers={"Authorization": f"Bearer {os.environ['DROPFANS_API_KEY']}"},
)
print(res.json())Questions? support@dropfans.io