POST alternative for GET /pipelines. Use when URL length limits are exceeded (e.g., many filter values). Supports both query parameters and request body. Body parameters take precedence over query parameters.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Sort field. Can be a DB field (name, created_at) or a metric field (latency, status, recordsLag)
Sort direction: 'asc' (ascending) or 'desc' (descending)
Filter by pipeline status. Comma-separated for multiple statuses (e.g., 'Active', 'Active,Paused'). Valid statuses: Active, Broken, Paused, Stopped, Starting, Unassigned, Unknown
Filter by pipeline latency in milliseconds. Format: 'operator:value' (e.g., 'gt:1000', 'lt:500'). Valid operators: gt (>), lt (<), gte (>=), lte (<=), eq (=), ne (!=)
Filter by pipeline lag (records behind). Format: 'operator:value' (e.g., 'gt:100', 'lt:50'). Valid operators: gt (>), lt (<), gte (>=), lte (<=), eq (=), ne (!=)
true, false Body model for POST /pipelines/search requests.
Supports large lists of filter values that would exceed URL length limits when using GET. Body parameters take precedence over query parameters when both are provided.
List of tag IDs (as array) or comma-separated string. Body takes precedence over query params.
List of source IDs (as array) or comma-separated string. Body takes precedence over query params.
List of destination IDs (as array) or comma-separated string. Body takes precedence over query params.
List of statuses (as array) or comma-separated string. Body takes precedence over query params.