Getting Started

Overview

The BlurIt Anonymization API allows clients to use the BlurIt Anonymization platform to blur faces and licence plates in images and videos.

Principles

The BlurIt Anonymization API contains predictable resource-oriented URLs, that accept JSON request bodies and returns JSON responses. It uses standard HTTP responses codes (200, 404, etc.) and verbs (GET, POST, etc.) as well as an HTTP header for authentication.

How it works ?

Authentication

Authentication is made with the POST /login route, with clientId and a secretId as parameters. It will return an access token that will be needed to call all other routes, as well as a refresh token. The access token have a lifetime of 1 hour. The /login route does not use any authorization.

Call the routes

Once authenticated, you can use the API. All routes require the access token to be sent in the Authorization HTTP header as a Bearer token : Authorization: Bearer xxxxxxx, where xxxxxxx is the access_token you received in the POST /login response.

Refresh token

If your access token is expired, you need to refresh your access token by calling the POST /token route with your refresh token in the body .

⚠ Important: The access token must be included in the Authorization header even if it's expired.