Check which drops sold (batch)
API reference

Check which drops sold (batch)

Sale info for a batch of product ids — the polling half of sale tracking.

View as MarkdownUpdated Aug 19, 2026
POST/api/external/drops/check-status

Sale info for a batch of product ids — the polling half of sale tracking.

Poll it periodically (every few minutes is plenty) with the productIds you are tracking. Amounts are gross buyer-paid totals in cents. sales keeps its original one-entry-per-product shape; orders lists every paid order per product with its per-fan externalRef — use that for shared drops (or the drop.paid webhook).

Truncation, omission, refunds

At most 200 ids are processed per call — extras are dropped without an error, so chunk larger lists. Unsold and unknown ids are omitted from the response (only paid: true entries appear). And unlike earnings, this endpoint does NOT exclude refunded or charged-back orders — a refunded sale still reports paid. Reconcile against GET /api/external/earnings for net truth.

Authentication

Send the creator's API key as a bearer token: Authorization: Bearer dpfn_…. See Authentication & API keys.

An agency's own key can call this for a creator it manages by adding X-Dropfans-Account: <account id> (needs canManageDrops). See Agencies.

Request body

Content type: application/json

NameTypeRequiredDescription
productIdsstring[]RequiredProduct ids to check (≤200 — extras silently dropped). Non-strings filtered out; an empty array returns {"sales":{}}.
Max items: 200
Check two drops
{
  "productIds": [
    "clxdr0p000001prod",
    "clxdr0p000002prod"
  ]
}

Responses

200Sales map — only sold products appear. Multiple paid orders on one product report the most recent.
NameTypeDescription
salesSalesMapproductId → most recent sale.
Show child attributes
{productId}objectKeyed by the product ids you sent. Unsold and unknown ids are OMITTED — only entries with paid:true come back. Multiple paid orders on one product report the most recent. Refunded/charged-back orders are NOT excluded here (unlike earnings) — cross-check GET /api/external/earnings for net truth.
Show child attributes
paidbooleanAlways true — unsold products simply do not appear.
saleAmountCentsintegerGross buyer-paid total in **cents** (order.totalCharged × 100).
buyerEmailstring | nullThe buyer’s email when known, else null.
Format: email
ordersOrdersByProductproductId → every paid order (newest first), each with its externalRef. Added 2026-10-17.
Show child attributes
{productId}Order[]Every paid order on that product, newest first — one entry per fan on a shared drop.
Show child attributes
orderIdstringThe order id. Unique per sale — dedupe on it.
productIdstringThe drop that was bought.
accountIdstringThe creator who sold it (the account behind the key).
externalRefstring | nullYour per-fan checkout reference from the link the buyer opened (?m= on the web, b_{productId}_{ref} in Telegram). Null when the buyer came without one. Not proof of identity — the buyer can edit the link.
Max length: 32
Pattern: ^[A-Za-z0-9_-]{1,32}$
amountCentsintegerGross buyer-paid total in **cents** (VAT included).
currencystringAlways USD.
One of: USD
paidAtstring | nullWhen the payment settled (UTC).
Format: date-time
paidWithstringCard, or the buyer’s prepaid wallet credits.
One of: card, credits
statusstringCurrent state of the sale.
One of: paid, refunded, charged_back
buyerobjectWho paid. Every field may be null for a guest checkout.
Show child attributes
idstring | nullThe buyer’s account id, when signed in.
emailstring | nullBilling / account email.
Format: email
telegramUserIdstring | nullTelegram user id (as a string) when the buyer used the Mini App — cross-check it against your externalRef.
telegramUsernamestring | nullTelegram @username without the @, when known.
Example response
{
  "sales": {
    "clxdr0p000001prod": {
      "paid": true,
      "saleAmountCents": 2500,
      "buyerEmail": "[email protected]"
    }
  },
  "orders": {
    "clxdr0p000001prod": [
      {
        "orderId": "clxor0001order",
        "productId": "clxdr0p000001prod",
        "accountId": "clx2f8a1b0001qw3k",
        "externalRef": "tg_48213377",
        "amountCents": 2500,
        "currency": "USD",
        "paidAt": "2026-10-17T16:20:00.000Z",
        "paidWith": "card",
        "status": "paid",
        "buyer": {
          "id": "clxbu0001buyer",
          "email": "[email protected]",
          "telegramUserId": "48213377",
          "telegramUsername": "fan_one"
        }
      }
    ]
  }
}

Errors

StatusBodyWhen
400{"error":"Invalid JSON body"}The body is not valid JSON.
401{"error":"Unauthorized","code":"unauthorized"}Missing or invalid API key.
500{"error":"Failed to check drop status"}Query failed — retry later.
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.
403{"error":"This key cannot act for that account.","code":"account_not_managed"}`X-Dropfans-Account` names an account this key cannot act for: not an agency’s own key, no ACCEPTED management, or the agency or account 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"}With `X-Dropfans-Account`: the agency lacks `canManageDrops` on that account.

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 -X POST "https://www.dropfans.io/api/external/drops/check-status" \
  -H "Authorization: Bearer $DROPFANS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "productIds": [
    "clxdr0p000001prod",
    "clxdr0p000002prod"
  ]
}'

Questions? [email protected]