Individual files on Uploadcare can be joined into groups. Those can be used to better organize your workflow. Technically, groups are ordered lists of files and can hold files together with Image Transformations in their URLs. The most common case with creating groups is when users upload multiple files at once.
Note, a group itself and files within that group MUST belong to the same project. Groups are immutable and the only way to add/remove a file is creating a new group.
- Group identifiers
- Group properties
- Get a paginated list of groups, GET
- Get a file group by UUID, GET
- Store all files in a group, PUT
Groups are identified in a way similar to individual files. A group ID consists of a UUID followed by a “~” tilde character and a group size: integer number of files in group. For example, here is an identifier for a group holding 12 files:
Date and time when a group was created.
Date and time when files in a group were stored.
Number of files in a group.
Public CDN URL for a group.
API resource URL for a group.
Multiple groups can be present in your project. This means you might first want to access a list of those groups, then individual groups, and files.
A preferred amount of groups in a list for a single response. Defaults to 100, while the maximum is 1000.
A starting point for filtering group lists. MUST be a
datetime value with
used as a separator:
Specifies the way groups are sorted in a returned list,
datetime_created- by creation time, ascending order.
-datetime_created- by creation time, descending order.
You may refer to getting a single file for a request and response example.
For your files to be available on from our CDN after the initial 24-hour period, you should store them. You can do that by either storing a file group, storing an individual file or storing a list of files.
You may refer to storing a single file for a request and response example.