End a conversation
Pay to Chat with `payScope: "PER_CONVERSATION"`: the fan pays again to chat, and their next message is asked at once. A subscriber stays in.
Questions? [email protected]
Pay to Chat with `payScope: "PER_CONVERSATION"`: the fan pays again to chat, and their next message is asked at once. A subscriber stays in.
Questions? [email protected]
/api/external/v1/chat-gate/fans/{fan}/lockalso served at /api/external/chat-gate/fans/{fan}/lockNewPay to Chat with payScope: "PER_CONVERSATION": the fan pays again to chat, and their next message is asked at once. A subscriber stays in.
Send the creator's API key as a bearer token: Authorization: Bearer dpfn_…. See Authentication & API keys.
For a creator you manage or onboarded
POST /api/external/v1/creators/{creatorId}/chat-gate/fans/{fan}/lock — an agency's own key for a creator or AI persona it manages (needs canManageDrops), 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.
| Name | Type | Required | Description |
|---|---|---|---|
fan | string | Required | Telegram user id of the fan. |
Content type: application/json
| Name | Type | Required | Description |
|---|---|---|---|
account | string | Required | Telegram user id of the creator’s account (the business connection’s user.id). |
{
"account": "5550001111"
}| Name | Type | Description |
|---|---|---|
account | string | Telegram user id. |
fan | string | Telegram user id. |
status | string | open the gate is off; team the creator, their agency or Dropfans staff; exempt on the Accept for list; subscribed / paid let in by money; opened an app opened the chat itself ([POST /chat-gate/fans/open](/developers/reference/open-chats)); locked would be asked.One of: open, team, exempt, subscribed, paid, opened, locked |
locked | boolean | Would be asked now. |
{
"account": "5550001111",
"fan": "48213377",
"status": "locked",
"locked": true
}| Status | Body | When |
|---|---|---|
| 400 | {"error":"account must be a Telegram user id (digits, as a string)","code":"invalid_telegram_id"} | `account` is missing or not a Telegram user id. |
| 400 | {"error":"fan must be a Telegram user id (digits, as a string)","code":"invalid_telegram_id"} | `fan` is missing or not a Telegram user id. |
| 409 | {"error":"Only Pay to Chat with payScope PER_CONVERSATION ends conversations.","code":"not_per_conversation"} | Any other setting on that account. |
| 401 | {"error":"Unauthorized","code":"unauthorized"} | Missing or invalid API key. |
| 403 | {"error":"This endpoint needs a key bound to an app with the chat_gate API category enabled — personal keys cannot use it.","code":"app_key_required","category":"chat_gate"} | A personal key: the chat gate answers back through app webhooks. |
| 409 | {"error":"The chat gate is for creator accounts.","code":"not_a_creator"} | The account is a fan account, suspended or banned. |
| 503 | {"error":"The chat gate is not available right now. Let the message through.","code":"unavailable"} | Something failed on our side. Fail open: let the message stand. |
| 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":"canManageDrops"} | For a managed creator: the agency lacks `canManageDrops` on that account. |
| 403 | {"error":"This app does not have the chat_gate API category enabled. Contact support to enable it.","code":"api_category_disabled","category":"chat_gate"} | Your app has the Pay to Chat [API category](/developers/concepts/api-categories) switched off (the default for new apps). |
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.
curl -X POST "https://www.dropfans.io/api/external/v1/chat-gate/fans/$FAN/lock" \
-H "Authorization: Bearer $DROPFANS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"account": "5550001111"
}'const fan = '…'; // from an earlier response
const res = await fetch(`https://www.dropfans.io/api/external/v1/chat-gate/fans/${fan}/lock`, {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.DROPFANS_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"account": "5550001111"
}),
});
console.log(await res.json());import os
import requests
fan = "…" # from an earlier response
res = requests.post(
f"https://www.dropfans.io/api/external/v1/chat-gate/fans/{fan}/lock",
headers={"Authorization": f"Bearer {os.environ['DROPFANS_API_KEY']}"},
json={
"account": "5550001111",
},
)
print(res.json())