Product changes

We updated our Service Level Agreement (SLA) and added Maintenance Window. The agreement now includes the "Scheduled Maintenance" term.

This means we will not include possible downtimes within scheduled maintenance in our Monthly Uptime Percentage (MUP) calculations.

We will inform you about scheduled maintenance and possible consequential downtimes. In every message regarding scheduled maintenance, we will provide a description of what operations we will perform and which systems may be affected.

Indeed, we strive to minimize possible downtimes at all times.

We just updated our PHP library to 2.2.0 and further to 2.2.1 which is a minor fix with its changes added up to this changelog.

uploadcare-php allows you to implement Uploadcare Widget, Image Processing, and REST API in your PHP code.

Added

• Users are now allowed to specify their User Agent.
• User Agent reports library and integration versions used.
• The data-integration attribute to the widget reporting its version together with the library version used.

Here is a reporting example:

$api = new Uploadcare\Api(UC_PUBLIC_KEY, UC_SECRET_KEY);
$api->setFramework('Wordpress', '4.9.5');
$api->setExtension('PHPUploadcare-Wordpress', '2.6.0');

Changed

• User Agent reporting now uses a new default format.
• $api->getUserAgent() replaced with $api->getUserAgentHeader().

Deprecated

• (2.2.1) $api->getUserAgent() was deprecated and will be completely removed in the next major version. Replacement: $api->getUserAgentHeader().

Fixed

• Updated the $api->getGroupList($options = array()) method.
• Mistakes in method descriptions.
• Hitting max throttling attempts when a request was successful.

Check out the uploadcare-php repo on GitHub or look through the full changelog specifically.

Introducing Video Processing. You can now optimize videos, transcode them, cut fragments, and generate thumbnails.

Video Processing is available to all our customers and works via REST API, here is how:

• You post a processing job by making a REST API request; all the processing params are passed in the request.
• Once the job is finished, you get a UUID of a processed output.
• At the same time, the output becomes addressable via a CDN URL.

Here is what you can do with videos:

• Resize
• Adjust quality
• Transcode
• Cut fragments
• Generate thumbnails

Check out the complete Video Processing documentation here or drop us a line in case you have any questions.

Since March, we've changed our file backup mechanics. On a daily basis, we used to check your backup bucket and copy all the stored files that were missing. From now on, files only go to your backup once. And that's when they get stored. In the first case, files you've deleted could reappear. Currently, deleted files won't be restored automatically. However, you can always contact us to restore stuff you accidentally deleted.

Since we're no longer listing through your buckets, the number of respective requests lowers: your backup procedure gets much faster and cost effective.

For a good while, there was a limitation on which S3 buckets could be used for backup and as custom storage with Uploadcare. We're happy to announce Uploadcare now supports all the AWS regions (including Frankfurt, Seoul, and Mumbai).

If you're interested in the details, the problem was with AWS signature version 4.

We've added Webhooks support to Uploadcare, so now you may receive real-time updates about your uploads and build more dynamic and complex applications. You can manage your webhooks via project dashboard or REST API.

The Zapier integration (that uses webhooks behind the scenes) will help you set up workflows that include Dropbox, GMail, Google Spreadsheets, Trello, and hundreds of other awesome services with a few mouse clicks and no code :).

We're happy to present a new version of our REST API number 0.5. It's goal is to make dealing with resource lists like File list or Group list more effective.

First of all, we've removed the to parameter from request. Now it is used for internal purpose only and is not expected to be set manually. Don't send it as it will produce incorrect results. Also, we slightly changed the purpose for the from parameter - just think about it as a starting point for filtering results.

Secondly, we've added an ordering ability so now you can specify the way the result must be sorted. Just use the ordering parameter in requests, like this:

curl -H "Authorization: Uploadcare.Simple demopublickey:demoprivatekey" \
       "https://api.uploadcare.com/files/?ordering=-size&limit=10"

Currently, you can sort files by their datetime_uploaded and size in both directions: ascending and descending. For groups only datetime_uploaded (ascending and descending) is allowed.

You can read more about how to use this in the documentation for each resource.

REST API copy file requests now support "file in group" URL as a source parameter. Previously you had to know the individual file UUID or URL.

For example, now you can do this:

$ curl -X POST \
       -H "Authorization: Uploadcare.Simple demopublickey:demoprivatekey" \
       -d "source=https://ucarecdn.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx~10/nth/5/" \
       -d "store=true" \
       "https://api.uploadcare.com/files/"