Latency Testing API
Ddosify Latency Testing API
You can instantly start a geo-targeted latency test or you can create/delete/update a latency test plan to re-use it with Latency API.
You will see the
locationskey in the request body of related API endpoints. The usage of this key let you able to perform latency test for desired locations.
You can target from continent to city by using the below format.
All supported cities in Texas
All supported cities in USA
All supported cities in USA and Paris
All supported cities
All endpoints require the
X-API-KEYheader for authentication. Please check the Get Your API Key section to learn how you can get it.
You'll be charged for 5K Requests for every successful latency test.
API concurrency limit is 5 requests per second for GET endpoints and 2 requests per second for others. You will get
HTTP 429(Concurrency Limit Exceeded) when you reach the concurrency.
Get supported latency locations
Start a latency test. You'll be charged for 5K Requests
Create a new latency test plan
Start a latency test with the plan id. You'll be charged for 5K Requests
Retrieve details of the latency test plan
Get latency test plans
Update the latency test plan
Delete the latency test plan
Get available credit
You can create periodic latency tests with the scheduling mechanism. The scheduler is basically a wrapper over Latency Test Plan to make it periodically runnable with the given configurations.
Interval time between each run. Format: "(digit)(s|m|h)" Examples: "30s" : Runs every 30 seconds "4m" : Runs every 4 minutes "1h" : Runs every 1 hour
Enable/disable logic for the scheduler
The maximum number of run counts for the scheduler. If it is
Latency Test Plan to be used by scheduler
This is a read-only field and is updated by the scheduler every time a test is finished.
intervalvalue is "30s".
At the beginning of each
interval, the Scheduler first checks
is_activeto be sure that the scheduler is active. Then it controls if the number of test runs reached its maximum value by comparing
run_count. If these two checks passed, the scheduler starts a new Latency Test by using the Latency Test Plan.
Be careful about the infinite Schedulers (when
null). They run forever until you stop them.
Create a scheduler
Retrieve details of the scheduler
List all the schedulers
List all the schedulers with Latency Test Plan ID
Get the result of executed latency tests in descending order by date
Update the Scheduler
Delete the Scheduler