Get user latency
GET https://hub2.trylevel2.com/broker/get_broker_user_latency_by_emailRetrieves latency information for trades triggered by a user, identified by their email address.
Request:
QUERY PARAMETERS
QUERY PARAMETERS
Required & Optional Parameters
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| user_email | email | Required | The registered email address of the user whose records are being fetched. |
| limit | integer | Optional | The maximum number of latency records to retrieve. |
Parameter Constraints
When setting the limit parameter, adhere to the following system boundaries:
- Minimum Value:
1 - Maximum Value:
100 - Default Value:
30(if no value is provided)
Responces:
Successful response with latency records 200
SCHEMA
SCHEMA
Records Object Array
Each entry in the records array represents a single execution event.
| Parameter | Type | Description | Example |
|---|---|---|---|
| trade_id | string | The unique identifier for the specific trade executed. | t789 |
| latency_ms | integer | The execution delay measured in milliseconds. | 150 |
| timestamp | date-time | The ISO 8601 timestamp of when the latency was recorded. | 2025-10-17T16:00:00Z |
Summary Data
| Parameter | Type | Description | Example |
|---|---|---|---|
| total | integer | The total count of latency records available for the requested period. | 50 |
EXAMPLE
EXAMPLE
{
"records": [
{
"trade_id": "t789",
"latency_ms": 150,
"timestamp": "2025-10-17T16:00:00Z"
}
],
"total": 50
}Responces:
Internal Server Error 500
SCHEMA
SCHEMA
| Parameter | Type | Description |
|---|---|---|
| error | string | A descriptive message detailing the specific issue encountered. |
EXAMPLE
EXAMPLE
{
"error": "An unexpected error occurred"
}Last updated on