Handling file groups
Groups serve a purpose of better organizing files in your Uploadcare projects. You can create one from a set of files by using their UUIDs.
Note, Media Processing operations are not stripped off but stored in a group together with file UUIDs.
Such requests return a JSON or JSONP response with your group info.
Defines a target project you work with, by its public key. If
pub_key is missing, method returns an error,
[HTTP 400] pub_key is required.
That parameter defines a set of files you want to join in a group. Technically, it should be a set of ordered parameters where can either be
n a unique positive number or zero. Each parameter can be a file UUID or a CDN URL, with or without applied Media Processing operations. If the parameter is missing or empty, method returns an error,
[HTTP 400] no files[N] parameters found.
If any of the files you provide is represented with an invalid UUID or CDN URL, the method returns an error,
[HTTP 400] this is not valid file url: http://invalid/url.
If some of the files you provide are missing in the project defined by your
pub_key, then method returns an error:
[HTTP 400] some files not found.
Sets the name of your JSONP callback function.
Below is the example of joining two files in a group: one by UUID and another with its Media Processing operations.
curl -F "pub_key=demopublickey" \
-F "files=d6d34fa9-addd-472c-868d-2e5c105f9fcd" \
-F "files=b1026315-8116-4632-8364-607e64fca723/-/resize/x800/" \