Delete a drop nobody has bought
API reference

Delete a drop nobody has bought

Deletes a drop that has no orders — not even an unfinished checkout. Once anyone has an order on it, buyers' access depends on it and the call returns `409 has_orders`.

View as MarkdownUpdated Oct 26, 2026
DELETE/api/external/v1/drops/{id}also served at /api/external/drops/{id}New

Deletes a drop that has no orders — not even an unfinished checkout. Once anyone has an order on it, buyers' access depends on it and the call returns 409 has_orders.

The vault media stays in the vault either way.

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

DELETE /api/external/v1/creators/{creatorId}/drops/{id} — 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.

Path parameters

NameTypeRequiredDescription
idstringRequiredThe product (drop) id.

Responses

200Deleted.
NameTypeDescription
idstringThe deleted drop’s id.
deletedbooleanAlways true.
Example response
{
  "id": "clxdr0p000001prod",
  "deleted": true
}

Errors

StatusBodyWhen
401{"error":"Unauthorized","code":"unauthorized"}Missing or invalid API key.
404{"error":"Drop not found"}No such drop on this account.
409{"error":"This drop has orders, so buyers keep access to it and it cannot be deleted.","code":"has_orders"}The drop has at least one order (paid or started).
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 drops API category enabled. Contact support to enable it.","code":"api_category_disabled","category":"drops"}Your app has the Drops & checkout links [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 -X DELETE "https://www.dropfans.io/api/external/v1/drops/$PRODUCT_ID" \
  -H "Authorization: Bearer $DROPFANS_API_KEY"

Questions? support@dropfans.io