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

# Revoke Api Key Via Edge Function

> Revoke an API key (via Edge Function)

Marks the API key as revoked. The key can no longer be used for authentication.

Security:
- Only callable by edge functions (validated via shared secret)
- Edge function validates user's JWT on Supabase side
- Users can only revoke their own keys

Headers (from edge function):
    X-Edge-Secret: Shared secret
    X-User-Id: Supabase user ID (already validated)
    X-User-Email: User email (already validated)
    
Returns:
    Success message



## OpenAPI

````yaml openapi.json post /v2/auth/api-keys/{key_id}/revoke
openapi: 3.1.0
info:
  title: Valiqor API
  description: >-
    The Valiqor API provides programmatic access to AI application testing,
    evaluation, failure analysis, and security auditing.


    ## Authentication


    All API requests require an API key passed as a Bearer token in the
    `Authorization` header:


    ```

    Authorization: Bearer vq-xxxxxxxxxxxxxxxxxxxx

    ```


    Get your API key from the [Valiqor Dashboard](https://app.valiqor.com) or
    via `valiqor login` CLI command.


    ## Base URL


    ```

    https://api.valiqor.com

    ```
  version: 2.0.0
  contact:
    name: Valiqor Support
    url: https://valiqor.com
    email: support@valiqor.com
servers:
  - url: https://api.valiqor.com
    description: Production
security: []
tags:
  - name: Authentication
    description: >-
      API key validation, user management, device authorization flow, and CLI
      authentication. All SDK requests require a valid API key passed as a
      Bearer token.
  - name: Evaluation
    description: >-
      Run quality evaluations on datasets or traces. Compute metrics like
      faithfulness, relevance, coherence, and more. Compare runs and track
      trends over time.
  - name: Security
    description: >-
      Security audits (S1-S23 safety categories) and red team simulations.
      Detect prompt injection, harmful content, data leakage, and other
      vulnerabilities.
  - name: Failure Analysis
    description: >-
      Analyze AI app failures with root cause detection, severity scoring, and
      actionable fix suggestions. Supports both trace-based (full) and
      dataset-based (minimal) analysis modes.
  - name: Tracing
    description: >-
      Upload and query execution traces from AI applications. Traces capture
      messages, spans, tool calls, retrievals, and LLM interactions for
      debugging and evaluation.
  - name: Scanner
    description: >-
      Upload code scans to detect AI app features, workflows, and prompts.
      Generates evaluation configurations automatically from your codebase.
  - name: Projects
    description: >-
      Create and manage projects. Projects are containers that organize
      evaluation runs, security audits, traces, and failure analysis results.
paths:
  /v2/auth/api-keys/{key_id}/revoke:
    post:
      tags:
        - Authentication
      summary: Revoke Api Key Via Edge Function
      description: >-
        Revoke an API key (via Edge Function)


        Marks the API key as revoked. The key can no longer be used for
        authentication.


        Security:

        - Only callable by edge functions (validated via shared secret)

        - Edge function validates user's JWT on Supabase side

        - Users can only revoke their own keys


        Headers (from edge function):
            X-Edge-Secret: Shared secret
            X-User-Id: Supabase user ID (already validated)
            X-User-Email: User email (already validated)
            
        Returns:
            Success message
      operationId: revoke_api_key_via_edge_function_v2_auth_api_keys__key_id__revoke
      parameters:
        - name: key_id
          in: path
          required: true
          schema:
            type: string
            title: Key Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````