List Traffic Policies
List the traffic policies attached to an endpoint. A traffic policy is a named container for one or more rules that the platform's edge runs against requests passing through the endpoint — IP allow-lists, rate limits, header injection, response caching, custom redirects, JWT validation, etc.
Policies are evaluated in priority order (lowest first). Within a policy, rules are scoped to a phase (TCP-connect, UDP-connect, HTTP-request, HTTP-response). The first rule whose expression matches fires; subsequent rules in the same phase are skipped per the standard chained-evaluation model.
Path parameters
uuid from /endpoints.Response (200 OK)
An object with a policies array. Each policy carries its full rules array (populated server-side for every policy in the list):
{policy_uuid} in the policy and rule routes.false skips this policy at evaluation time without deleting it.uuid, policy_uuid, phase, rule_type, name, expression, config, priority, enabled. See GET .../policies/{policy_uuid} for the per-rule field detail. A verify-webhook or jwt-validation rule's config.secret is write-only: a saved secret reads "****", never the value (an empty one stays empty). To keep it, send **** back on a rule update.Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.