Alloy Cases API

Case management, evidences, and review work items.

Operations 8

GET /cases List Cases #
GET /cases/{case_token} Get a Case #
GET /cases/{case_token}/evidences List Case Evidences #
POST /cases/{case_token}/evidences Add Case Evidence #
GET /cases/{case_token}/evidences/{evaluation_token}/alert Get a Case Evidence Alert #
GET /cases/{case_token}/works List Case Works #
POST /cases/{case_token}/works Add Case Work #
POST /cases/multi/works Submit Multi-Case Works #

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/alloy-com-cases-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

alloy-com-cases-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Alloy Cases API
  description: 'The Alloy API is the programmatic surface for Alloy''s identity decisioning

    platform. It exposes the resources behind Alloy''s KYC, KYB, AML, fraud,

    credit, and ongoing-monitoring workflows used by banks, credit unions, and

    fintechs.


    The API is organized around evaluations, journey applications, entities

    (persons and businesses), bank accounts, documents, events, cases,

    investigations, custom lists, published attributes, and webhooks. Sandbox

    and production environments are exposed as two distinct base URLs.

    '
  version: '1.0'
  contact:
    name: Alloy Developer Support
    url: https://help.alloy.com
  license:
    name: Proprietary
    url: https://www.alloy.com/tos
servers:
- url: https://sandbox.alloy.co/v1
  description: Sandbox environment
- url: https://api.alloy.co/v1
  description: Production environment
security:
- basicAuth: []
- bearerAuth: []
tags:
- name: Cases
  description: Case management, evidences, and review work items.
paths:
  /cases:
    get:
      tags:
      - Cases
      summary: List Cases
      operationId: getCases
      responses:
        '200':
          description: Cases
  /cases/{case_token}:
    parameters:
    - name: case_token
      in: path
      required: true
      schema:
        type: string
    get:
      tags:
      - Cases
      summary: Get a Case
      operationId: getCase
      responses:
        '200':
          description: Case
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Case'
  /cases/{case_token}/evidences:
    parameters:
    - name: case_token
      in: path
      required: true
      schema:
        type: string
    get:
      tags:
      - Cases
      summary: List Case Evidences
      operationId: getCaseEvidences
      responses:
        '200':
          description: Evidences
    post:
      tags:
      - Cases
      summary: Add Case Evidence
      operationId: postCaseEvidence
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: Evidence added
  /cases/{case_token}/evidences/{evaluation_token}/alert:
    parameters:
    - name: case_token
      in: path
      required: true
      schema:
        type: string
    - name: evaluation_token
      in: path
      required: true
      schema:
        type: string
    get:
      tags:
      - Cases
      summary: Get a Case Evidence Alert
      operationId: getCaseEvidenceAlert
      responses:
        '200':
          description: Alert
  /cases/{case_token}/works:
    parameters:
    - name: case_token
      in: path
      required: true
      schema:
        type: string
    get:
      tags:
      - Cases
      summary: List Case Works
      operationId: getCaseWorks
      responses:
        '200':
          description: Works
    post:
      tags:
      - Cases
      summary: Add Case Work
      operationId: postCaseWork
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: Work added
  /cases/multi/works:
    post:
      tags:
      - Cases
      summary: Submit Multi-Case Works
      operationId: postCasesMultiWorks
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: Works submitted
components:
  schemas:
    Case:
      type: object
      properties:
        case_token:
          type: string
        status:
          type: string
        entity_token:
          type: string
        created_at:
          type: string
          format: date-time
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: HTTP Basic Authentication with workflow or account-level API key as username and secret as password.
    bearerAuth:
      type: http
      scheme: bearer
      description: OAuth 2.0 bearer token obtained via the OAuth endpoints.