Send a single conversion event to track user actions that trigger rewards.

When to Use This Endpoint

• Tracking real-time user actions (trades, deposits, purchases, etc.)
• Sending events as they happen for immediate attribution
• Recording individual user conversions with unique deduplication IDs
• Integrating event tracking into your application's user flows

When NOT to Use This Endpoint

• Sending multiple events at once (use POST /v1/events/batch instead for better performance)
• Bulk importing historical events (use batch endpoint)
• High-throughput scenarios with >100 events/minute (use batch endpoint)

Important Constraints

• Rate Limit: 100 requests/minute
• Deduplication: Each event must have a unique dedup_id to prevent duplicates
• Event Name: Must match a trigger name configured in your project
• User Identifier: Must be valid for the specified identifier_type
• Timestamp: Optional - defaults to current time if not provided

Common Errors

• 400 Bad Request: Invalid user identifier format or missing required fields
• 403 Forbidden: API key lacks SendTrackingEvent scope
• 409 Conflict: Event with this dedup_id already exists (duplicate submission)

Related Endpoints

• POST /v1/events/batch - Send multiple events efficiently
• GET /v1/events/status - Check event creation status