Retrieve most time-consuming API endpoints

Use this API to retrieve latency metrics for the most time-consuming API endpoints in a Reltio tenant. The response includes execution times, operation types, and compute usage by day.

HTTP method and endpoint

Use the following HTTP method and endpoint path to submit the request for retrieving the most time-consuming APIs by execution time.

POST /statistics-reporting/{tenantId}/API/getMostTimeConsumingApis

Replace {tenantId} with the ID of the target tenant.

Request headers

The following request headers must be included.


Header	Value	Required
`Content-Type`	`application/json`	Yes
`Authorization`	`Bearer {access_token}`	Yes

Request body

The following table describes the request body parameters, including accepted values and defaults.


Parameter	Type	Required	Description	Accepted values / Default
`from` ⁽¹⁾	Long	Yes	Start time in epoch milliseconds	—
`to` ⁽¹⁾	Long	Yes	End time in epoch milliseconds	—
`env`	String	Yes	Target environment	Example: `prod`, `qa`, `dev` Default: none
`queryTypes`	Array	No	Filters by query type	`Read`, `Write`, `Search`, `Merge`, `Graphs` Default: all
`httpMethods`	Array	No	Filters by HTTP methods	Example: `POST`, `GET` Default: all methods
`apiEndPoints`	Array	No	Filters by API paths	Example: `/api/{tenantId}/entities` Default: all
`users`	Array	No	Filters by user email addresses	Example: `user1@example.com` Default: all users
Note: The time range defined by the `from` and `to` values must not exceed one month. If the specified range exceeds the allowed limit, the API returns an HTTP `416 Range Not Satisfiable` error with the following response: `{ "errors": [ { "message": "Invalid time range." } ] }`

Example request

Use the following example to see how a complete request is structured with headers and a JSON body.

curl -X POST https://{baseUrl}/statistics-reporting/{tenantId}/API/getMostTimeConsumingApis \
  -H "Authorization: Bearer YOUR_BEARER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "from": 1720867200000,
    "to": 1721016000000,
    "env": "prod",
    "httpMethods": ["POST"],
    "apiEndPoints": ["/api/{tenantId}/entities/_search"],
    "users": ["user1@example.com"]
  }'

Response fields

The following table describes the fields returned in the response body.


Field	Type	Description
`day`	Long	Timestamp in milliseconds for the day the data represents
`operationType`	String	Operation type (`SYNC` or `ASYNC`)
`httpMethod`	String	HTTP method used (e.g., `GET`, `POST`)
`endPoint`	String	API endpoint path that was called
`execTime`	Integer	Execution time in milliseconds
`execTimeMinutes`	String	Execution time formatted as `minutes:seconds.milliseconds`
`rcu`	Float	Reltio Compute Unit (RCU) value used for quota tracking and billing

Example response

The following example shows a response with multiple API calls, their execution times, and compute usage per day.

[
  {
    "day": 1704867200000,
    "operationType": "SYNC",
    "httpMethod": "POST",
    "endPoint": "/api/tenant123/entities/_search",
    "execTime": 4893,
    "execTimeMinutes": "00:04.893",
    "rcu": 12.4
  },
  {
    "day": 1703980800000,
    "operationType": "ASYNC",
    "httpMethod": "POST",
    "endPoint": "/api/tenant123/entities/_findConnected",
    "execTime": 3745,
    "execTimeMinutes": "00:03.745",
    "rcu": 10.4
  },
  {
    "day": 1703894400000,
    "operationType": "SYNC",
    "httpMethod": "GET",
    "endPoint": "/api/tenant123/entities/{id}/_tree",
    "execTime": 2973,
    "execTimeMinutes": "00:02.973",
    "rcu": 8.4
  }
]

Unify and manage your data