Upcoming API Changes

Here is a list of changes to the API that we want you to be aware of well in advance as they may affect how you use Clarifai's platform. These changes include scheduled downtime and other improvements in stability, performance or functionality of the Clarifai platform in order to better serve you as a customer. Some of these changes may not be backward compatible and thus require you to update how you call our APIs. We created this page with the mindset of being as transparent as possible so you can plan any corresponding changes in advance and minimize any interruptions to your usage of Clarifai.
The dates listed in the following tables are the date we plan to make the change. We may actually make the change in the days following the specified date. However, to be safe, your client-side code needs updating before that date to minimize any downtime to your applications.
We will continue to update this page regularly, so a good way to always stay up to date is to watch our documentation repo on GitHub.
Upcoming Changes
Date
Change
Completed Changes
Date
Change
September 11, 2019. 9:00am ET
Scheduled Database Downtime

We plan to upgrade our database to make it faster and provide more space for your applications. We expect a few minutes of downtime during this upgrade but you should plan for up to an hour of downtime in case things don't go as expected. This will primarily affect the following uses of our platform: POST/GET/PATCH/DELETE inputs, Search, Custom Training, Model Evaluation
September 24, 2019. 5:00pm ET
POST /inputs will only operate asynchronously

We are cleaning up some inconsistent behavior in the API where a single image added with POST /inputs was a synchronous operation, but a batch of images was asynchronous. We are making both asynchronous. This allows us to provide more advanced functionality with workflows that index your inputs.

What this means for your code is if you application relies on added inputs having already been indexed when the POST /inputs call returns, you now need to add a second call to GET /inputs/{input_id} in order to check the status of the input you just added to look for 30000 (INPUT_IMAGE_DOWNLOAD_SUCCESS) status code.
September 30, 2019. 5:00pm ET
DELETE /inputs will only operate asynchronously

Along the same lines as POST /inputs becoming completely asynchronous, we are cleaning up some inconsistent behavior in the API for deleting inputs. Previously, when a single image is deleted with DELETE /inputs or DELETE /inputs/{input_id} it was a synchronous operation, but when a batch of images were deleted it was asynchronous. We are making both asynchronous. This allows us to provide more advanced functionality with workflows that index your inputs.

What this means for your code is if you application relies on the input having been deleted when the DELETE /inputs or DELETE /inputs/{input_id} calls return, you now need to add a second call to GET /inputs/{input_id} in order to check that it fails with a not found error.
November 20, 2019
image.crop argument will be deprecated

In some requests we used to allow cropping of images during the request using the image.crop field. This was for convenience only, but in reality is was rarely ever used and significantly complicates the processing pipelines under the hood. Therefore, we will no longer support the image.crop field in any requests that used to accept it. 

If you want to have similar behaviour please crop the images on the client side and send the cropped bytes as base64 encoded image data.
Feb 1, 2020
Deprecation of Focus Model

The Focus model will no longer be supported and will be removed from our API after this point in time. If you have requests for recognizing focus and blurry regions within images please contact sales@clarifai.com so that we can help you directly.
Feb 3, 2020
PATCH /inputs overwrite action change

The overwrite action when patching inputs currently has some inconsistent behavior. If you patch input.data.metadata or input.data.geo fields on an input that has input.data.concepts already added to it, these concepts will remain after the patch even though the patch action was overwrite.

Going forward, the overwrite behavior will overwrite the entire data object with what is included in the PATCH /inputs API call. Therefore if concepts are not provided in the patch call, but were originally on that input, they will be erased (overwritten with an empty list of concepts). You can maintain the current behvaiour by always sending back the complete data object from GET /input/{input_id} along with any modification to it if you are using the overwrite action. 

Update: this change has become more complicated than originally expected and we may not undergo it after all, more to come in future. Still a good idea to update your PATCH calls to use the merge or remove actions instead of overwrite due to overwrite's inconsistency.
Feb 12, 2020. 9:00am ET
Deprecation of Face model type names

