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

# List schemas

> Lists registry entries — built-in schemas (read-only) and custom schemas. Requires the admin:schemas:read scope.



## OpenAPI

````yaml /products/specter/openapi.yaml get /api/admin/schemas
openapi: 3.1.0
info:
  contact:
    email: support@hellgate.io
    name: Starfish GmbH & Co. KG
    url: https://hellgate.io/cpa/specter
  description: Composable decision engine and fraud prevention service.
  license:
    name: Hellgate API Terms
    url: https://hellgate.io/terms-and-conditions
  title: Specter API
  version: '1.0'
servers:
  - description: Managed instance of Specter
    url: https://{instance}.{env}.on-hellgate.cloud
    variables:
      instance:
        default: my-instance
        description: Your unique instance slug, provided during onboarding.
      env:
        default: eu1
        description: Deployment environment (currently eu1).
security: []
tags:
  - description: Evaluate transactions and retrieve decision results.
    name: Decisions
  - description: Close decisions that were flagged for manual review.
    name: Resolutions
  - description: Report payment lifecycle events for a prior decision.
    name: Lifecycle Events
  - description: Manage rulesets and their activation lifecycle.
    name: Rulesets
  - description: Register and version custom decision-payload schemas.
    name: Schemas
  - description: Configure interceptors and intercept live payment requests.
    name: Interceptors
  - description: Subscribe to decision and event notifications.
    name: Webhooks
  - description: Manage blocked field values.
    name: Blacklist
paths:
  /api/admin/schemas:
    get:
      tags:
        - Schemas
      summary: List schemas
      description: >-
        Lists registry entries — built-in schemas (read-only) and custom
        schemas. Requires the admin:schemas:read scope.
      operationId: admin_schemas_list
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SchemaList'
          description: Schema list
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Unauthorized
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Forbidden
      callbacks: {}
      security:
        - bearerAuth: []
components:
  schemas:
    SchemaList:
      properties:
        data:
          items:
            $ref: '#/components/schemas/Schema'
          type: array
        links:
          properties:
            next:
              description: >-
                Always null — the list is returned whole; the registry is not
                paginated.
              type:
                - string
                - 'null'
          type: object
      title: SchemaList
      type: object
    Error:
      description: Generic error response with classifier, code, and message
      example:
        classifier: NOT_FOUND
        code: 404
        message: The requested resource does not exist
      properties:
        classifier:
          type: string
        code:
          type: integer
        message:
          type: string
      required:
        - classifier
        - code
        - message
      title: Error
      type: object
    Schema:
      properties:
        built_in:
          description: >-
            True for schemas that ship with Specter (`transaction`). Built-ins
            are read-only — they cannot be published to or deprecated — and
            change only additively through Specter releases. Their documents are
            readable through the version endpoints.
          type: boolean
        created_at:
          description: >-
            Null for built-in schemas, which ship with the platform rather than
            being registered.
          format: date-time
          type:
            - string
            - 'null'
        latest_version:
          example: 3
          type: integer
        name:
          example: customer-registration
          type: string
      title: Schema
      type: object
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: >-
        HS256-signed JWT bearer token, obtained via the OAuth2
        client-credentials grant (see Authentication).
      scheme: bearer
      type: http

````