> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reindex a config's records

> Rewrites one page of the config's records into the search index so a newly declared index field becomes filterable. Resume with the cursor from the previous reply. A record the indexer refuses is reported by id and does not stop the page. With `ancestors` instead, reads (`status`), sets (`mark`) or withdraws (`unmark`) the account's folder-ancestors marker; mark and unmark are root and admin only, and mark answers 409 while an index rebuild runs, which lets under_folder answer; the backfill tool marks only after its parity check passes.



## OpenAPI

````yaml /api-reference/endpoint/records/openapi.json post /records/reindex
openapi: 3.1.0
info:
  title: Records API
  version: 1.1.0
  description: >-
    Record configurations (schemas, views, versions) and the records that
    conform to them. Record IDs are server-generated, config IDs are
    client-supplied (`^[a-zA-Z0-9_-]+$`). Configs and records are updated with
    PUT: a config update applies only the fields sent, a record update merges
    `data`. Editing a config schema does not retroactively re-validate existing
    records. Publish a config version to snapshot the stored config; list and
    read versions to see its history.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Record Configs
    description: >-
      Manage record configuration schemas. Each configuration defines the
      structure (fields, types, validation rules) that records must conform to.
  - name: Records
    description: >-
      Manage individual data records. Each record belongs to exactly one
      configuration and its data is validated against that configuration's
      schema.
  - name: Record Config Collections
    description: Groups of record configs.
  - name: Record Config Versions
    description: Published snapshots of a record config.
  - name: Record History
    description: The change history of a record.
  - name: Record Assessment
  - name: Strategy and Simulation
  - name: Record Metrics
paths:
  /records/reindex:
    post:
      tags:
        - Records
      summary: Reindex a config's records
      description: >-
        Rewrites one page of the config's records into the search index so a
        newly declared index field becomes filterable. Resume with the cursor
        from the previous reply. A record the indexer refuses is reported by id
        and does not stop the page. With `ancestors` instead, reads (`status`),
        sets (`mark`) or withdraws (`unmark`) the account's folder-ancestors
        marker; mark and unmark are root and admin only, and mark answers 409
        while an index rebuild runs, which lets under_folder answer; the
        backfill tool marks only after its parity check passes.
      operationId: reindexRecords
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                config_id:
                  type: string
                cursor:
                  type: string
                limit:
                  type: integer
                ancestors:
                  type: string
                  enum:
                    - status
                    - mark
                    - unmark
                  description: >-
                    Read the folder-ancestors marker with pending and failed
                    sweeps, or set or withdraw it (root and admin); config_id is
                    then not required.
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Response'
        '400':
          description: Request refused or invalid
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    Response:
      type: object
      properties:
        status_code:
          type: integer
          description: HTTP status code echoed in the response body.
        body:
          type: object
          description: Response payload.
    ErrorResponse:
      type: object
      properties:
        status_code:
          type: integer
        body:
          type: object
          properties:
            error:
              type: string
              description: Human-readable error message.
      example:
        status_code: 400
        body:
          error: field 'rating' is required
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.