From 676ab384eedd6a4713a25d40595a61f51815e83f Mon Sep 17 00:00:00 2001 From: Nikita Varabei Date: Tue, 26 May 2026 16:24:20 -0500 Subject: [PATCH 1/3] docs: update API Overview based on knowledge update "Building custom reporting flows without ChainPatrol bots" --- external-api/overview.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/external-api/overview.mdx b/external-api/overview.mdx index dd65c92..d036d7d 100644 --- a/external-api/overview.mdx +++ b/external-api/overview.mdx @@ -30,3 +30,12 @@ as a free service to wallets, security apps, and marketplaces. Fetch our entire allowlist/blocklist for use in your own application. + +## Custom Reporting Flows + +If you want to build your own reporting flow for a platform we don't support yet (chat apps, internal systems, etc.) or can't use our Discord/Telegram/Slack bots, you can use ChainPatrol's public APIs to replicate the functionality: + +- **Asset Check API** (`/external-api/asset-check`) to check the status of domains/URLs/addresses against ChainPatrol's blocklist (e.g., to warn users about malicious links in their chat or platform) +- **Report Create API** (`/external-api/report-create`) to submit reports into ChainPatrol from your own system, so reports still land in the ChainPatrol review queue and benefit from the full detection/review/takedown pipeline + +This is the recommended approach for any "we want bot-like reporting but on a platform/system you don't support" use case. \ No newline at end of file From 1d2bd574445f07ec41964b05bbf400ed69f4ecab Mon Sep 17 00:00:00 2001 From: Nikita Varabei Date: Tue, 26 May 2026 16:24:25 -0500 Subject: [PATCH 2/3] docs: update Asset Check based on knowledge update "Building custom reporting flows without ChainPatrol bots" --- external-api/asset-check.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/external-api/asset-check.mdx b/external-api/asset-check.mdx index 73b28ec..a958ac8 100644 --- a/external-api/asset-check.mdx +++ b/external-api/asset-check.mdx @@ -5,10 +5,12 @@ openapi: "POST /asset/check" ## Quick Start +The Asset Check API is commonly used to build custom reporting flows for platforms we don't support yet. Check domains, URLs, and addresses against ChainPatrol's blocklist to warn users about malicious content in your chat app, internal system, or custom platform. + ### Authentication Include your API key in the `X-API-KEY` header: ```bash X-API-KEY: -``` +``` \ No newline at end of file From efefb1d4da2874bd9319ecb077c1d83a49046a27 Mon Sep 17 00:00:00 2001 From: Nikita Varabei Date: Tue, 26 May 2026 16:24:46 -0500 Subject: [PATCH 3/3] docs: update Report Create based on knowledge update "Building custom reporting flows without ChainPatrol bots" --- external-api/report-create.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/external-api/report-create.mdx b/external-api/report-create.mdx index ff82832..5ff360d 100644 --- a/external-api/report-create.mdx +++ b/external-api/report-create.mdx @@ -7,6 +7,8 @@ openapi: "POST /report/create" The Report Create endpoint allows you to submit assets (URLs, domains, blockchain addresses, etc.) for review by the ChainPatrol team. This endpoint handles bulk submissions and provides detailed error reporting for validation failures. +This API is commonly used to build custom reporting flows for platforms we don't support yet. Submit reports from your own chat app, internal system, or custom platform directly into ChainPatrol's review queue, where they benefit from the full detection/review/takedown pipeline. + ## Error Responses ### 422 Unprocessable Content @@ -175,4 +177,4 @@ All assets must be valid for the report to be created A report can only be created once per email address for a specific asset -For technical issues or questions about error responses, contact support@chainpatrol.io and include the full error response in your request. +For technical issues or questions about error responses, contact support@chainpatrol.io and include the full error response in your request. \ No newline at end of file