Appearance

CryptoComply API ​

These guides show you how to integrate CryptoComply into your own stack. If you only need the raw endpoint list, jump to the generated REST reference or the MCP tool reference.

CryptoComply exposes two programmatic surfaces over the same data and permissions:

  • REST API — call CryptoComply from any backend, script, or job. This is what the guides in this section cover.
  • MCP server — connect an AI client (Claude, ChatGPT, Cursor, and others) to CryptoComply. See the MCP integration guide.

Base URL ​

https://api.cryptocomply.xyz

Every REST path in these docs is relative to that host — for example, GET /api/orgs/ means GET https://api.cryptocomply.xyz/api/orgs/.

Authentication at a glance ​

The REST API authenticates with a user-scoped API key sent in the Authorization header:

Authorization: Api-Key your_api_key_here

Keys carry the same role-based permissions as the user who created them, and each key is either read-only or full-access. See Authentication & API keys for how to create, scope, and rotate them.

Start here ​

  • Quickstart — make your first authenticated call in under five minutes, with copy-paste examples in curl, Python, Node, and Go.
  • Concepts & data model — organizations, profiles, blockchain addresses, alerts, and how multi-tenancy works.
  • Authentication & API keys — key creation, read-only vs full-access, rotation.
  • Pagination and Errors — the cross-cutting conventions every endpoint follows.

Full reference ​