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

# Receipt Proof Bundle

> Download a self-contained proof bundle for offline receipt verification.

Returns a self-contained proof bundle for a receipt event. The bundle includes the signed receipt envelope, Merkle inclusion proof from the transparency log, and the issuer key snapshot at time of issuance.

The bundle can be used for offline verification — no server call required after download.

## Path parameters

<ParamField path="id" type="string" required>
  UUID of the receipt.
</ParamField>

## Response

<ResponseField name="bundle_id" type="string">UUID of the proof bundle.</ResponseField>
<ResponseField name="bundle_version" type="string">Bundle format version (e.g. `receipt-v1`).</ResponseField>
<ResponseField name="receipt" type="object">Signed receipt envelope with `receipt_id`, `receipt_type`, and `signature`.</ResponseField>
<ResponseField name="key" type="object">Issuer key snapshot: `public_key_b64url`, `status`, `compromised_at`.</ResponseField>
<ResponseField name="transparency_log" type="object">Merkle inclusion proof and checkpoint.</ResponseField>
<ResponseField name="bundle_hash_b64url" type="string">SHA-256 hash of the entire bundle.</ResponseField>


## OpenAPI

````yaml mint-openapi.yaml GET /v1/receipts/{id}/proof-bundle
openapi: 3.0.3
info:
  title: Truthlocks API
  description: >
    Truthlocks is a universal verification infrastructure for documents,
    credentials, and digital assets.

    This specification defines the canonical API for interacting with Truthlocks
    services.


    ## Base URLs

    - **Production**: `https://api.truthlocks.com`

    - **Sandbox**: `https://sandbox-api.truthlocks.com`


    ## Authentication

    - **API Keys**: Use `X-API-Key` header for machine-to-machine operations

    - **Bearer Tokens**: Use `Authorization: Bearer <jwt>` for user-initiated
    operations


    ## Tenant Identity

    In production, tenant identity is derived from the authenticated context
    (API key or JWT).

    The `X-Tenant-ID` header is ignored in production to prevent spoofing.
  version: 1.0.0
  contact:
    name: Truthlocks Support
    url: https://truthlocks.com/support
    email: support@truthlocks.com
servers:
  - url: https://api.truthlocks.com
    description: Production API
  - url: https://sandbox-api.truthlocks.com
    description: Sandbox Environment
security:
  - APIKey: []
tags:
  - name: Authentication
    description: API key and token management
  - name: Issuers
    description: Issuer registration and trust management
  - name: Keys
    description: Cryptographic key management for issuers
  - name: Attestations
    description: Attestation lifecycle (mint, revoke, supersede)
  - name: Verification
    description: Attestation verification and proof bundles
  - name: Governance
    description: Issuer governance workflows (admin only)
  - name: Identity
    description: Organization, user, and role management
  - name: Audit
    description: Audit event queries
  - name: Platform
    description: Platform administration (super admin only)
  - name: Platform Review
    description: Staff review workflows for issuer applications
  - name: Tenant Console
    description: Tenant profile and lifecycle endpoints
  - name: Health
    description: Service health and readiness endpoints
  - name: Risk
    description: Risk signal ingestion and fraud detection
  - name: Risk Enforcement
    description: Risk enforcement actions — block, challenge, quarantine, and configuration
  - name: Billing
    description: Billing, subscription, and addon management
  - name: Machine Identity
    description: >-
      Machine Agent Identity Protocol (MAIP) — agent registration, sessions,
      trust, witness, compliance, orchestration, and observability
externalDocs:
  description: Transparency read-only API (separate service spec)
  url: >-
    https://github.com/truthlocks/truthlock/blob/main/docs/transparency/openapi.yaml
paths:
  /v1/receipts/{id}/proof-bundle:
    get:
      tags:
        - Receipts
      summary: Get receipt proof bundle
      description: >-
        Returns the full cryptographic proof bundle for a receipt including
        transparency log inclusion proof.
      operationId: receipts.proofBundle
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Receipt UUID
      responses:
        '200':
          description: Proof bundle
          content:
            application/json:
              schema:
                type: object
                properties:
                  receipt_id:
                    type: string
                  signature:
                    type: object
                  transparency_proof:
                    type: object
                  issuer:
                    type: object
        '401':
          description: Authentication required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
        '404':
          description: Receipt not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
      security:
        - APIKey: []
components:
  schemas:
    ErrorEnvelope:
      type: object
      required:
        - code
        - message
        - http_status
      properties:
        code:
          type: string
          description: Machine-readable error code
          enum:
            - AUTH_REQUIRED
            - AUTH_INVALID
            - PERMISSION_DENIED
            - TENANT_IDENTITY_UNVERIFIED
            - NOT_FOUND
            - VALIDATION_ERROR
            - CONFLICT
            - PAYLOAD_TOO_LARGE
            - RATE_LIMIT_EXCEEDED
            - QUOTA_EXCEEDED
            - SERVICE_UNAVAILABLE
            - INTERNAL_ERROR
        message:
          type: string
          description: Human-readable error message
        http_status:
          type: integer
          description: HTTP status code
        retry_after_ms:
          type: integer
          description: Milliseconds to wait before retrying (for rate limits)
        details:
          type: object
          description: Additional error context
      example:
        code: AUTH_REQUIRED
        message: Authentication required
        http_status: 401
  securitySchemes:
    APIKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: API key for machine-to-machine authentication

````