Aicscan API documentation

Aicscan continuously watches the addresses of your treasury, your project or your customers across several chains, and alerts you as soon as a movement matches one of your rules. This documentation is for developers who want to drive Aicscan from their code and receive alerts in their own systems.

Three ways to integrate#

Alerts can also go to Telegram, helloMe, Discord, Slack or email: see Channels.

At a glance#

• Base URL: https://aicscan.io/v1
• Format: UTF-8 JSON, ISO 8601 dates in UTC, amounts as raw integers in strings.
• Authentication: Authorization: Bearer aic_…, one key per workspace, read and write scopes. See Authentication.
• Plans: the API is included in the Pro and Business plans. See Plans and quotas.
• Errors: always { "error": { "code", "message", "details" } }, with a stable code. See Errors.
• Version: the major version is in the path (/v1) and in the Aicscan-Api-Version header. See Versioning.

curl https://aicscan.io/v1/health

{
  "at": "2026-11-14T09:31:02.551Z",
  "chains": [
    { "chain_id": 56, "name": "BNB Chain", "up": true, "last_processed_block": 45123470, "last_confirmed_block": 45123455, "seconds_since_block": 1.2 }
  ],
  "status": "ok",
  "api_version": "1"
}

Where to start#

1. Create an API key in your client area (API keys page), then follow the quickstart: from key to first alert in about ten minutes.
2. Read the rule types to choose what to watch.
3. Plug in a webhook and verify its signatures.

The complete OpenAPI 3.1 document can be downloaded from /v1/openapi.yaml: import it into Postman, Insomnia or a client generator.

Contact#

A question about the API, a Business plan or an integration issue: write to support@aicscan.io. Give your workspace name and, for an error, the route called, the time (UTC) and the code received; never send a full API key.