Aclid API

REST API for biosecurity screening and compliance automation. Initiate a pathogen/toxin sequence screen from a FASTA or FASTQ upload, a CSV of named sequences, or an inline JSON payload; poll or retrieve the screen summary, the full findings detail, or a pre-signed stream URL for large result sets; create and retrieve customers (which also initiates a sanctions and watchlist screen); attach notes to screens and customers; and mint a hosted or embeddable customer verification URL. Authentication is an API key passed verbatim in the HTTP Authorization header, and the key itself selects live or test mode.

Operations 18

POST /v2/screen_fasta Initiate Screen (FASTA File Upload) #
POST /v2/screen_csv Initiate Screen (CSV File Upload) #
POST /v2/screen_file Initiate Screen (FASTA File Upload) #
POST /v2/screen Initiate Screen (FASTA File Upload) #
POST /v2/screen_inline Initiate Screen (Inline) #
GET /v2/screens List Screens #
GET /v2/screens/names List Screen Names #
GET /v2/screens/{id}/stream Stream Screen #
GET /v2/screens/{id} Retrieve Screen Summary #
GET /v2/screens/{id}/details Retrieve Screen Details #
GET /v2/verifications/{screen_id} Retrieve Verification #
POST /v2/notes Create Or Update A Note #
GET /v2/screens/{screen_id}/notes List Screen Notes #
POST /v2/verification_url/ Create Verification Url #
GET /v2/customers List Customers #
POST /v2/customers Create Customer #
GET /v2/customers/{requester_id} Retrieve Customer #
GET /v2/customers/{requester_id}/notes List Customer Notes #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/aclid-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

aclid-openapi.yml Raw ↑
openapi: 3.1.0
info:
  title: Aclid API
  description: 'The Aclid API is organized around

    <a href="https://en.wikipedia.org/wiki/REST" target="_blank">REST</a>.

    Our API has predictable resource-oriented URLs, returns

    <a href="https://www.json.org/json-en.html" target="_blank">JSON-encoded</a>

    responses, and uses standard HTTP response codes and authentication.


    You can use the Aclid API in test mode, which doesn''t affect your live data. The API key

    you use to authenticate the request determines whether the request is live mode or test

    mode.'
  version: 2.2.1
servers:
- url: https://api.aclid.bio
  description: 'Aclid production API host, as published in the Authentication section of the Aclid API reference (curl example:
    https://api.aclid.bio/v2/screens)'
