List built prehandlers
Returns all prehandlers in their fully evaluated (built) runtime form, sorted by execution order. Built prehandlers have all evaluatable fields resolved and reflect the current live state of the pipeline. Use this when you need the effective script and condition values rather than the source definitions.
Authorizations
Response
Successful response
Evaluated actions executed when the prehandler conditions match.
Actions executed when the prehandler conditions match.
- EXPRESSION
- JAVASCRIPT_V1
- MAP_DATA_ATTRIBUTES
- SET_DATA
- SET_SANDBOX
Evaluated 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 evaluated prehandler description.
Whether the built prehandler is active in the event-processing pipeline.
Unique identifier for the prehandler.
Evaluated prehandler name.
Execution order for the built prehandler.
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"
