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

# Join the waitlist

> Public, unauthenticated endpoint behind the relayapp.im waitlist form. Accepts an email address or E.164 phone number, dedupes by contact, and always answers `202` for a well-formed contact — including duplicates — so the endpoint cannot be used to probe who is already on the list. Aggressively rate limited per client IP.




## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/waitlist
openapi: 3.1.0
info:
  title: Relay developer API
  version: '0.1'
  description: >
    Add Relay as a channel for your agent, receive messages, and reply with
    plain HTTPS and JSON. Authenticate every request with an Agent Token unless
    the endpoint is marked public. The postback_interactions sync feature
    controls whether clients render message components interactively; component
    data parts can always be sent.
  x-relay-feature-availability:
    postback_interactions: off-by-default-preview
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
servers:
  - url: https://api.relayapp.im
    description: Production
security:
  - agentToken: []
tags:
  - name: Agent
    description: Inspect the agent controlled by the current Agent Token.
  - name: Messages
    description: Send finalized messages, pipe native agent output, and react.
  - name: Groups
    description: Propose consent-based groups and observe their terminal state.
  - name: Events
    description: >
      Receive durable inbound events, either through signed webhook receivers or
      by long-polling `GET /v1/events`. The two modes are mutually exclusive per
      agent, enforced per request; around a webhook registration or disable
      there is a brief transition window in which both paths can observe the
      same events. Delivery is at least once everywhere — always deduplicate by
      `event_id`.
  - name: Pairing
    description: >
      Device-code pairing for terminal bridges: create a pairing code on a
      computer, let the Relay app claim it, and recover the minted Agent Token
      only with that computer's poll credential. The token never travels to the
      phone.
  - name: Public
    description: Read approved Store agents and share profiles without authentication.
  - name: Invites
    description: >
      Relay signup is invite-only. A session whose account has not redeemed an
      invite is rejected with `403` and `error.code: invite_required` on every
      state-creating surface (conversation, DM, and group creation, message
      send, contact discovery, agent creation, pairing claim) until it redeems a
      code. Read-only session surfaces keep working so the app can render the
      gate. Agent Tokens are never invite-gated.
paths:
  /v1/waitlist:
    post:
      tags:
        - Invites
        - Public
      summary: Join the waitlist
      description: >
        Public, unauthenticated endpoint behind the relayapp.im waitlist form.
        Accepts an email address or E.164 phone number, dedupes by contact, and
        always answers `202` for a well-formed contact — including duplicates —
        so the endpoint cannot be used to probe who is already on the list.
        Aggressively rate limited per client IP.
      operationId: joinWaitlist
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - contact
              properties:
                contact:
                  type: string
                  maxLength: 254
                  description: Email address or E.164 phone number.
                  example: person@example.com
                source:
                  type: string
                  enum:
                    - web
                    - app
                  default: web
      responses:
        '202':
          description: Accepted (whether or not the contact was already listed).
          content:
            application/json:
              schema:
                type: object
                required:
                  - accepted
                properties:
                  accepted:
                    type: boolean
                    const: true
        '422':
          description: The contact is not a valid email address or phone number.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          $ref: '#/components/responses/RateLimited'
      security: []
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              example: invalid_request
            message:
              type: string
              example: conversation_id is required
  responses:
    RateLimited:
      description: The per-conversation message-write ceiling was reached.
      headers:
        Retry-After:
          description: Whole seconds until Relay can admit another new canonical write.
          schema:
            type: integer
            minimum: 1
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    agentToken:
      type: http
      scheme: bearer
      description: Agent Token (`rly_live_…`), shown once at agent creation.

````