Move a vault item to a folder
API reference

Move a vault item to a folder

Files a vault item into a folder, or unfiles it back to "All".

View as MarkdownUpdated Aug 19, 2026
PATCH/api/external/v1/vault/{id}/folderalso served at /api/external/vault/{id}/folder

Files a vault item into a folder, or unfiles it back to "All".

Omitting folderId (or sending null, "", an empty body — even a malformed body) unfiles the item. That leniency is deliberate: {} is the documented unfile signal.

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

PATCH /api/external/v1/creators/{creatorId}/vault/{id}/folder — an agency's own key for a creator or AI persona it manages (needs canManageVault), 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 vault item id.

Request body

Content type: application/json

NameTypeRequiredDescription
folderIdstring | nullOptionalDestination folder id. Omit/null/"" to unfile.
Move into a folder
{
  "folderId": "clxf0ld3r0001abcd"
}
Move back to All
{}

Responses

200Moved.
NameTypeDescription
successbooleanAlways true.
Example response
{
  "success": true
}

Errors

StatusBodyWhen
400{"error":"folderId must be a string"}`folderId` is present but not a string (e.g. a number).
400{"error":"This folder is managed automatically and cannot receive items."}The destination is a system folder.
401{"error":"Unauthorized","code":"unauthorized"}Missing or invalid API key.
404{"error":"Vault item not found"}No such item on this account.
404{"error":"Folder not found"}No such folder on this account.
500{"error":"Failed to move vault item"}Write 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.
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":"canManageVault"}For a managed creator: the agency lacks `canManageVault` on that account.
403{"error":"This app does not have the vault API category enabled. Contact support to enable it.","code":"api_category_disabled","category":"vault"}Your app has the Vault [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 PATCH "https://www.dropfans.io/api/external/v1/vault/$VAULT_ITEM_ID/folder" \
  -H "Authorization: Bearer $DROPFANS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "folderId": "clxf0ld3r0001abcd"
}'

Questions? support@dropfans.io