5-second timeout for all processing endpoints

A timeout of 5 seconds is introduced for all processing endpoints (/tagging, /croppings, /colors and /categorizations/...). For example if you send an image to "/tagging" and the API is unable to download and analyse the image in less than 5 seconds it will go unsuccessful. The analysis takes less than 50ms so the main factor here is the image download time.
Tip: If most of your request timeout, you'd better upload the images to our "/content" endpoint first (which is free and not accounted towards your usage) then use the content id to submit your images for processing.

Update in the general response of the usage endpoint

Until now, because of changes in the limiting, the response of the usage endpoint was broken and the data returned didn’t match the data displayed in the imagga.com dashboard. We fixed this but for backwards compatibility he API's /usage endpoint now accepts a fix parameter which should be set to 1 e.g.(/usage?fix=1) and combined with type general (the default one) will result in a completely different response which look like the following:

{
    "billable": {
        "daily": 0,
        "monthly": 19
    },
    "billing_period": {
        "end": 1456843043,
        "start": 1454337443
    },
    "last_request": "1455171842.036982",
    "limits": {
        "concurrency": 3,
        "monthly": 70000
    },
    "total": {
        "daily": 2,
        "monthly": 43
    }
}

As you can see, information about the number of billable (the ones subtracted from the limits) and total number of request is returned. Also UNIX timestamp of the last request and the start and end of the current billing period. The subscription plans’ limits could also be found in the limits key of the JSON response.