Skip to content

API Access

Testomat.io provides a robust API that allows users to integrate, automate, and extend their test management workflows. Testomat.io uses JSON API as standard for Request and Response data. Access to the API is secured using Access Tokens, which ensure that only authorized systems and users can interact with your projects.


There are two main types of access tokens in Testomat.io:

  • Provide full API-driven access to all projects within your Testomat.io account.
  • Ideal for administrative or automation tasks that span multiple projects.
  • Limit API access to a specific project only.
  • Recommended for importing and reporting.

Testomat.io - Access Tokens


API Authentication with either General Token or Email + Password

Section titled “API Authentication with either General Token or Email + Password”

Before interacting with the Testomat.io API, you must authenticate and obtain a JWT token, which is required for all subsequent requests.

You can authenticate in one of two ways:

Request Example:

Terminal window
POST /api/login
{
"api_token": "testomat_EXAMPLETOKENt7dp5VFPR_h8b8SO12EXAMPLETOKEN"
};

Option 2 Log In Using Your Email + Password

Section titled “Option 2 Log In Using Your Email + Password”

Request Example:

Terminal window
POST /api/login
{
"email": "test.testomat@gmail.com",
"password": "Test123!"
};

After sending your login request, you’ll receive a JSON Web Token (JWT) in the response. This token is used to authenticate all subsequent API calls.

Response Example:

{
"jwt": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9"
}

Include the received JWT in the Authorization header for all subsequent API requests.

Because test suites are nested, you’ll need to fetch them in multiple requests to reconstruct the full hierarchy.

Terminal window
GET /api/<project_name>/suites

Iterate over each returned suite ID and retrieve its details:

Terminal window
GET /api/<project_name>/suites/:suite_id

Repeat this process recursively for each child suite to build the complete suite + test tree.

Each suite response includes:

  • Suite metadata (name, ID, description, etc.)

  • Child suite IDs

  • Tests contained within that suite

You can use the API to list, create, and inspect runs within a project.

Important: In the testomat.io API, the path parameters /run/... and /testrun/... refer to two different resources:

  • /run/... endpoints return information about a Run — the execution session itself — including the list of tests that belong to it.
  • /testrun/... endpoints return Test Run records — the results of individual tests executed within a run.

Retrieve all test runs associated with a project.

Terminal window
GET /api/{project_id}/runs

Retrieve details of a specific run by ID.

Terminal window
GET /api/{project_id}/run/{id}

To get all test results from a specifc run:

Terminal window
GET /api/{project_id}/testruns?run_id={run_id}

For a complete list of available endpoints, request parameters, and schemas, see the official documentation:

Testomat.io API Reference

Importing and Reporting with Project Token

Section titled “Importing and Reporting with Project Token”

Project Tokens are used when working with Importing and Reporting APIs in Testomat.io. These tokens provide access specifically for operations such as importing tests or reporting test results to a given project.

Please check the documentation below for for details:

Importing API (1.0.0)

Reporting API (1.0.0)