Stopping the Recording Process

Chapter Prerequisites

To follow the steps described in this chapter, you need to obtain:

  • A token.
  • An identifier of a test run.

    The following values are used as example values throughout the chapter:

  • token_Qwe12345 as a token.
  • tr_1234 as an identifier of a test run.

The necessity to stop a baseline requests recording process is explained here in detail.

Stop the recording process by issuing the following API call:


Stop Recording Process
API call: GET /v1/test_run/test_run_id/action/stop
Authorization: Required With the token
HTTP header with the token: X-WallarmAPI-Token Serves to pass the token’s value to the API server
Parameters: test_run_id (required) The identifier of the test run to stop recording the baseline requests for

Example of a request:

curl --request GET \
  --url \
  --header 'Host:' \
  --header 'X-WallarmAPI-Token: token_Qwe12345'

Example of a response:

  "status": 200,
  "body": {
    "id": tr_1234,
    "recording": false,

If the request to the API server is successful, you are presented with the server’s response. The response provides useful information, including the state of the recording process (the recording parameter’s value).

If the parameter’s value is false, then the stop is successful.

The process of testing the target application against the vulnerabilities could last a long time until finished, after the recording process was stopped. Check the status of the test run periodically to determine if the FAST security tests are completed.

You could go back to the list of FAST integration's steps if necessary.

results matching ""

    No results matching ""