> ## 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.

# Relay connector challenge

> Public webhook route of one Connector Instance whose kind declares the push mode; the address is its webhook_url. There is no API key; the connector plugin verifies the request (a signature, a challenge) with the Deposited Credential. A GET is typically a source's verification challenge, relayed to the plugin like a delivery.



## OpenAPI

````yaml /openapi.yaml get /v0/connector-webhooks/{connector_id}
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/connector-webhooks/{connector_id}:
    get:
      tags:
        - Connector webhooks
      summary: Relay connector challenge
      description: >-
        Public webhook route of one Connector Instance whose kind declares the
        push mode; the address is its webhook_url. There is no API key; the
        connector plugin verifies the request (a signature, a challenge) with
        the Deposited Credential. A GET is typically a source's verification
        challenge, relayed to the plugin like a delivery.
      operationId: relayConnectorChallenge
      parameters:
        - name: connector_id
          in: path
          required: true
          schema:
            type: string
            minLength: 1
      responses:
        '500':
          description: >-
            The delivery cannot be processed (the plugin reported an access or
            source error), shown in health.push.
        '503':
          description: >-
            Temporarily unavailable (the plugin is unreachable or ingestion is
            down); retry after Retry-After seconds. Polling catches up
            meanwhile.
        2XX:
          description: >-
            The connector plugin accepted the delivery; its items were ingested
            before this answer. The body and content type are the plugin's
            answer to the source (for example a challenge response).
        4XX:
          description: >-
            The connector plugin refused the delivery (for example a bad
            signature), with its own body; nothing changed. 404 names no enabled
            instance of a kind that declares push; 413 a body over 1 MiB.
      security: []
components:
  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.

````