Skip to main content
GET
Permission Required: project:read-runs
Retrieve all bugs detected during a specific run.

Path Parameters

runId
string
required
The multiplayer run ID (12 lowercase alphanumeric characters)

Response

data
BugOccurrence[]
required
Array of bug occurrences found during the run
pagination
object
required
Pagination metadata (page, page_size, total_count, total_pages). Bug occurrences per run are naturally bounded, so the response always returns the full list in a single page — the envelope is kept to match the shape of other list routes.

Bug Occurrence Object

id
string
required
Unique occurrence ID
bug_id
string
required
Bug identifier (same bug across runs shares this ID)
title
string
required
Short bug title
description
string
required
Detailed description of the bug
category
string
required
Bug category: ui, gameplay, performance, crash, audio, visual
severity
string
required
Severity level: low, medium, high, critical
confidence
string
required
Detection confidence: low, medium, high
reproduction_steps
string
required
Steps to reproduce the bug
player_number
integer
required
Which player encountered the bug (0-indexed)
test_step
integer
required
Test step where bug was detected
turn
integer
required
Agent turn number when detected
detected_at
string
required
ISO 8601 timestamp when bug was detected
details
object
Additional bug-specific details (screenshots, element IDs, etc.)

Severity Levels

Blocks core functionality or causes crashes. Requires immediate attention.
Major feature broken or significantly impaired. Should be fixed before release.
Feature works but with noticeable issues. Should be addressed in normal development cycle.
Minor issues with minimal impact. Can be fixed when convenient.

Aggregate Bugs Across Runs

Here’s an example of fetching bugs from multiple recent runs:

Authorizations

X-Api-Key
string
header
required

API key for authentication

Path Parameters

runId
string
required

The multiplayer run ID

projectId
string
required

The project ID. You can copy it from the project settings page or the project URL in the dashboard.

Response

Successful response

Bugs detected during a multiplayer run. Bug occurrences per run are naturally bounded, so the response always returns the full list in a single page; the pagination envelope is kept to match the shape of other list routes.

data
object[]
required
pagination
object
required