Skip to main content
POST
Resolve data sets

Authorizations

X-BRONTO-API-KEY
string
header
required

Body

application/json
time_range
string
required

Time range to resolve the datasets. Mutually-exclusive with from_ts and to_ts.

Example:

"Last 10 minutes"

where
string

Filter expression used to resolve datasets. At least one of "where" or "from_expr" must be provided.

Example:

"SELECT * WHERE auth_success = 'false' GROUP BY user_id"

from_expr
string

Expression used to filter datasets. At least one of "where" or "from_expr" must be provided.

Example:

"environment = 'production'"

from_ts
integer

The starting time (unix time in milliseconds) for which to resolve the datasets. Must be used together with to_ts. This parameter is incompatible with time_range.

Example:

1709251200000

to_ts
integer

The ending time (unix time in milliseconds) for which to resolve the datasets. Must be used together with from_ts. This parameter is incompatible with time_range.

Example:

1709251200000

match_type
enum<string>

Key matching strategy for dataset resolution: - EXACT: The key must match exactly (case-sensitive). - IEXACT: The key must match exactly (case-insensitive). - SUBSTRING: The key must partially match (case-sensitive). - ISUBSTRING: The key must partially match (case-insensitive).

Available options:
EXACT,
IEXACT,
SUBSTRING,
ISUBSTRING
Example:

"EXACT"

expand_type
enum<string>

Strategy to expand the requested keys for resolution: - DISABLED: No expansion is performed; match only the requested keys. - SYNONYM: Match the requested keys in addition to a number of synonyms and variations of each key. When using this option, the match_type parameter may only be specified as EXACT or IEXACT.

Available options:
DISABLED,
SYNONYM
Example:

"SYNONYM"

Response

Successfully resolved datasets

datasets
object[]
keys
string[]

List of keys used to resolve datasets; the keys specified in the client request, plus any additional keys added by the server if key expansion was enabled