Skip to main content
POST
Add assets to organization allowlist

Overview

Batch add multiple assets to your organization’s allowlist. Each asset will be automatically parsed, classified by type, and approved with ALLOWED status. This endpoint supports adding up to 1,000 assets per request with optional metadata like name, description, and group assignment.

Quick Start

Authentication

Include your API key in the X-API-KEY header:

Example Request

Request Body

Supported Asset Types

The endpoint automatically detects and classifies the following asset types:
  • URL - Full URLs with protocol (e.g., https://example.com)
  • ADDRESS - Blockchain addresses (e.g., Ethereum, Bitcoin addresses)
  • PAGE - Web page identifiers
  • DISCORD - Discord server or channel identifiers
  • TELEGRAM - Telegram channel or group identifiers
  • TWITTER - Twitter/X handles (e.g., @username)
  • INSTAGRAM - Instagram handles
  • MEDIUM - Medium publication or user identifiers
  • GITHUB - GitHub repository or user identifiers
  • YOUTUBE - YouTube channel identifiers
  • LINKEDIN - LinkedIn profile identifiers
  • TWITCH - Twitch channel identifiers
  • TIKTOK - TikTok handle identifiers
  • EMAIL - Email addresses

Response

Success Response

Partial Success Response

When some assets succeed and others fail:

Response Fields

Error Responses

400 Bad Request

Returned when the request is malformed or exceeds limits:

401 Unauthorized

Returned when the API key is missing, invalid, or doesn’t have organization access:

404 Not Found

Returned when a specified group ID doesn’t exist:

Common Error Messages

Best Practices

Batch Operations

  • Maximize throughput: Use the full 1,000 asset limit per request when bulk importing
  • Handle partial failures: Always check both successCount and errorCount in responses
  • Retry failed assets: Extract failed assets from results and retry with corrected data

Asset Format

  • URLs: Include protocol (https:// or http://)
    • https://example.com
    • example.com (will be interpreted as domain, not URL)
  • Blockchain addresses: Use full address format
    • 0x1234567890abcdef1234567890abcdef12345678
  • Social handles: Include the @ symbol for Twitter/social platforms
    • @username
    • username (also works)

Metadata

  • Names: Use descriptive names for easier identification in your dashboard
  • Descriptions: Add context about the asset’s purpose, especially for addresses and URLs
  • Groups: Organize assets by type, project, or purpose using groups

Error Handling

  • Check the results array for per-asset success/failure status
  • Use successCount and errorCount for aggregate reporting
  • Log failed assets with their error messages for debugging
  • Implement retry logic for failed assets after correcting issues

Use Cases

Import from Spreadsheet

Add Multiple Asset Types

Notes

  • Assets are automatically parsed and classified by type
  • All successfully added assets receive ALLOWED status
  • Duplicate assets (already in your organization) will fail with an appropriate error
  • The endpoint returns partial success - some assets may succeed while others fail
  • Organization is automatically determined from your API key
  • Group IDs must belong to your organization
  • Asset validation happens during processing; invalid formats will be reported in the results

Authorizations

X-API-KEY
string
header
required

Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.

Body

application/json
assets
object[]
required
Required array length: 1 - 1000 elements

Response

Successful response

results
object[]
required
successCount
number
required
errorCount
number
required