Authentication
In order to use the live caption and transcription services of the Verbit platform via API, authentication is required using JSON web token (JWT) authentication. This authentication method requires the customer to generate a JWT using a unique API key that identifies the customer. Authentication is performed using the Verbit authentication service API.
Note: If a previous integration is still using the original API token to authenticate post-production API calls, this is still a valid method for authentication and will still be supported. Also understand that these post-production APIs can now use the JWT authentication as well.
Before proceeding, an API key will need to be generated on the Verbit Platform.
The next step will be to acquire the bearer token. The user will need to make a POST call to the endpoint as shown below. In the body call, ensure the "api_key" property uses the API Key that was generated from the Verbit platform.
curl -X POST "https://users.verbit.co/api/v1/auth"
-H "Content-Type: application/json"
-d '{ "data": { "api_key": "<API-KEY>"} }'
The authentication API will then return the Bearer token:
{
"token": "eyJraWQiOiJIMVVkZUVXeGJxYjlHY2R5VjB3WFJyVWpzRG5nNUk3aGpwQUFGWHo3eGwwPSI...."
}
Now the Bearer token can be used in all the Verbit API calls in the Authorization
header property as shown here:
Authorization: bearer eyJraWQiOiJIMVVkZUVXeGJxYjlHY2R5VjB3WFJyVWpzRG5nNUk3aGpwQUFGWHo3eGwwPSI....
The Bearer token expires 24 hours after creation.
Updated 4 months ago