The facedetect* model types will be deprecated in favor of their more general detect* counterparts. For example these would be the changes of model type:
facedetect -> detect
facedetect-identity -> detect-concept
facedetect-demographics -> detect-concept
facedetect-embed -> detect-embed
This change is to unify the APIs around face products and object detection products so that they are compatible everywhere either is used.
February 24, 2020. 9:00am ET
[Consolidation of Input Related Status Codes

 As we support more media types, it is impractical to have status codes for each. Thus status codes will now be prefixed INPUT_... rather than INPUT_IMAGE_... or INPUT_VIDEO_.... We will maintain the int value for the INPUT_IMAGE_... prefixed statuses, but no longer support the int values associated with statuses prefixed INPUT_VIDEO....
Feb 27, 2020. 9:00am ET
​Deprecation of Face object from API

The Face object in our API responses will be deprecated in favor of a list of Concepts that other model types return. This should only effect users of the Celebrity, Demographics, or custom face recognition models where the data.face attributes like data.face.identity, data.face.age_appearance, data.face.gender_appearance, and data.face.multicultural_appearance will now be returned in the list of data.concepts Concept object. The API will return both for a while during the transition to give you time to update your code away from using the data.face objects altogether. We are doing this to simplify the API interface and make it more easily compatible for advanced functionality that is coming soon in workflows! The custom face recognition and celebrity models are a simple change to just access the new data.concepts field, but the demographics model is a more fundamental change away from having three distinct lists of concept to a single list. In order to cope with this, we have introduced a vocab_id field in each data.concepts entry that is returned by the demographics model so that you can distinguish age_appearance, gender_appearance and multicultural_appearance.To convert new format to old format, check python example [here][https://github.com/Clarifai/docs/tree/master/examples/deprecate_face_object].
Apr 1, 2020. 9:00am ET
Stop returning Face object from API

 This is part of deprecation of Face object from API. Currently as transition period, we are returning both data.face and data.concept. We will stop returning data.face after Apr 1st 2020. The new [response][https://github.com/Clarifai/docs/tree/master/examples/deprecate_face_object/new_response.json] will only contain concepts.

Saved searches

Next - Product Updates

Changelog

Last updated 2 months ago

Date	Change
September 11, 2019. 9:00am ET	Scheduled Database Downtime We plan to upgrade our database to make it faster and provide more space for your applications. We expect a few minutes of downtime during this upgrade but you should plan for up to an hour of downtime in case things don't go as expected. This will primarily affect the following uses of our platform: POST/GET/PATCH/DELETE inputs, Search, Custom Training, Model Evaluation
September 24, 2019. 5:00pm ET	`POST /inputs` will only operate asynchronously We are cleaning up some inconsistent behavior in the API where a single image added with `POST /inputs` was a synchronous operation, but a batch of images was asynchronous. We are making both asynchronous. This allows us to provide more advanced functionality with workflows that index your inputs. What this means for your code is if you application relies on added inputs having already been indexed when the `POST /inputs` call returns, you now need to add a second call to `GET /inputs/{input_id}` in order to check the status of the input you just added to look for 30000 (INPUT_IMAGE_DOWNLOAD_SUCCESS) status code.
September 30, 2019. 5:00pm ET	`DELETE /inputs` will only operate asynchronously Along the same lines as `POST /inputs` becoming completely asynchronous, we are cleaning up some inconsistent behavior in the API for deleting inputs. Previously, when a single image is deleted with `DELETE /inputs` or `DELETE /inputs/{input_id}` it was a synchronous operation, but when a batch of images were deleted it was asynchronous. We are making both asynchronous. This allows us to provide more advanced functionality with workflows that index your inputs. What this means for your code is if you application relies on the input having been deleted when the `DELETE /inputs` or `DELETE /inputs/{input_id}` calls return, you now need to add a second call to `GET /inputs/{input_id}` in order to check that it fails with a not found error.
November 20, 2019	`image.crop` argument will be deprecated In some requests we used to allow cropping of images during the request using the `image.crop` field. This was for convenience only, but in reality is was rarely ever used and significantly complicates the processing pipelines under the hood. Therefore, we will no longer support the `image.crop` field in any requests that used to accept it. If you want to have similar behaviour please crop the images on the client side and send the cropped bytes as base64 encoded image data.
Feb 1, 2020	Deprecation of Focus Model The Focus model will no longer be supported and will be removed from our API after this point in time. If you have requests for recognizing focus and blurry regions within images please contact sales@clarifai.com so that we can help you directly.
Feb 3, 2020	`PATCH /inputs` overwrite action change The overwrite action when patching inputs currently has some inconsistent behavior. If you patch `input.data.metadata` or `input.data.geo` fields on an input that has `input.data.concepts` already added to it, these concepts will remain after the patch even though the patch action was `overwrite`. Going forward, the overwrite behavior will overwrite the entire `data` object with what is included in the `PATCH /inputs` API call. Therefore if concepts are not provided in the patch call, but were originally on that input, they will be erased (overwritten with an empty list of concepts). You can maintain the current behvaiour by always sending back the complete `data` object from `GET /input/{input_id}` along with any modification to it if you are using the `overwrite` action. Update: this change has become more complicated than originally expected and we may not undergo it after all, more to come in future. Still a good idea to update your PATCH calls to use the `merge` or `remove` actions instead of `overwrite` due to `overwrite`'s inconsistency.
Feb 12, 2020. 9:00am ET	Deprecation of Face model type names The `facedetect` model types will be deprecated in favor of their more general `detect` counterparts. For example these would be the changes of model type: `facedetect` -> `detect` `facedetect-identity` -> `detect-concept` `facedetect-demographics` -> `detect-concept` `facedetect-embed` -> `detect-embed` This change is to unify the APIs around face products and object detection products so that they are compatible everywhere either is used.
February 24, 2020. 9:00am ET	[Consolidation of Input Related Status Codes As we support more media types, it is impractical to have status codes for each. Thus status codes will now be prefixed `INPUT_...` rather than `INPUT_IMAGE_...` or `INPUT_VIDEO_...`. We will maintain the int value for the `INPUT_IMAGE_...` prefixed statuses, but no longer support the int values associated with statuses prefixed `INPUT_VIDEO...`.
Feb 27, 2020. 9:00am ET	Deprecation of Face object from API The Face object in our API responses will be deprecated in favor of a list of Concepts that other model types return. This should only effect users of the Celebrity, Demographics, or custom face recognition models where the `data.face` attributes like `data.face.identity`, `data.face.age_appearance`, `data.face.gender_appearance`, and `data.face.multicultural_appearance` will now be returned in the list of `data.concepts` Concept object. The API will return both for a while during the transition to give you time to update your code away from using the `data.face` objects altogether. We are doing this to simplify the API interface and make it more easily compatible for advanced functionality that is coming soon in workflows! The custom face recognition and celebrity models are a simple change to just access the new `data.concepts` field, but the demographics model is a more fundamental change away from having three distinct lists of concept to a single list. In order to cope with this, we have introduced a `vocab_id` field in each `data.concepts` entry that is returned by the demographics model so that you can distinguish `age_appearance`, `gender_appearance` and `multicultural_appearance`.To convert new format to old format, check python example [here][https://github.com/Clarifai/docs/tree/master/examples/deprecate_face_object].
Apr 1, 2020. 9:00am ET	Stop returning Face object from API This is part of deprecation of Face object from API. Currently as transition period, we are returning both `data.face` and `data.concept`. We will stop returning `data.face` after Apr 1st 2020. The new [response][https://github.com/Clarifai/docs/tree/master/examples/deprecate_face_object/new_response.json] will only contain concepts.