List prehandlers
Returns all prehandlers for the client, sorted by their execution order. Prehandlers are pre-processing hooks that run before the main event-processing pipeline. Each entry includes its script, conditions, and current state (active or archived). Use GET /v6/prehandlers/built to retrieve the evaluated runtime version.
Authorizations
Response
Successful response
Actions executed when the prehandler conditions match.
Actions executed when the prehandler conditions match.
- EXPRESSION
- JAVASCRIPT_V1
- MAP_DATA_ATTRIBUTES
- SET_DATA
- SET_SANDBOX
Conditions that must match before the prehandler actions run.
Conditions that must match before the prehandler actions run.
- BLOCK_MATCH
- DATA_EXISTS
- EVENT_NAME_MATCH
- EXPRESSION
- HTTP_HEADER_MATCH
- JAVASCRIPT_V1
RFC 3339 or RFC 9557 date-time with a numeric UTC offset and an optional IANA time-zone suffix in square brackets. Precision up to milliseconds.
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,3})?(Z|[+-](?:[01][0-9]|2[0-3]):[0-5][0-9])(\[[^\]]+\])?$"2025-10-24T02:00:00-07:00"
Optional build-time expression that resolves to the prehandler description.
Build-time expression that controls whether the prehandler is active.
Unique identifier for the prehandler.
Build-time expression that resolves to the prehandler name.
Build-time expression that controls the prehandler execution order.
Tags used to classify or filter the prehandler.
Tags used to classify or filter the prehandler.
RFC 3339 or RFC 9557 date-time with a numeric UTC offset and an optional IANA time-zone suffix in square brackets. Precision up to milliseconds.
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,3})?(Z|[+-](?:[01][0-9]|2[0-3]):[0-5][0-9])(\[[^\]]+\])?$"2025-10-24T02:00:00-07:00"
