---
title: "Bulk Restore Object Records"
method: POST
path: "/objects/{object_slug}/records/bulk-restore"
tags: ["Objects"]
---

# Bulk Restore Object Records

`POST /objects/{object_slug}/records/bulk-restore`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/objects/{object_slug}/records/bulk-restore`
- Auth: HTTP bearer

Restore each listed record: the inverse of `bulk-archive`.

Same rules as the single restore: a snapshot the current attribute rules reject fails on its own row, under
`failed`, without stopping the others. Needs `objects:write` and the credential's write grant on the object.

## Path parameters

- `object_slug` string, required

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- RecordBulkArchiveRequest: Body of ``POST /{slug}/records/bulk-archive`` and ``.../bulk-restore``: an explicit id list, capped at 500 like the bulk update.
  - `record_ids` string[], required

## Response `200`

Successful Response

- ApiResponseRecordBulkArchiveResponse
  - `data` RecordBulkArchiveResponse, required: ``succeeded`` lists exactly the records this call changed, so a bulk restore of ``succeeded`` is the exact inverse of a bulk archive. ``failed`` uses the bulk-update failure shape; codes: not_found, already_archived (archive), not_archived (restore), locked, invalid_value, unique_conflict, constraint_violation or rejected.
    - `succeeded` string[], required
    - `failed` RecordBulkUpdateFailure[], required
      - `id` string, uuid, required
      - `error` string, required
      - `code` string
      - `attribute_slug` string, nullable
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)