Some of the actions performed via our application's screens can also be carried out by sending requests to our Rest APIs.

API Documentation 

If you are interested in creating signature or certification requests via API, you will find what you need here.

Webhooks

If you are interested in implementing webhooks, or if you are unfamiliar with the term and would like to learn more, click here to find out more and discover how to set them up.

Embedded signature in your application screens

If you are interested in using embedded signatures with an Iframe directly integrated into your application screens, or if you would like to learn more about it, then click here.

Practical information

Connecting to the API

Connection to our API is achieved using an authentication token, which can be created from the Tediji screens.

Click on the ‘Hello XXX’ button at the top right, then on ‘Channel management’. This screen allows you to add a new token by entering a name and an expiry date.

Once you have entered the information, press ‘Create’. Your token will be added to the list of tokens at the bottom of the screen.

Swagger

You can view and test our Rest APIs on Swagger via this link.

From this new tab, you will need to log in to make your requests. To do so, click on the ‘Authorise’ button and fill in the required field with the token ID you retrieved earlier.

For example, if you want to check that a document has been certified, go to the ‘Check’ category and click on the ‘/check’ feature.

There you will see a description of the feature, as well as an example of the information you will need to provide and an example of the information you will receive once the request has been made.

Click on the ‘Try it out’ button to use this feature. You can now fill in the information required for your request by replacing the information in the example. Once you have filled in the information, click on the ‘Execute’ button.

If your request was successful, you will receive a response with the code ‘200’ and additional information if necessary. Otherwise, you will receive an error message explaining the cause.