API introduction¶

API allows you to use Rythmex programmatically. From birds prespective, it allows you to transcipt audio and video files bypass the web interface. This is useful if you want to integrate Rythmex into your own application or workflow.

So, let’s start!¶

First, you need to have an account (not subuser invited in the team) on Rythmex. Please use this link https://rythmex.com/register to register user. For API users we recommend to use direct registration, instead of Google or Facebook (but it’s up to you). Difference only that we make all tests on direct registered users.

Detailed documentation about API you can find in multiple sources:

ReDoc: https://rythmex.com/api/schema/public/redoc/ (well structured API endpoints documentation)
Swagger: https://rythmex.com/api/schema/public/swagger-ui/ (interactive API endpoints documentation. You can login and try API endpoints directly from Swagger)
Download YML file: https://rythmex.com/api/schema/public/ (YML file with API endpoints documentation, that you can use to generate your own documentation)

Lets dive little more in details!¶

We have two types of Authorization:

JWT token
API token

JWT Token¶

Please use JWT token for API calls from client side (browser, mobile app, etc).

On the other hand is API token, that you can use for API calls from server side (backend, etc).

This is essential for your security, because you don’t want to expose your API token to the client side.

JWT token consist of two parts: access token and refresh token. Both of this tokens stateless (i.e. we don’t store them on our side).

Access token is short lived token (1 hour), that you can use to call API endpoints.

Refresh token is long lived token (7 days), that you can use to get new access token.

This is common practice for JWT tokens and many JS frameworks have built-in support for this.

API Token¶

API token is living till you rotate it manually. So, you can not expose it or use in some exposed to public places. Even browser headers only the place, where you expose it, it’s still unsafe. So please use it only on server side. It’s quite comfortable to use it on server side because you don’t need to rotate it every hour.

Let’s practice a bit!¶

Authorization¶

First of all we need API token. You can get it in https://rythmex.com/api/schema/public/swagger-ui/#/Authentication/v1_auth_api_token_get_or_create_create. Press “Try it out” >> Enter your email and password >> Press “Execute” >> Copy token from response body.

../../_images/api_token_swagger_endpoint_try_it.png

../../_images/api_token_swagger_endpoint.png

Congratulations! You have your API token now! Let’s try to use it.

On the very top of this page you can see “Authorize” button. Press it!

../../_images/available_authorization.png

Here you can see two kinds of authorization: JWT and API token. Let’s use API token first. Please paste your token from previous step in “Value” of tokenAuth (apiKey) in format Token <your_token> and press “Authorize” button. That’s it! You are authorized now! Now you can use API endpoints.

Note

Your token will be stored in your localstorage and send with every request in “Authorization” header. Even after page reload you will be authorized, even it’s not shown in “Authorize” window. If you want to logout, please press “Logout” in “Authorize” window with any value in “Value” field.

With JWT token a bit more tricky. JWT token is living only 1 hour. So, you need to refresh it every hour. Swagger will not do it for you automatically. So, after 1 hour you will get 401 error on any call, that requires authorization.

Let’s try it!

You can get it in https://rythmex.com/api/schema/public/swagger-ui/#/Authentication/v1_auth_jwt_create_create. Press “Try it out” >> Enter your email and password >> Press “Execute” >> Copy access token from response body.

Please paste your token from previous step in “Value” of jwtAuth (http, Bearer) in format <your_token> and press “Authorize” button. That’s it! You are authorized now! Now you can use API endpoints.

How it works?¶

To act as authorized user you need to pass your token in header of each request.

In case of JWT token it looks like: Authorization: Bearer <your_token>.

In case of API token it looks like: Authorization: Token <your_token>.

Congratulations! You are ready to use API!

What’s next?

Please read other topics in this documentation to get more information about API endpoints + each endpoint has description of how to use it.

../../_images/api_token_swagger_endpoint_description.png