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

# List delivery attempts

> Paginated append-only transport history, without secrets or receiver bodies.



## OpenAPI

````yaml /openapi.yaml get /v0/deliveries/{delivery_id}/attempts
openapi: 3.1.0
info:
  title: Quivr V2 public text foundation contract
  version: 0.0.0-draft
  description: >-
    THE-543 and THE-547 evaluation contracts; endpoint implementations are
    separate work. Matching criterion is plugin-owned and deferred. One
    configured webhook destination, immutable Matches, independent at-least-once
    Delivery and reference-only notifications. OpenAPI is authoritative for
    transport shapes. THE-640 adds text search and asynchronous Corpus
    projection rebuild initiation.
servers: []
security:
  - ApiKey: []
paths:
  /v0/deliveries/{delivery_id}/attempts:
    get:
      tags:
        - Deliveries
      summary: List delivery attempts
      description: >-
        Paginated append-only transport history, without secrets or receiver
        bodies.
      operationId: listDeliveryAttempts
      parameters:
        - name: delivery_id
          in: path
          required: true
          schema:
            type: string
            minLength: 1
        - name: page_cursor
          in: query
          schema:
            type: string
            minLength: 1
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 100
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeliveryAttemptPage'
        default:
          description: >-
            Structured error. Existing /v0 authentication, scope, pagination and
            idempotency semantics apply.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    DeliveryAttemptPage:
      type: object
      additionalProperties: false
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/DeliveryAttempt'
        next_page_cursor:
          type: string
          minLength: 1
      required:
        - items
    Error:
      type: object
      additionalProperties: false
      properties:
        code:
          type: string
          minLength: 1
        message:
          type: string
          minLength: 1
        retryable:
          type: boolean
        field:
          type: string
          minLength: 1
          description: >-
            JSON Pointer (RFC 6901) to the request member that caused a 422,
            when known (for example /config/url or /credential/secret/token on
            connector commands).
        resync_url:
          type: string
          format: uri-reference
      required:
        - code
        - message
        - retryable
    DeliveryAttempt:
      type: object
      additionalProperties: false
      properties:
        attempt_id:
          type: string
          minLength: 1
        delivery_id:
          type: string
          minLength: 1
        number:
          type: integer
          minimum: 1
        outcome:
          type: string
          enum:
            - in_flight
            - acknowledged
            - retryable_error
            - permanent_error
            - unknown
        http_status:
          type: integer
          minimum: 100
          maximum: 599
        error:
          $ref: '#/components/schemas/Error'
      required:
        - attempt_id
        - delivery_id
        - number
        - outcome
      description: >-
        Read view of append-only admission/outcome facts. Unknown network result
        can be retried with the same event ID; no response body, signature or
        signing key is exposed.
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      description: >-
        API key, not necessarily a JWT. Server derives Organization, permitted
        actions and Corpus scope; every resource access is authorized.

````