Broadcast one drop to many fans
Send the same drop to many fans with one checkout link each, and match every payment back to the fan who paid.
Questions? [email protected]
Send the same drop to many fans with one checkout link each, and match every payment back to the fan who paid.
Questions? [email protected]
One drop can be sold to any number of fans. Give each fan a personal checkout link that carries a reference of your choice, such as your id for the fan or the conversation. When the fan pays, the order comes back with that reference, so you know who paid and where to deliver the content.
One drop has one price. If fans should pay different amounts, create one drop per price.
curl -X POST "https://www.dropfans.io/api/external/v1/drops" \
-H "Authorization: Bearer $DROPFANS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Friday set","price":25,"vaultItemIds":["clxv1a2b30001item","clxv1a2b30002item"]}'Keep the productId.
Pick a reference per recipient: your own id for the conversation, 1–32 characters of A-Z a-z 0-9 _ -. On the web it goes in the short m parameter; in Telegram it follows the product id. Fill it into the templates from GET /links:
| Where | Link |
|---|---|
| Web | https://www.dropfans.io/buy/{productId}?m={externalRef} |
| Telegram Mini App | https://t.me/<bot>/app?startapp=b_{productId}_{externalRef} |
Telegram limits the whole start parameter to 64 characters, so with a 25-character product id the 32-character reference always fits. The reference survives the whole checkout: card, saved card, 3-D Secure and wallet credits.
Each paid order carries the reference as externalRef:
drop.paid. data.externalRef tells you which fan paid. Use data.orderId as your idempotency key.?productId=…&since=… sweeps a whole broadcast.// drop.paid handler (after verifying the signature)
const { orderId, externalRef, productId, buyer } = event.data;
if (await alreadyDelivered(orderId)) return;
const chat = await findConversationByRef(externalRef); // your lookup
await deliverMedia(chat, productId);
await markDelivered(orderId);buyer.telegramUserId (set when they paid inside Telegram) with the chat you expect.drop.refunded with the same orderId and externalRef.Send each fan a tip link with your reference and match the tip when it is paid. Fill the tipWithRefTemplate from GET /links:
| Where | Link |
|---|---|
| Web | https://www.dropfans.io/u/{username}?tip={usd}&m={externalRef} ({usd} = 1 lets the fan pick) |
| Telegram Mini App | https://t.me/<bot>/app?startapp=tm_{cents}_{externalRef}_{username} ({cents} = 0 lets the fan pick) |
In the Telegram link the reference comes before the username, which may contain underscores, so there it is 1–20 characters of A-Z a-z 0-9 - with no underscore. The paid tip arrives as tip.paid (with the fan's message), or poll GET /api/external/v1/tips?externalRef=…. Refunds arrive as tip.refunded.
Next: Webhooks & polling or Creator sign-up from your platform.