SanctionsKit Counterparties API

Counterparty operations of the SanctionsKit API — list persistent customer and vendor records, read a counterparty with its linked screening, case and monitor history, and page through that history including expired evidence metadata.

Operations 3

GET /counterparties List persistent customer and vendor records #
GET /counterparties/{id} Read a counterparty and linked screening, case and monitor history #
GET /counterparties/{id}/history Page through linked history including truthful expired evidence metadata #

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/sanctionskit:sanctionskit-counterparties-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

OpenAPI Specification

sanctionskit-counterparties-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SanctionsKit Counterparties API
  version: 1.0.0
  description: Explore success and error examples without an account or API key. Recorded examples use isolated synthetic application data; remaining examples are labeled contract fixtures. Potential-match screening is for review. No-match is limited to selected, qualified sources. Sandbox uses synthetic records and is never billed. Each successfully completed subject consumes one allowance unit, including monitoring rescreens. Failed rows and idempotent retries do not consume additional units.
servers:
- url: /api/v1
  description: This site origin; deployment configuration and access rules apply
tags:


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