---
title: "Update regression testing item statuses in batch"
method: PUT
path: "/app/{appId}/regressionItems/batch"
tags: ["regressionTesting"]
---

# Update regression testing item statuses in batch

`PUT /app/{appId}/regressionItems/batch`

## Request

- Base URL: `https://api.runway.team`
- URL: `https://api.runway.team/app/{appId}/regressionItems/batch`
- Auth: API key in header `X-API-Key`

Sets the status of up to 200 existing regression testing items in one request, for example after re-running a test suite against a new build. Identify items by the `id` returned when they were created. Each item is validated independently: invalid items are reported in `errors` and the rest are still updated. Only supported for apps using FlightPaths. Sending an item's current status again is accepted and refreshes who set it and when.

## Path parameters

- `appId` string, required

## Request body

- UpdateRegressionItemsBatchRequestBody
  - `items` UpdateRegressionItemStatusRequestItem[], required: The regression testing items to update, at most 200. Each id may appear once.
    - `id` string, required: The id of the regression testing item, as returned when it was created
    - `status` 'approved' | 'rejected' | 'inProgress' | 'blocked' | 'passed' | 'failed', required: All possible statuses for a checklist item

## Response `200`

A batch checklist item status update response

- BatchUpdateChecklistItemStatusesResponse
  - `requestedCount` integer, required: The number of items requested in the batch
  - `updatedCount` integer, required: The number of items successfully updated
  - `errorCount` integer, required: The number of items that failed to update
  - `updatedItems` ChecklistItemEntity[], required: The items that were updated, in request order
    - `id` string, required: The identifier of the checklist item
    - `title` string, required: The title of the checklist item
    - `description` string: The description of the checklist item. Accepts markdown.
    - `approverGroups` UserGroup[], required: The list of user groups that can approve this checklist item. Custom groups can be included as well.
    - `releaseType` 'all' | 'hotfixOnly' | 'rollbackOnly' | 'allExceptHotfix', required: The type of release this checklist item will appear on
    - `notifyEnabled` boolean, required: Whether the checklist item will notify on Slack when its status changes
    - `statuses` ChecklistItemStatusType[], required: The list of possible checklist item status types for this checklist item. A subset of all possible ChecklistItemStatusType values
    - `releaseStepType` string: The release step that the checklist item appears on. Will be `null` if the placement of the item is not `binary`. Can either be of type ReleaseStepType, or a step's Step ID can be sent instead
    - `stepId` unknown
    - `oneOffForVersion` string: If the checklist item only applies for a single release version, this field will contain the version string for that version
    - `status` ChecklistItemStatus: The status of a checklist item
      - `status` 'approved' | 'rejected' | 'inProgress' | 'blocked' | 'passed' | 'failed', required: All possible statuses for a checklist item
      - `createdBy` string, required: The userId (email) of the user that created the checklist item
      - `createdAt` string, date-time, required: The date and time the checklist item was created
    - `placement` 'stepChecklist' | 'approvals' | 'regressionTesting', required: The placement of a given checklist item
    - `comment` ChecklistItemComment: A comment on a checklist item
      - `createdAt` string, date-time
      - `createdBy` string: The user id (email) of the user that added the comment
      - `comment` string: The comment string. Can be markdown.
  - `errors` BatchChecklistItemIdError[], required: Per-item failures, in request order
    - `index` integer, required: The zero-based index of the item in the request payload
    - `id` string: The id of the item that failed, when provided
    - `error` string, required: The error message for the failed item

## Other responses

- `400`: Bad request response
- `404`: Resource not found response

---

[API](https://skmtc.dev/runway/apis/runway-rest-api.md) - [All operations](https://skmtc.dev/runway/apis/runway-rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/runway/apis/runway-rest-api/revisions/081109863a9a?raw)
