Add media to vault list
Add one or more media items to a vault list (folder) for organization.
Add one or more media items to a vault list (folder) for organization.
OnlyFans only. Requests made with a user-id belonging to a Fansly account are rejected — use the platform-neutral CRM data routes (/notifications, /balances, /chats, /purchases, /subscribers/cached, ...) which are Fansly-aware.
Guide: The two surfaces
Authorization
apiKey Your CRM panel API key
In: header
Path Parameters
Vault list ID
Header Parameters
Creator account ID of the account to act as (e.g. 509955039). Required — omitting it returns 400 user-id header is required. Use GET /accounts to list your connected accounts. On /api2/v2/* the account must be an OnlyFans account; Fansly accounts are rejected there.
Proxy URL — HTTP or SOCKS5 (e.g. http://user:pass@host:port or socks5://user:pass@host:port). Optional on post-connection routes, where it overrides the proxy saved at login time. Required on the connection routes (POST /accounts/login, POST /accounts/login/cookies, POST /accounts/login/verify-otp) for OnlyFans accounts; optional for Fansly.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
curl -X POST "https://example.com/api2/v2/vault/lists/0/media" \ -H "user-id: 509955039" \ -H "Content-Type: application/json" \ -d '{ "mediaIds": [ 0 ] }'Attach vault media to post/message PUT
Attach a media item from the vault to an existing post or message. The media must already be uploaded.
Find vault media by MD5 (dedupe) GET
Deduplication / file→vault-item lookup. Given the MD5 of an original file, returns the matching vault media if that exact byte content was previously uploaded, or 404…