Api Annotation Items List List
GET/POST /api/annotation-items/list/
Admin/Manager view: Team progress tracking with pagination and filtering.
Sophisticated listing endpoint for management dashboard (L from CRUDL).
Permission: Requires annotation_items:read (admin/manager only)
Features:
- Pagination (cursor-based)
- Filtering (source_type, status, etc.)
- Accepts filters via URL params OR POST body
Use cases:
- Management dashboard
- Track team progress
- Filter by status, source_type
- View who's assigned to what
Query Parameters (GET):
- page, page_size: Pagination
- source_type: Filter by source type
- status: Filter by status
Request Body (POST):
{
"filters": {
"source_type": {"operator": "in", "value": ["logs", "threads"]},
"status": {"operator": "", "value": "pending"}
}
}
Response:
{
"count": 150,
"next": "...",
"previous": "...",
"results": [
{
"id": "item_1",
"assignee": {"email": "worker@co.com"},
"status": "pending",
"source_type": "logs",
"created_at": "..."
}
],
"filters_data": {...}
}
Authentication
AuthorizationBearer
JWT access token or Respan API key
Query parameters
page
A page number within the paginated result set.
page_size
Number of results to return per page.
Response
count
results
next
previous
total_count
current_filters
Pydantic model for FilterParamDict. A dictionary that maps metric names to their filter parameters.
Each key is a metric name (str), and each value can be:
- A single MetricFilterParamPydantic (one condition)
- A List[MetricFilterParamPydantic] (multiple conditions for same metric)
- A FilterBundlePydantic (nested filter bundle with connector)
Note: Uses extra=“allow” for dynamic metric name fields. The pydantic_extra annotation tells Pydantic what types to expect for extra fields, and generates typed additionalProperties in JSON Schema.
filters_data