Shipeasy
APIOperations

Confirm a suspected regression

Confirm a suspect: the item goes onto the trail with source post_merge and the suspect's evidence is kept. A person's call — the restricted ops key cannot…

Confirm a suspect: the item goes onto the trail with source post_merge and the suspect's evidence is kept. A person's call — the restricted ops key cannot confirm.

POST
/api/admin/trails/{handle}/suspects/{suspectId}/confirm

Authorization

bearerSdkKey
AuthorizationBearer <token>

Pass an admin SDK key as Authorization: Bearer sdk_admin_…. Mint via POST /api/admin/keys with type: "admin".

In: header

Path Parameters

handle*string

The trail's handle (T-12) or its id.

Match^(?:T-[0-9]+|[0-9a-fA-F-]{32,36})$
Length1 <= length <= 64
suspectId*string

The suspect id (from trails get).

Length1 <= length <= 128

Header Parameters

X-Project-Id?string

Project the request operates on. Optional — defaults to the project the SDK key belongs to; pass it only to scope a multi-project key (the generated client sets it once from its configuration, so per-call callers never thread it).

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://shipeasy.ai/api/admin/trails/string/suspects/string/confirm"
{
  "id": "string",
  "item": {
    "id": "string",
    "number": 0,
    "type": "bug",
    "title": "string",
    "status": "open"
  },
  "confidence": "high",
  "evidence": "string",
  "status": "pending",
  "attributedBy": "string",
  "source": "post_merge",
  "createdAt": "string"
}
{
  "error": "Missing or invalid admin SDK key.",
  "code": "UNAUTHORIZED"
}

{
  "error": "Key is valid but not allowed to act on this project.",
  "code": "FORBIDDEN"
}

{
  "error": "The resource does not exist or is not visible to the caller.",
  "code": "NOT_FOUND"
}

{
  "error": "A resource with this name already exists in the project.",
  "code": "ALREADY_EXISTS"
}

Was this page helpful?