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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://developers.fireblocks.com/feedback

```json
{
  "path": "/api-reference/compliance/set-byork-light-verdict",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Set BYORK Light verdict

> Submit verdict (ACCEPT or REJECT) for a transaction in the BYORK Light flow. If the transaction is awaiting your decision, the verdict is applied immediately (response status COMPLETED). If processing has not yet reached that point, the verdict is stored and applied when it does (response status PRE_ACCEPTED). Requires BYORK Light to be enabled for the tenant.



## OpenAPI

````yaml https://docs.fireblocks.com/api/v1/swagger.yaml post /screening/byork/verdict
openapi: 3.0.0
info:
  title: Fireblocks API
  description: >
    Fireblocks provides a suite of applications to manage digital asset
    operations and a complete development platform to build your business on the
    blockchain.


    - Visit our website for more information: [Fireblocks
    Website](https://fireblocks.com)

    - Visit our developer docs: [Fireblocks
    DevPortal](https://developers.fireblocks.com)
  version: 1.6.2
  contact:
    email: developers@fireblocks.com
servers:
  - url: https://api.fireblocks.io/v1
    description: Fireblocks Production Environment Base URL
  - url: https://sandbox-api.fireblocks.io/v1
    description: Fireblocks Sandbox Environment Base URL
security: []
paths:
  /screening/byork/verdict:
    post:
      tags:
        - Compliance
      summary: Set BYORK Light verdict
      description: >-
        Submit verdict (ACCEPT or REJECT) for a transaction in the BYORK Light
        flow. If the transaction is awaiting your decision, the verdict is
        applied immediately (response status COMPLETED). If processing has not
        yet reached that point, the verdict is stored and applied when it does
        (response status PRE_ACCEPTED). Requires BYORK Light to be enabled for
        the tenant.
      operationId: setByorkVerdict
      parameters:
        - $ref: '#/components/parameters/X-Idempotency-Key'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ByorkVerdictRequest'
      responses:
        '200':
          description: Verdict applied (COMPLETED) or pre-accepted (PRE_ACCEPTED).
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ByorkVerdictResponse'
        '400':
          description: BYORK Light not enabled for tenant or invalid verdict.
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '409':
          description: >-
            BYORK decision already final, screening already completed, or state
            inconsistent.
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '425':
          description: Too Early - transaction not found (screening not started yet).
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '500':
          description: Internal server error.
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        default:
          $ref: '#/components/responses/Error'
      x-codeSamples:
        - lang: TypeScript
          source: >-
            const response: Promise<FireblocksResponse<ByorkVerdictResponse>> =
            fireblocks.compliance.setByorkVerdict(complianceApiSetByorkVerdictRequest);
        - lang: Java
          source: >-
            CompletableFuture<ApiResponse<ByorkVerdictResponse>> response =
            fireblocks.compliance().setByorkVerdict(byorkVerdictRequest,
            idempotencyKey);
        - lang: Python
          source: >-
            response =
            fireblocks.compliance.set_byork_verdict(byork_verdict_request,
            idempotency_key);
components:
  parameters:
    X-Idempotency-Key:
      name: Idempotency-Key
      in: header
      description: >-
        A unique identifier for the request. If the request is sent multiple
        times with the same idempotency key, the server will return the same
        response as the first request. The idempotency key is valid for 24
        hours.
      required: false
      schema:
        type: string
  schemas:
    ByorkVerdictRequest:
      type: object
      required:
        - txId
        - verdict
      properties:
        txId:
          type: string
          description: Transaction ID to set the verdict for
          example: 550e8400-e29b-41d4-a716-446655440000
        verdict:
          $ref: '#/components/schemas/ByorkSetVerdictEnum'
    ByorkVerdictResponse:
      type: object
      required:
        - status
        - message
      properties:
        status:
          $ref: '#/components/schemas/ByorkVerdictResponseStatusEnum'
        message:
          type: string
          description: Human-readable message
          example: Verdict ACCEPT applied
    ErrorSchema:
      type: object
      properties:
        message:
          type: string
        code:
          type: number
    ByorkSetVerdictEnum:
      type: string
      enum:
        - ACCEPT
        - REJECT
      example: ACCEPT
      description: Verdict to apply (ACCEPT or REJECT).
    ByorkVerdictResponseStatusEnum:
      type: string
      enum:
        - PRE_ACCEPTED
        - COMPLETED
        - PENDING
        - RECEIVED
      example: COMPLETED
      description: >
        PRE_ACCEPTED - Verdict stored and will be applied when processing
        reaches the point where your decision is needed. COMPLETED - Verdict
        final and processing complete. PENDING - Transaction in BYORK flow; no
        final verdict yet (awaiting decision or processing). RECEIVED - Verdict
        final and stored; processing not yet complete.
  headers:
    X-Request-ID:
      schema:
        type: string
      description: >-
        Unique ID correlated to the API request. Please provide it in any
        support ticket you create or on Github issues related to Fireblocks SDKs
  responses:
    Error:
      description: Error Response
      headers:
        X-Request-ID:
          $ref: '#/components/headers/X-Request-ID'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorSchema'

````