Query Events

Search, filter, and browse Vision Events in the dashboard and via the API

Query and Filter Events

Find specific events using filters in the Vision Events dashboard or query them programmatically via the REST API.

Browse Events in the Dashboard

Select a Use Case

From the Vision Events page, click on a Use Case to view its events. Events are displayed in reverse chronological order.

Filter Events

Use the filter controls at the top of the events list to narrow results by:

• Date range — start and end timestamps

• Event type — quality_check, inventory_count, safety_alert, custom, operator_feedback

• Device — filter by device ID

• Stream — filter by stream or camera ID

• Workflow — filter by the workflow that generated events

• Detection — filter by a detected object class, with an optional confidence threshold

• Feedback status — correct, incorrect, inconclusive, or no feedback

• Custom metadata — filter by any custom metadata field and value

• Warnings — show only events that had ingestion warnings

You can also click on values in the event detail sidebar (such as device ID, stream, quality check result, or custom metadata values) to quickly add them as filters.

Filter chips are editable -- click on any active filter chip to modify its value or operator without having to remove and re-add it.

When filters are applied, a total count of matching events is displayed at the top of the results list. This count updates independently of the event list, so you can see how many events match your filters even while events are still loading.

View Event Details

Click on any event in the list to view its full details:

• The source image and any output images

• All source metadata (device, stream, workflow)

• Object detections, classifications, and segmentations with their confidence scores

• Event-type-specific data (ex: pass/fail result, item count, alert severity)

• Custom metadata key-value pairs

Draw Detections

When an event contains prediction data (object detections, instance segmentations, or keypoints), a "Draw Detections" checkbox appears above the image. Enable it to overlay bounding boxes, segmentation polygons, and labels with confidence scores on top of the source image.

This is useful when your pipeline only persists the original input image and you want to visualize what the model detected without storing a separate output image.

The checkbox is hidden when viewing a distinct output image, since those already have detections rendered.

Query Events via the API

The query endpoint supports the same filters as the dashboard, plus cursor-based pagination. For the full list of parameters and response fields, see the Vision Events API Reference.

Basic Query

curl -X POST "https://api.roboflow.com/vision-events/query" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "useCaseId": "assembly-line-qa",
    "startTime": "2026-03-01T00:00:00Z",
    "endTime": "2026-03-31T23:59:59Z",
    "limit": 25
  }'

Response:

{
  "events": [
    {
      "eventId": "evt-789ghi",
      "eventType": "quality_check",
      "timestamp": "2026-03-30T14:30:00.000Z",
      "deviceId": "factory-cam-01",
      "streamId": "line-3",
      "images": [],
      "eventData": { "result": "fail" },
      "customMetadata": {
        "line_id": "line-3",
        "shift": "morning",
        "part_number": "PN-4421"
      }
    }
  ],
  "nextCursor": "eyJ0cyI6IjIwMjYtMDMtMzAifQ==",
  "hasMore": true
}

Pagination

Results are paginated using a cursor. If the response includes a nextCursor value and hasMore is true, pass the cursor in your next request to retrieve the next page:

curl -X POST "https://api.roboflow.com/vision-events/query" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "useCaseId": "assembly-line-qa",
    "limit": 25,
    "cursor": "eyJ0cyI6IjIwMjYtMDMtMzAifQ=="
  }'

Continue until hasMore is false.

Filter by Event Type

Query a single event type:

{
  "useCaseId": "assembly-line-qa",
  "eventType": "quality_check"
}

Or multiple event types (max 20):

{
  "useCaseId": "assembly-line-qa",
  "eventTypes": ["quality_check", "operator_feedback"]
}

Filter by Feedback Status

Use feedbackStatus to find events based on whether operators have reviewed them and how they were rated:

{
  "useCaseId": "assembly-line-qa",
  "feedbackStatus": ["incorrect", "none"]
}

Valid values: correct, incorrect, inconclusive, none. Use none to find events that haven't been reviewed yet.

Filter by Custom Metadata

Use customMetadataFilters to filter events by your own metadata fields:

{
  "useCaseId": "assembly-line-qa",
  "customMetadataFilters": [
    { "key": "line_id", "operator": "eq", "value": "line-3" },
    { "key": "shift", "operator": "eq", "value": "morning" }
  ]
}