Wallet Watch

API文档

使用我们的安全REST API将Wallet Watch数据集成到您的应用程序中

Important: 重要提示：Wallet Watch保留审查和批准所有API访问请求的权利。访问权限基于预期用途和合规要求由我们酌情授予。

API密钥层级
根据使用需求提供两个层级
受限

20次请求/月

免费层级

每月重置

无限制

无月度限制

企业层级

需要批准

安全与认证
SHA-256哈希密钥与安全验证
256-bit API keys with SHA-256 hashing
Monthly usage tracking and enforcement
Automatic rate limit reset cycle
Request logging and audit trail
基础URL与认证
开始使用Wallet Watch API

Base URL

https://your-domain.com/api/public

Authentication Header

x-api-key: your_api_key_here

技术详情

• API keys are 64-character hexadecimal strings (256-bit)

• Keys are hashed using SHA-256 before storage

• Limited tier: 20 requests per calendar month with automatic reset

• Unlimited tier: No monthly restrictions (enterprise only)

• All API responses use standard HTTP status codes

• Request/response content-type: application/json

获取提交
通过筛选选项检索钱包提交
GET
/submissions

Query Parameters

limitintegerResults limit (1-500, default: 100)
categoryIdstringFilter by category ID (optional)
cryptocurrencyIdstringFilter by cryptocurrency ID (optional)
searchTermstringSearch in wallet addresses (optional)

Example Request

GET /api/public/submissions?limit=10&searchTerm=1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa

Example Response

{
  "submissions": [
    {
      "id": "cm1234567890",
      "walletAddress": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
      "category": {
        "id": "cat123",
        "name": "Phishing",
        "icon": "AlertTriangle"
      },
      "cryptocurrency": {
        "id": "btc",
        "name": "Bitcoin",
        "symbol": "BTC"
      },
      "reason": "Used in phishing attack targeting crypto users",
      "websiteUrl": "https://fake-exchange.scam",
      "reportedOwner": "Scammer Name",
      "status": "approved",
      "createdAt": "2024-01-15T10:30:00.000Z"
    }
  ],
  "total": 1,
  "limit": 10
}
API使用与限制
技术实现详情

速率限制实现

• Limited Tier: 20 requests per calendar month

• Reset Mechanism: Monthly counter automatically resets on the first day of each month

• Usage Tracking: Each successful API call increments the usage counter

• Enforcement: Requests exceeding the limit receive HTTP 401 with error message

错误响应示例

// Monthly limit exceeded (Limited tier)
{
  "message": "Monthly API limit exceeded (20 requests/month)"
}

// Invalid API key
{
  "message": "Invalid API key"
}

// Missing API key
{
  "message": "API Key is required"
}

请求标头

x-api-key: [your-64-char-api-key]Content-Type: application/jsonAccept: application/json
参考数据端点
检索用于筛选的类别和加密货币

类别

GET
/categories

返回所有可用的非法活动类别，包含ID、名称、描述和图标

加密货币

GET
/cryptocurrencies

返回所有支持的加密货币，包含ID、名称、符号和图标

Example Response Structure

// Categories endpoint
{
  "categories": [
    {
      "id": "cat123",
      "name": "Phishing",
      "description": "Fraudulent websites...",
      "icon": "AlertTriangle"
    }
  ]
}

// Cryptocurrencies endpoint
{
  "cryptocurrencies": [
    {
      "id": "btc",
      "name": "Bitcoin",
      "symbol": "BTC",
      "icon": "bitcoin-icon"
    }
  ]
}
Error Responses
Understanding API error codes
400Bad RequestInvalid or missing parameters
401UnauthorizedMissing or invalid API key
429Rate LimitedToo many requests
500Server ErrorInternal server error

Error Response Format

{
  "success": false,
  "error": "Invalid API key",
  "code": 401
}
API访问申请流程
如何获得API访问权限和批准要求

Access Approval Required: 需要访问批准：Wallet Watch保留审查、批准或拒绝所有API访问请求的权利，完全由我们自主决定。我们根据预期用途、合规要求和平台安全考虑来评估请求。

申请流程

  1. Contact us through our Contact page with your API access request
  2. Provide detailed information about your intended use case and integration plans
  3. Include information about your organization, compliance requirements, and data handling practices
  4. Wait for our team to review your request (review process may take 5-10 business days)
  5. If approved, receive your API key and tier assignment
  6. Begin integration with proper authentication and rate limit compliance

批准要求

• Legitimate business use case for crypto fraud prevention or research

• Compliance with applicable data protection and privacy laws

• Commitment to responsible use of API data

• Technical capability to properly integrate and handle rate limits

• Agreement to our Terms of Use and API usage policies