All endpoints require
Authorization: Bearer <token>.https://your-api-domain.com/api/v1/problems
Create a problem
POST /
string
required
Short title for the problem (e.g.
"Intermittent database connection timeouts under load").string
required
Full description of the known issue and its observable symptoms.
string
Known or suspected root cause. Can be updated as investigation progresses.
string
Temporary mitigation to reduce impact while the root cause is being addressed.
string
The affected service or team area.
string
Priority:
LOW, MEDIUM, HIGH, or CRITICAL.IDs of incidents caused by or related to this problem.
string
Email of the engineer responsible for resolving the problem.
List problems
Returns a paginated list of problem records ordered by creation date descending.GET /
number
default:"1"
Page number.
number
default:"20"
Items per page (max 100).
string
Filter by status:
OPEN, IN_PROGRESS, KNOWN_ERROR, or RESOLVED.string
Filter by priority:
LOW, MEDIUM, HIGH, or CRITICAL.Get a problem
GET /:id
string
required
The problem ID.
Update a problem
Accepts the same fields asPOST /. Only provided fields are updated. Use this endpoint to progress status, document the root cause once confirmed, or link additional related incidents.
PUT /:id
string
required
The problem ID.
cURL
Delete a problem
DELETE /:id
string
required
The problem ID to delete.
Problems with status
RESOLVED are retained for historical analysis. Deletion is irreversible — use RESOLVED status to close out a problem without losing the record or its linked incidents.