Skip to main content
POST
Create alert configuration

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Alert configuration

Creates a new alert configuration, or updates an existing one when id is given.

The alert filters can be given in one of two ways, but never both:

  • config: a structured filter object for the given noti_type. Fetch the available filter fields per alert type from GET /api/alerts/filters.
  • input: a DSL expression such as add @energy where calls and volume > 100. Fetch the DSL grammar from GET /api/alerts/query/grammar. The noti_type field is required for DSL expressions.
config
The configuration of an alert. · object
required

An alert configuration, there is no fixed schema for this as each alert will have a different configuration.

Example:
name
string
required
Example:

"Chain OI Chg: TGT241122C00177500"

noti_type
string
required
Example:

"chain_oi_change"

id
string<uuid>

When given, updates the existing alert configuration with this id instead of creating a new one.

input
string

A DSL expression describing the alert filters. Use instead of config for complex filter expressions. See the DSL grammar endpoint for the syntax.

Example:

"where calls and volume > 100 and premium > 10000"

status
enum<string>
Available options:
active,
rate_limit,
paused
Example:

"active"

Response

The created or updated alert configuration

The created or updated alert configuration

data
object
required
Last modified on September 29, 2026