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/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.

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.

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/vault/$VAULT_ITEM_ID/folder" \
  -H "Authorization: Bearer $DROPFANS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "folderId": "clxf0ld3r0001abcd"
}'

Questions? [email protected]