Query Count API
Last updated
Last updated
This reference contains information about the e6data application programming interfaces (APIs) for the query history component which provides query count in the response payload. These response payloads are typically in JSON format.
Query Count endpoint: The subdomain would have been provided during the .
Start date: The start_date
parameter is optional and should be specified in UTC. It is expected in the format YYYY-MM-DD HH:MM:SS
(e.g., 2024-05-03 18:30:30
). If not specified, the latest 100 records will be fetched by default.
End date: The end_date
parameter is optional and should be specified in UTC. It is expected in the format YYYY-MM-DD HH:MM:SS
(e.g., 2024-05-03 18:30:30
). If not specified, the current time will be used as the end time.
Authorization through Access Token: The header needs to be passed for authorization purposes in the below JSON format. Refer to the for Access Token.
e6data API calls typically include the following components:
of your e6data account.
from the mentioned workspace.
API Operation type: POST
The request body needs to be passed to identify query history and query count. Query count can be filtered based on -
Workspace name
Run by
Cluster name
Here is a response payload example -