paths:
  /v2/screen_fasta:
    post:
      summary: Initiate Screen (FASTA File Upload)
      description: 'Initiate a pathogen screen.


        Input is a file (`Content-Type: multipart/form-data`), in either <a href="https://en.wikipedia.org/wiki/FASTA_format">FASTA</a>
        or

        <a href="https://en.wikipedia.org/wiki/FASTQ_format">FASTQ</a> format.

        Files which are not valid FASTA or FASTQ will be rejected.


        FASTA sequences must each be at least 30 base pairs in length. (FASTQ sequences may be any non-zero length.)

        Total base pair count, across all sequences, may not exceed 1,000,000,000.'
      operationId: handle_v2_screen_fasta_v2_screen_fasta_post
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/Body_handle_v2_screen_fasta_v2_screen_fasta_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '303':
          description: Request was previously cached using the same idempotence key
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screen_csv:
    post:
      summary: Initiate Screen (CSV File Upload)
      description: 'Initiate a pathogen screen.


        Input is a CSV file (`Content-Type: multipart/form-data`) that has the following format:

        ```

        name,sequence

        cholera toxin A2 [Vibrio cholerae],ATGAGCAACACCTGCGACGAGAAGACCCAGAGCCTGGGCGTGAAGTTCCTGGACGAGTACCAGAGCAAGGTGAAGCGGCAGTACTTCAG

        ```


        (This example shows only one sequence, but you may pass in more than one.)


        Sequences must each be at least 30 base pairs in length.

        Total base pair count, across all sequences, cannot exceed 1,000,000,000.'
      operationId: handle_v2_screen_csv_v2_screen_csv_post
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/Body_handle_v2_screen_csv_v2_screen_csv_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '303':
          description: Request was previously cached using the same idempotence key
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screen_file:
    post:
      summary: Initiate Screen (FASTA File Upload)
      description: '`/screen_file` has been deprecated in favor of <a href="#operation/handle_v2_screen_fasta_v2_screen_fasta_post">`/screen_fasta`</a>.
        Please use that instead.'
      operationId: handle_v2_screen_fasta_v2_screen_file_post
      deprecated: true
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/Body_handle_v2_screen_fasta_v2_screen_file_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '303':
          description: Request was previously cached using the same idempotence key
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screen:
    post:
      summary: Initiate Screen (FASTA File Upload)
      description: '`/screen` has been deprecated in favor of <a href="#operation/handle_v2_screen_fasta_v2_screen_fasta_post">`/screen_fasta`</a>.
        Please use that instead.'
      operationId: handle_v2_screen_fasta_v2_screen_post
      deprecated: true
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/Body_handle_v2_screen_fasta_v2_screen_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '303':
          description: Request was previously cached using the same idempotence key
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screen_inline:
    post:
      summary: Initiate Screen (Inline)
      description: "Initiate a pathogen screen.\n\nSequences must each be at least 30 base pairs in length.\nTotal base pair\
        \ count, across all sequences, cannot exceed 1,000,000,000.\n\nInput is a JSON request (`Content-Type: application/json`)\
        \ that has the following body format:\n```\n{\n  \"name\": \"Screen for order #123456\",\n  \"sequences\": [\n   \
        \ {\n      \"name\": \"cholera toxin A2 [Vibrio cholerae]\",\n      \"sequence\": \"ATGAGCAACACCTGCGACGAGAAGACCCAGAGCCTGGGCGTGAAGTTCCTGGACGAGTACCAGAGCAAGGTGAAGCGGCAGTACTTCAG\"\
        \n    }\n  ]\n}\n```\n\n(This example shows only one sequence, but you may pass in more than one.)"
      operationId: Initiate_Screen__Inline__v2_screen_inline_post
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Body_Initiate_Screen__Inline__v2_screen_inline_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '303':
          description: Request was previously cached using the same idempotence key
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screens:
    get:
      summary: List Screens
      description: 'Return a list of recent screens. Screens will include summary data.


        Please refer to this <a href="#tag/Compliance-Reason-Codes">

        list of compliance reason codes</a>.'
      operationId: List_Screens_v2_screens_get
      parameters:
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          maximum: 100
          minimum: 10
          description: Limit on the number of items returned per page.
          title: Limit
        description: Limit on the number of items returned per page.
      - name: screen_id
        in: query
        required: false
        schema:
          type: array
          items:
            type: string
          description: Limit items to specific screen_ids.
          title: Screen Id
        description: Limit items to specific screen_ids.
      - name: status
        in: query
        required: false
        schema:
          type: array
          items:
            $ref: '#/components/schemas/ScreenStatus'
          title: Filter by status
          description: Filter by status
          default:
          - queued
          - running
          - succeeded
          - failed
          - archived
        description: Filter by status
      - name: name
        in: query
        required: false
        schema:
          type: array
          items:
            type: string
          title: Filter by name
          description: Filter by name
        description: Filter by name
      - name: expand
        in: query
        required: false
        schema:
          type: boolean
          title: Expand
          description: Expand the response with additional screen data
          default: false
        description: Expand the response with additional screen data
      - name: cursor
        in: query
        required: false
        schema:
          type: string
          title: Cursor
          description: A cursor for use in pagination
        description: A cursor for use in pagination
      - name: created_after
        in: query
        required: false
        schema:
          type: string
          format: date-time
          title: Created After
          description: Filter to include only reports created after this datetime
        description: Filter to include only reports created after this datetime
      - name: regulatory_status
        in: query
        required: false
        schema:
          type: array
          items:
            $ref: '#/components/schemas/RegulatoryStatus'
          title: Regulatory Status
          description: Filter by one or more regulatory statuses
        description: Filter by one or more regulatory statuses
      - name: verification_status
        in: query
        required: false
        schema:
          type: array
          items:
            $ref: '#/components/schemas/VerificationStatus'
          title: Verification Status
          description: Filter by one or more verification statuses
        description: Filter by one or more verification statuses
      - name: decision_status
        in: query
        required: false
        schema:
          type: array
          items:
            $ref: '#/components/schemas/DecisionStatus'
          title: Decision Status
          description: Filter by one or more decision statuses
        description: Filter by one or more decision statuses
      - name: search_str
        in: query
        required: false
        schema:
          type: string
          title: Search by name
          description: Search by name
        description: Search by name
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportsResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screens/names:
    get:
      summary: List Screen Names
      description: Return all screen names for the authenticated customer, removing duplicates.
      operationId: List_Screen_Names_v2_screens_names_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                items:
                  type: string
                type: array
                title: Response List Screen Names V2 Screens Names Get
      tags:
      - Endpoints
  /v2/screens/{id}/stream:
    get:
      summary: Stream Screen
      description: Return a pre-signed URL to a JSON/CSV file to stream a large screening result.
      operationId: Stream_Screen_v2_screens__id__stream_get
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StreamReportResponse'
        '204':
          description: Screen Not Ready
        '404':
          description: Screen Not Found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screens/{id}:
    get:
      summary: Retrieve Screen Summary
      description: 'Return summary data for a previously submitted screen.


        Please refer to this <a href="#tag/Compliance-Reason-Codes">

        list of compliance reason codes</a>.'
      operationId: Retrieve_Screen_Summary_v2_screens__id__get
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportMetadata'
        '404':
          description: Screen Not Found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screens/{id}/details:
    get:
      summary: Retrieve Screen Details
      description: 'Return detailed data for a previously submitted screen, including match and assessment data.


        Until the screen is completed, this endpoint will return an HTTP 204.


        Please refer to this <a href="#tag/Compliance-Reason-Codes">

        list of compliance reason codes</a>.'
      operationId: Retrieve_Screen_Details_v2_screens__id__details_get
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Id
      - name: max_match_count_per_region
        in: query
        required: false
        schema:
          type: integer
          description: How many matches, at most, to return for each query.
          min: 1
          max: 250
          default: 25
          title: Max Match Count Per Region
        description: How many matches, at most, to return for each query.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  $ref: '#/components/schemas/MatchGroup'
                title: Response Retrieve Screen Details V2 Screens  Id  Details Get
        '204':
          description: Screen Not Ready
        '404':
          description: Screen Not Found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/verifications/{screen_id}:
    get:
      summary: Retrieve Verification
      description: Return data for a previously submitted verification.
      operationId: Retrieve_Verification_v2_verifications__screen_id__get
      parameters:
      - name: screen_id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Screen Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Followup'
        '404':
          description: Verification Not Found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/notes:
    post:
      summary: Create Or Update A Note
      operationId: Create_or_Update_a_Note_v2_notes_post
      parameters:
      - name: content-type
        in: header
        required: true
        schema:
          type: string
          title: Content-Type
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Body_Create_or_Update_a_Note_v2_notes_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Note'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/screens/{screen_id}/notes:
    get:
      summary: List Screen Notes
      description: Returns a list of your screen notes.
      operationId: List_Screen_Notes_v2_screens__screen_id__notes_get
      parameters:
      - name: screen_id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Screen Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Note'
                title: Response List Screen Notes V2 Screens  Screen Id  Notes Get
        '404':
          description: Note Not Found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/verification_url/:
    post:
      summary: Create Verification Url
      description: 'Create a verification URL to verify orders using an embedded integration or a flow hosted by Aclid.



        Provide a `screen_id` obtained by first calling one of the Initiate Screen endpoints. The response will

        include a URL that can be shared with a customer to submit additional information for an order.


        <strong>Embedded Integration</strong>


        The embedded flow is a drop-in module that lets you verify orders within your web page. The flow securely

        collects and verifies compliance information without redirecting away from your website.


        1. Confirm with the Aclid team that your website is in our allow lists.

        2. Load the Aclid client in your application.


        ```

        <script src="https://verify.aclid.bio/widget.js"></script>

        ```

        3. Create a verification URL using this endpoint.

        4. Initialize the verification in whichever way is appropriate for your application.


        ```

        Aclid.showEmbeddedVerification(({ verificationUrl: string, onSuccess: function })

        ```

        <strong>Hosted Flow Integration</strong>


        The hosted flow allows allows your team to verify orders through Aclid without spending time on development.

        It is hosted by Aclid but its branding and theming is fully customizable.


        1. Create a verification URL using this endpoint and optionally provide a `redirect_url` to redirect users back

        to your website after verification.

        2. Redirect from your website to the URL created in step 1.'
      operationId: Create_Verification_URL_v2_verification_url__post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Body_Create_Verification_URL_v2_verification_url__post'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FollowupURLCreateResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/customers:
    get:
      summary: List Customers
      description: Returns a list of your customers. The customers are returned sorted by creation date, with the most recent
        customers appearing first.
      operationId: List_customers_v2_customers_get
      parameters:
      - name: search_str
        in: query
        required: false
        schema:
          type: string
          title: Search
          description: Search by name or company
        description: Search by name or company
      - name: status_filter
        in: query
        required: false
        schema:
          type: array
          items:
            type: string
          title: Status
          description: Filter by customer status
          default: []
        description: Filter by customer status
      - name: decision_status
        in: query
        required: false
        schema:
          type: array
          items:
            type: string
          title: Decision Status
          description: Filter by customer status
          default: []
        description: Filter by customer status
      - name: page_index
        in: query
        required: false
        schema:
          type: integer
          default: 1
          title: Page Index
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/CustomerScreen'
                title: Response List Customers V2 Customers Get
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
    post:
      summary: Create Customer
      description: Creates the customer and initiates a sanction and watchlist screen.
      operationId: Create_customer_v2_customers_post
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Body_Create_customer_v2_customers_post'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SanctionScreenCreateResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/customers/{requester_id}:
    get:
      summary: Retrieve Customer
      description: Returns customer data.
      operationId: Retrieve_customer_v2_customers__requester_id__get
      parameters:
      - name: requester_id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Requester Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomerScreen'
        '404':
          description: Customer not found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
  /v2/customers/{requester_id}/notes:
    get:
      summary: List Customer Notes
      description: Returns a list of your customer notes.
      operationId: List_Customer_Notes_v2_customers__requester_id__notes_get
      parameters:
      - name: requester_id
        in: path
        required: true
        schema:
          type: string
          minLength: 5
          maxLength: 36
          title: Requester Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/CustomerNote'
                title: Response List Customer Notes V2 Customers  Requester Id  Notes Get
        '404':
          description: Customer not found
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Endpoints
components:
  schemas:
    Body_Create_Verification_URL_v2_verification_url__post:
      properties:
        screen_id:
          type: string
          title: Screen Id
          description: The screen id for which you want to create a verification.
        redirect_url:
          type: string
          title: Redirect Url
          description: The URL to redirect to after verification is completed.
      type: object
      required:
      - screen_id
      title: Body_Create_Verification_URL_v2_verification_url__post
    Body_Create_customer_v2_customers_post:
      properties:
        name:
          type: string
          title: Name
        company:
          type: string
          title: Company
        address:
          type: string
          title: Address
        country:
          type: string
          title: Country
        screen_id:
          type: string
          title: Screen Id
      type: object
      required:
      - name
      - company
      title: Body_Create_customer_v2_customers_post
    Body_Create_or_Update_a_Note_v2_notes_post:
      properties:
        screen_id:
          type: string
          title: Screen Id
        content:
          title: Content
          type:
          - string
          - 'null'
        note_id:
          title: Note Id
          type:
          - string
          - 'null'
        decision_status:
          anyOf:
          - $ref: '#/components/schemas/DecisionStatus'
          - type: 'null'
      type: object
      required:
      - screen_id
      title: Body_Create_or_Update_a_Note_v2_notes_post
    Body_Initiate_Screen__Inline__v2_screen_inline_post:
      properties:
        name:
          title: Upload Name
          description: A display label that's useful for you to identify this screen. Unused by Aclid.
          examples:
          - 'Order #123456'
          type:
          - string
          - 'null'
          maxLength: 100
        sequences:
          items:
            $ref: '#/components/schemas/ScreenInputSequence'
          type: array
          title: Sequences
        idempotence_key:
          title: Idempotence Key
          description: Optional. Within any 24-hour window, the first screen request with a given idempotence key will be
            processed normally. However, subsequent screen requests (within 24 hours) with the same idempotence key will not
            be re-assessed. Instead, those subsequent requests will be redirected (HTTP 303) to the original screen's summary.
          examples:
          - 4202ba63-5122-4904-b2d8-a3cbf81692de
          type:
          - string
          - 'null'
          maxLength: 60
        asynchronous:
          type: boolean
          title: Asynchronous
          description: Set asynchronous to false for real-time screening results
          default: true
        verification_success_url:
          title: Verification Success Url
          description: URL to redirect to after verification is completed
          type:
          - string
          - 'null'
        frameworks:
          title: Frameworks
          description: "Default: `['us_ccl_export_control', 'eu_dual_use_export_control', 'us_select_agent', 'us_screening_framework']`.\n\
            \nList of frameworks to screen sequences against.\n\n Please refer to [this](#tag/Compliance-Reason-Codes) list\
            \ of available frameworks. Reach out to us if you'd like to add a framework not currently available in the list\
            \ above or if you'd like to use custom criteria exclusive to your account."
          type:
          - array
          - 'null'
          items:
            type: string
        requester_id:
          title: The associated requester id for this screen.
          type:
          - string
          - 'null'
          maxLength: 100
        sequence_type:
          $ref: '#/components/schemas/SequenceType'
          title: Sequence Type
          description: 'The type of the submitted sequences: `nucleotide` (default) or `amino_acid`. All sequences in a single
            screen must be of the same type.'
          default: nucleotide
      type: object
      required:
      - sequences
      title: Body_Initiate_Screen__Inline__v2_screen_inline_post
    Body_handle_v2_screen_csv_v2_screen_csv_post:
      properties:
        file:
          type: string
          contentMediaType: application/octet-stream
          title: CSV File
          description: A valid CSV sequence file
        name:
          title: Upload Name
          description: A display label that's useful for you to identify this screen. Unused by Aclid.
          examples:
          - 'Order #123456'
          type:
          - string
          - 'null'
          maxLength: 100
        idempotence_key:
          title: Idempotence Key
          description: Optional. Within any 24-hour window, the first screen request with a given idempotence key will be
            processed normally. However, subsequent screen requests (within 24 hours) with the same idempotence key will not
            be re-assessed. Instead, those subsequent requests will be redirected (HTTP 303) to the original screen's summary.
          examples:
          - 4202ba63-5122-4904-b2d8-a3cbf81692de
          type:
          - string
          - 'null'
          maxLength: 100
        asynchronous:
          type: boolean
          title: Asynchronous
          description: Set asynchronous to false to wait for real-time response
          default: true
        verification_success_url:
          title: Verification Success Url
          description: URL to redirect to after verification is completed
          type:
          - string
          - 'null'
        frameworks[]:
          title: Frameworks[]
          description: "Default: \n\nframeworks[]=us_ccl_export_control\n\nframeworks[]=eu_dual_use_export_control\n\nframeworks[]=us_select_agent\n\
            \nframeworks[]=us_screening_framework\n\nList of frameworks to screen sequences against.\n\n Please refer to [this](#tag/Compliance-Reason-Codes)\
            \ list of available frameworks. Reach out to us if you'd like to add a framework not currently available in the\
            \ list above or if you'd like to use custom criteria exclusive to your account."
          type:
          - array
          - 'null'
          items:
            type: string
        requester_id:
          title: The associated requester id for this screen.
          type:
          - string
          - 'null'
          maxLength: 100
        sequence_type:
          $ref: '#/components/schemas/SequenceType'
          ti

# --- truncated at 32 KB (78 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/aclid/refs/heads/main/openapi/aclid-openapi.yml