Skip to main content

Using the API

Welcome to the Re:infer API. We strive to make the API predictable, easy to use and painless to integrate. If there is anything you feel we can do to improve it or if you encounter any bugs or unexpected behaviour, please contact support and we will get back to you as soon as possible.

You can see all available endpoints in the API Reference. There is also an API Tutorial.

API Endpoint

All API requests are sent to Re:infer as JSON objects to your tenant endpoint over HTTPS.

Tenants onboarded via UiPath:<my_uipath_organisation>/<my_uipath_tenant>/reinfer_/api/...

Tenants onboarded via Re:infer:

Development and production environments

In Re:infer, development and production data and workflows can be separated either by having separate tenants, or by placing them in separate projects in the same tenant. In each case the data access is permissioned separately (so that developers can have admin access to development data while stricter controls can be placed on production). If using separate tenants then the API endpoint is different for each of development and production data; if using separate projects in the same tenant then that single tenant's endpoint is used for both.


All API requests require authentication to identify the user making the request. Authentication is provided through an access token. The developer access token can be obtained from your Manage Account page.


You can have only one API token active at a time. Generating a new token will invalidate the previous one.

You need to include the following HTTP header for every API call you make, where $REINFER_TOKEN is your Re:infer API token.

Authorization: Bearer $REINFER_TOKEN

The bash examples in the API Reference assume that you have saved your token in an environment variable. The Python and Node examples in the API Reference assume that the token has been stored in a local variable REINFER_TOKEN via your chosen config solution.

curl -X GET 'https://<my_api_endpoint>/api/...' \
-H "Authorization: Bearer $REINFER_TOKEN"


Each API endpoint in the API Reference lists its required permissions. You can view the permissions you have by going to your Manage Account page. The page shows the Projects you have access to and the Permissions you have in each project.


We use conventional HTTP response codes to indicate success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided request and codes in the 5xx range indicate a problem with the Re:infer platform.

Requests that error will also return a body with a status value of error instead of ok, and an error message describing the error.

curl -X GET 'https://<my_api_endpoint>/api/v1/nonexistent_page' \
-H "Authorization: Bearer $REINFER_TOKEN"

Note that your request can fail due to issues in your network before it reaches Re:infer. In such cases the response you receive will look different from the Re:infer error response described above.

Performance Timing

We use the Server-Timing HTTP header to communicate the time taken for requests to our API to be processed. We include a single metric, total, which you can use to measure how long our platform took to process your request free from latency of the network request.

An example of the header as it will be seen in a response:

Server-Timing: total;dur=37.7

Server-Timing values are always in milliseconds, so in this case the API request with this header value took 37.7 milliseconds to process on our platform.