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

# Compliance Receipts

> Fetch the signed SMLTP compliance receipt for a completion

# Compliance Receipts

When a completion is routed through the **SMLTP gateway**, SecureAI produces a signed compliance **receipt** — cryptographic proof of the policy that governed the call. This endpoint fetches that receipt by its bundle id.

Receipts exist only for gateway-routed deployments. On direct-provider deployments there is no gateway to sign receipts, and this endpoint returns `404`.

## Endpoint

```
GET /receipts/:bundleId
```

## Where the bundle id comes from

Completion responses expose the bundle id whenever an SMLTP entitlement is minted for the call:

* Classic endpoint: `metadata.smltp.bundle_id` (and a ready-made `metadata.smltp.receipt_url`).
* OpenAI-compatible endpoint: `secureai.smltp_bundle_id`.

The bundle id (an entitlement id such as `jti-…`) is returned even on native/direct-provider deployments. The **signed receipt** at that id, however, only exists when traffic is routed through the SMLTP gateway — on direct deployments this endpoint returns `404` (see below).

## Authentication

```bash theme={null}
Authorization: Bearer sk-your-api-key-here
```

## Request Example

```bash theme={null}
curl -X GET "https://{customer.name}.hiperai.ai/api/external/receipts/bnd_9f2c...e71" \
  -H "Authorization: Bearer sk-your-api-key-here"
```

## Response

### 200 OK

```json theme={null}
{
  "success": true,
  "receipt": {
    "bundle_id": "bnd_9f2c...e71",
    "...": "signed SMLTP receipt payload (policy, entitlement, verdict, signatures)"
  }
}
```

The `receipt` object is the signed payload emitted by the gateway. See [SMLTP Security](/security/smltp) for how receipts fit into the transparency and audit model.

### 404 Not Found

```json theme={null}
{
  "success": false,
  "error": "Receipt not found",
  "message": "No receipt for this bundle id. Receipts are only available when requests are routed through the SMLTP gateway, and are retained in its in-memory store for a limited time. The authoritative record is the hash-chained audit log."
}
```

### 400 Bad Request

Returned when the bundle id is missing or longer than 128 characters.

## Notes

* Receipts are held in the gateway's in-memory store for a limited time. For long-term proof, rely on the **hash-chained audit log** — the authoritative, immutable record. See [Immutable Logs](/security/immutable-logs).
* Not every deployment routes through the gateway; treat a `404` as "no gateway receipt for this call," not an error in your integration.

## Related

* [SMLTP Security](/security/smltp)
* [Immutable Logs](/security/immutable-logs)
* [Chat Completion](/api/chat/completions)


## OpenAPI

````yaml GET /receipts/{bundleId}
openapi: 3.0.3
info:
  title: SecureAI External API
  description: >
    SecureAI External API provides AI chat completion and image generation
    capabilities with knowledge base retrieval, 

    security policies, and comprehensive usage tracking. This API is designed
    for external developers 

    and integrations using API key authentication.


    ## Key Features

    - **RAG (Retrieval-Augmented Generation)**: Automatically search knowledge
    bases for relevant context

    - **Multi-Model Support**: OpenAI, Anthropic, Google, Meta, and other AI
    models

    - **Model Redundancy & Failover**: Caller-defined failover chains (primary +
    fallbacks) with per-attempt timeouts

    - **OpenAI-Compatible Endpoint**: Point any OpenAI SDK at `/api/external/v1`
    — no code changes

    - **Image Generation**: Generate and edit images using Google Gemini 2.5
    Flash Image

    - **Speech-to-Speech (S2S)**: Real-time voice conversations using OpenAI
    Realtime API with WebRTC

    - **Security Policies**: SMLTP policy enforcement, per-call Prompt Shield,
    and signed compliance receipts

    - **Usage Tracking**: Comprehensive usage monitoring, self-service quota,
    and rate limiting

    - **Knowledge Base Integration**: Access to personal and shared knowledge
    bases

    - **User Management**: Complete user, group, and role management
    capabilities

    - **Audit Logging**: Comprehensive activity and security audit logs


    ## Authentication

    All endpoints (except health check) require API key authentication using
    Bearer token:

    ```

    Authorization: Bearer sk-your-api-key-here

    ```


    ## Billing and Usage

    By default, API requests are billed to the user account that owns the API
    key. You can specify 

    a different user to bill by including the `user_id` parameter in your
    request. This allows for:

    - Multi-tenant applications with per-user billing

    - Flexible completion limit management

    - Per-user "Usage by Model" settings


    ## Rate Limits

    - Default: 60 requests per minute, 1000 requests per hour

    - Daily limits: 100 requests (configurable)

    - Monthly limits: 10,000 requests (configurable)


    ## Base URL

    ```

    https://secureai.hiperai.ai/api/external

    ```
  version: 1.1.0
  contact:
    name: SecureAI Support
    email: support@secureai.hiperai.ai
  license:
    name: Proprietary
    url: https://secureai.hiperai.ai/terms
servers:
  - url: https://secureai.hiperai.ai/api/external
    description: Production server
  - url: http://localhost:3010/api/external
    description: Development server
security:
  - ApiKeyAuth: []
tags:
  - name: System
    description: System health and status endpoints
  - name: Discovery
    description: Endpoints to discover available models, indexes, and policies
  - name: Chat
    description: AI chat completion endpoints
  - name: User Management
    description: Endpoints for managing user accounts and roles
  - name: Index Management
    description: Endpoints for managing knowledge base indexes
  - name: Group Management
    description: Endpoints for managing user groups
  - name: SMLTP Security
    description: Endpoints for managing SMLTP security policies and audit logs
  - name: Role Management
    description: Endpoints for managing user roles
  - name: Activity Logs
    description: Endpoints for retrieving activity logs
externalDocs:
  description: SecureAI Documentation
  url: https://secureai.hiperai.ai/docs
paths:
  /receipts/{bundleId}:
    get:
      tags:
        - Security
      summary: Fetch a signed SMLTP compliance receipt
      description: >
        Returns the signed compliance receipt for a gateway-routed completion.
        The

        bundle id is exposed on completion responses as
        `metadata.smltp.bundle_id`

        (classic) or `secureai.smltp_bundle_id` (/v1). Returns 404 on

        direct-provider deployments (no gateway to sign receipts).
      operationId: getReceipt
      parameters:
        - name: bundleId
          in: path
          required: true
          schema:
            type: string
            maxLength: 128
      responses:
        '200':
          description: The signed receipt object
        '400':
          description: Invalid bundle id
        '404':
          description: No receipt for this bundle id (or non-gateway deployment)
      security:
        - ApiKeyAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: |
        API key authentication using Bearer token format.
        Example: `Authorization: Bearer sk-your-api-key-here`

````