Skip to main content
Files are documents your organization stores in AnyCRM and attaches to the records they’re relevant to — a contract on a deal, a signed proposal, an image on an account. Folders give them an optional organizing structure on top.

​
How uploads work

A file’s bytes never pass through the AnyCRM API request body. Uploading is a short handshake: the API issues a presigned upload URL scoped to your organization, the client uploads the bytes directly to storage, and a final confirmation call marks the file ready. This keeps large files (and their bandwidth cost) off the API server entirely. Downloading works the same way in reverse — the API hands back a short-lived presigned URL rather than streaming the bytes itself. Deleting a file is a soft delete — the underlying storage object stays in place — with one exception: aborting an upload that hasn’t been confirmed yet does remove the object, since nothing else could reference it.

​
Attachments

A file isn’t tied to a single record. Instead, an attachment is its own record linking a file to an entity (a deal, an account, a contact, and so on) — the same file can be attached to more than one thing, and attaching or detaching doesn’t affect the underlying file itself.

​
Folders

Folders form a simple tree — each folder optionally has a parent, and a file optionally belongs to one folder. There’s no folder-scoped permission model beyond the organization’s normal CRM scopes; folders are purely an organizing convenience, with the usual safeguards (you can’t create a cycle by moving a folder into its own descendant, and deleting a non-empty folder requires explicitly cascading the deletion to what’s inside it).

​
Technical reference

For the full endpoint-by-endpoint reference, see the Files API reference (starting at List Files) and the Folders API reference (starting at List Folders).