LoadNinja REST API

Last modified on November 11, 2021

LoadNinja REST API (or LoadNinja API) is used for accessing LoadNinja data and for integration with external systems. It is available to all LoadNinja customers.

Swagger UI

The API has a web interface that contains and describes all the available API operations and parameters, and allows you to make API calls and view the returned data.

To access the API web interface, go to:


Keep in mind that the web interface accesses and changes real-world data.

Base URL and scheme

To access the API from external tools and utilities, use the following base URL:


The LoadNinja API uses HTTPS as the transfer protocol (scheme).


Each request to the LoadNinja API should include an authorization header with a 32-symbol API key. To authenticate, append the API key as the authorization header to your request in the following format:

authorization: 123aa578-aa2b-bb2c-becf-123456c122
  1. In LoadNinja, go to  > Settings.

  2. Switch to the API Keys tab.

  3. Click Generate.

  4. Confirm this action in the subsequent dialog.

  5. After you do this, LoadNinja will generate an API key.

    • To copy the key to the clipboard, click .

    • To view the key, click .

    • To stop using this key and create a new one, click Regenerate, then confirm this action in the subsequent dialog.

Data format headers

LoadNinja API operations use the JSON data format for request bodies.

To provide the server with the correct information about the body format, append the following header to the requests that have a body:

Content-Type: application/json

Since most operations also return JSON data, please add the Accept header to your requests as well:

Accept: application/json

Response codes

LoadNinja API uses the following status codes for responses:

Status code Description
200 The request was completed successfully. LoadNinja sent the expected response.
400 The request is missing the authorization header, or the authorization key is invalid.
500 The request was not processed due to an internal error. For example, the client tried to access a non-existing resource, or used a wrong HTTP method.

Note: An error response may contain additional information on the error within the request body.

See Also

LoadNinja Tutorial
Typical Use Cases

Highlight search results