# Get Query Result Get the Query Result details for a specific Query Result ID. This endpoint is used to fetch the results of a query that had previously been created. It is recommended to follow the Location header included in the Create Query Result output, but the URL can also be constructed manually with the <query-result-id>. Endpoint: GET /1/query_results/{datasetSlug}/{queryResultId} Version: 1.0.0 Security: configuration_key ## Path parameters: - `datasetSlug` (string, required) The dataset slug or use for endpoints that support environment-wide operations. - `queryResultId` (string, required) The unique identifier (ID) of the query result. ## Response 200 fields (application/json): - `query` (object) - `query.id` (string) - `query.breakdowns` (array) the columns by which to break events down into groups - `query.calculations` (array) the calculations to return as a time series and summary table - `query.calculations.op` (string, required) Enum: "COUNT", "CONCURRENCY", "SUM", "AVG", "COUNT_DISTINCT", "HEATMAP", "MAX", "MIN", "P001", "P01", "P05", "P10", "P20", "P25", "P50", "P75", "P80", "P90", "P95", "P99", "P999", "RATE_AVG", "RATE_SUM", "RATE_MAX" - `query.calculations.column` (null,string) the name of the column - `query.filters` (array) the filters with which to restrict the considered events - `query.filters.column` (null,string) - `query.filters.value` (any) - `query.filter_combination` (string) set to "OR" to match ANY filter in the filter list Enum: "AND", "OR" - `query.granularity` (integer) The time resolution of the query's graph, in seconds. Given a query time range T, valid values (T/1000...T/1). If left blank, granularity may be set to a sub-second value for queries with short time ranges. - `query.orders` (array) The terms on which to order the query results. Each term must appear in either the field or the field. - `query.orders.order` (string) Enum: "ascending", "descending" - `query.limit` (integer) The maximum number of unique groups returned in 'results'. Aggregating many unique groups across a large time range is computationally expensive, and too high a limit with too many unique groups may cause queries to fail completely. Limiting the results to only the needed values can significantly speed up queries. The normal allowed maximum value when creating a query is 1_000. When running 'disable_series' queries, this can be overridden to be up to 10_000, so the maximum value returned from the API when fetching a query may be up to 10_000. - `query.start_time` (integer) Absolute start time of query, in seconds since UNIX epoch. Must be <= . - `query.end_time` (integer) Absolute end time of query, in seconds since UNIX epoch. - `query.time_range` (integer) Time range of query in seconds. Can be used with either (seconds after ), (seconds before ), or without either (seconds before now). - `query.havings` (array) The Having clause allows you to filter on the results table. This operation is distinct from the Where clause, which filters the underlying events. Order By allows you to order the results, and Having filters them. - `query.havings.calculate_op` (string, required) Enum: "COUNT", "CONCURRENCY", "SUM", "AVG", "COUNT_DISTINCT", "MAX", "MIN", "P001", "P01", "P05", "P10", "P20", "P25", "P50", "P75", "P80", "P90", "P95", "P99", "P999", "RATE_AVG", "RATE_SUM", "RATE_MAX" - `query.havings.column` (null,string) The name of the column to filter against - `query.calculated_fields` (array) Computed properties that are calculated by a formula. - `query.calculated_fields.name` (string, required) The field name - `query.calculated_fields.expression` (string, required) The formula for your Calculated Field. To learn more about syntax and available functions, and to explore some example formulas, visit [Calculated Field Formula Reference](https://docs.honeycomb.io/reference/derived-column-formula/). - `id` (string) The unique identifier (ID) of a Query Result Example: "sGUnkBHgRFN" - `complete` (boolean) Indicates if the query results are available yet or not. For example, is the query still being processed or complete? Example: true - `data` (object) An object containing the query result data - `data.series` (array) Timeseries data from the query result (equivalent to the graph data in the Honeycomb UI) - `data.series.time` (string) Example: "2021-04-09T14:16:00Z" - `data.series.data` (object) - `data.results` (array) Query results data (equivalent to the Overview in the Honeycomb UI below the graph) - `data.total_by_aggregate` (object) An object containing each aggregate in the query mapped to its total value across all groups. Aggregate values do not respect any Having clauses included in a query. Only available if query was run with set to . - `data.total_by_aggregate_series` (array) Timeseries data showing the total value of each aggregate returned in across the time range. Aggregate values returned do not respect any Having clauses included in a query. Only available if both and are set to . - `data.other_by_aggregate` (object) An object containing each aggregate in the query mapped to its value for the groups not included in the query limit. Aggregate values do not respect any Having clauses included in a query. Only available if query was run with set to . - `links` (object) An object containing UI links to the query result and query result graph - `links.query_url` (string) A link to the query result in the Honeycomb UI Example: "https://ui.honeycomb.io/myteam/datasets/test-via-curl/result/HprJhV1fYy" - `links.graph_image_url` (string) A direct link to the graph image from the query result Example: "https://ui.honeycomb.io/myteam/datasets/test-via-curl/result/HprJhV1fYy/snapshot" ## Response 404 fields (application/json): - `error` (string) ## Response default fields (application/json): - `error` (string)