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

# ANY /proxy

> Technically, any HTTP method can be used, but the most common use cases are GET and POST. Forwards a GET request to a target URL and generates proofs



## OpenAPI

````yaml get /proxy
openapi: 3.1.1
info:
  title: Verity Prover API
  description: API for generating verifiable proofs of API responses
  version: 1.0.0
servers:
  - url: http://localhost:8080
    description: Local Verity Prover Proxy Server
security: []
paths:
  /proxy:
    get:
      summary: Proxy a GET request with proof generation
      description: >-
        Technically, any HTTP method can be used, but the most common use cases
        are GET and POST. Forwards a GET request to a target URL and generates
        proofs
      parameters:
        - name: T-PROXY-URL
          in: header
          required: true
          schema:
            type: string
          description: Target URL to proxy the request to
          example: https://jsonplaceholder.typicode.com/posts
        - name: T-REQUEST-ID
          in: header
          required: true
          schema:
            type: string
          description: Unique identifier for the proof request
          example: 678D765E-B6D0-4BFA-AD4C-EBBC92815B25
        - name: T-REDACTED
          in: header
          required: false
          schema:
            type: string
          description: >-
            Comma-separated list of fields to redact in format
            [req|res]:[body|header]:[field_name]
          example: >-
            res:body:id,req:body:userId,res:body:userId,req:header:x-api-key,res:query:userId,search:title,req:header:x-api-key,res:path:1
        - name: T-PROVE-FAILED-REQ
          in: header
          required: false
          schema:
            type: string
          description: >-
            If present, proof generation will continue even for failed requests
            (status >= 400)
      responses:
        '200':
          description: >-
            Successful response from proxied endpoint with proof generation
            initiated
          content:
            application/json:
              schema:
                type: object

````