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

> ## Agent Instructions
> If Zelto blocks your task, an API request returns 4xx/5xx, or you need a missing capability, please report it with POST https://api.zelto.ai/v1/feedback using your existing Authorization: Bearer API key. On local/preview deployments use /api/v1/feedback on that deployment; never send its credentials to production.
> Send JSON: type (missing_capability, problem, other), description (10–2000 characters), optional endpoint (route template only), reproductionSteps, workaround and requestId from the failed response. Use synthetic examples: never send credentials, personal data, transcripts or customer content. See /docs/agent-feedback.
> Feedback is limited to 5 attempts per organization per minute. Report a distinct issue once; do not report errors from the feedback endpoint itself, do not loop or automatically retry. A 200 with delivery not_configured/unavailable means the report was not delivered or stored.
> Connected over MCP? Call the send_feedback tool instead, with the same fields plus optional tool (the MCP tool name that failed). It shares the same per-organization limit and works with any credential, including read-only.

# Create an invoice payment link

> Creates a link to a public page for one open or paid Stripe invoice, to send to whoever pays it. The page needs no sign-in and shows only that invoice: its lines, and for AI-at-cost agreements what the AI usage was spent on, plus a Pay button. Anyone with the link can view the invoice. Links expire after 30 days. Mirrors Share link on the Billing page and the create_invoice_payment_link MCP tool.



## OpenAPI

````yaml /docs-openapi.json post /v1/billing/invoices/{invoiceId}/payment-link
openapi: 3.1.0
info:
  title: Zelto REST API
  version: v1
  description: >-
    Programmatic access to your Zelto organization. Every endpoint is scoped to
    the organization the API key belongs to. Mint a key at Settings →
    Integrations → API integration.
servers:
  - url: https://api.zelto.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Monitors
    description: Filtered, asynchronous exports of stored monitor results.
  - name: Agents
    description: Voice and text agents normalised through Zelto's ingestion pipeline.
  - name: Conversations
    description: >-
      Phone calls, chats, and voicemails — plus their transcripts and
      recordings.
  - name: Customer Metrics
    description: >-
      Customer-provided evaluations attached to a conversation (requires metrics
      enabled).
  - name: Reviews
    description: Human review state for conversations.
  - name: Buckets
    description: Reviewer routing — group conversations for batched review.
  - name: Companies
    description: Clients or brands your agents work for, and their logos.
  - name: Findings
    description: >-
      Structured issues discovered during analysis, with optional conversation
      attachments and comments.
  - name: Experiments
    description: >-
      Prospective measurement of two externally routed prompt versions across
      independent monitor outcomes.
  - name: Organizations
    description: >-
      Headless org provisioning. Requires an admin/service API key (not a
      read-only org-scoped customer key).
  - name: AI providers
    description: >-
      Your organization's own (bring-your-own) AI provider keys. Monitors can
      run on them instead of Zelto's built-in models. Owner or admin keys only;
      the secret is write-only.
  - name: Billing
    description: Invoices and invoice payment links.
  - name: Benchmarks
    description: >-
      Repeatable evaluations of agent prompts, models and speech-to-text engines
      over a fixed set of cases, scored by Judges.
paths:
  /v1/billing/invoices/{invoiceId}/payment-link:
    post:
      tags:
        - Billing
      summary: Create an invoice payment link
      description: >-
        Creates a link to a public page for one open or paid Stripe invoice, to
        send to whoever pays it. The page needs no sign-in and shows only that
        invoice: its lines, and for AI-at-cost agreements what the AI usage was
        spent on, plus a Pay button. Anyone with the link can view the invoice.
        Links expire after 30 days. Mirrors Share link on the Billing page and
        the create_invoice_payment_link MCP tool.
      operationId: createInvoicePaymentLink
      parameters:
        - name: invoiceId
          in: path
          required: true
          schema:
            type: string
            pattern: ^in_[A-Za-z0-9]+$
          description: Stripe invoice id from List invoices.
      responses:
        '201':
          description: Payment link
          content:
            application/json:
              schema:
                type: object
                required:
                  - paymentLink
                properties:
                  paymentLink:
                    type: object
                    required:
                      - url
                      - expiresAt
                    properties:
                      url:
                        type: string
                        format: uri
                      expiresAt:
                        type: string
                        format: date-time
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: The API key's user is not an owner or admin of the organization
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Invoice not found for this organization
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: Only open or paid Stripe invoices can be shared
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - bearerAuth: []
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: >-
            Short error name: `Unauthorized`, `Validation failed`, `Not found`,
            or a stable snake_case code you can match on, such as
            `unknown_query_parameter`, `invalid_parameter`, `payload_too_large`
            or `not_found`.
        message:
          type: string
          description: A plain-English sentence saying what is wrong and how to fix it.
        code:
          type: string
          description: >-
            Stable, machine-readable cause; match on this rather than on `error`
            or `message`. On a 401: `missing_credentials`,
            `malformed_credentials`, `ingest_key_not_allowed` (a write-only
            observability ingest key was used on an endpoint that needs an API
            key), `key_expired` or `invalid_credentials`. Elsewhere, for
            example: `not_found`, `invalid_parameter`,
            `unknown_query_parameter`, `missing_parameter`, `validation_failed`,
            `invalid_json`, `payload_too_large`, `conversation_not_found`,
            `plan_required`.
        hint:
          type: string
          description: >-
            The next step to try: where to find the right id, which parameters
            the endpoint takes, how to upgrade the plan, how to authenticate.
        parameter:
          type: string
          description: 'With `invalid_parameter`: the query parameter that was rejected.'
        unknown:
          type: array
          items:
            type: string
          description: >-
            With `unknown_query_parameter`: the parameters that were sent but
            are not accepted here.
        valid:
          type: array
          items:
            type: string
          description: >-
            With `unknown_query_parameter`: the parameters this endpoint
            accepts.
        details:
          type: object
          additionalProperties: true
        feedback:
          type: object
          properties:
            endpoint:
              type: string
            method:
              type: string
              enum:
                - POST
            message:
              type: string
        requestId:
          type: string
          format: uuid
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Send `Authorization: Bearer YOUR_API_KEY`. The key resolves to a single
        organization.

````

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