Opening
Home / Docs / API Reference / Events The Events API allows you to track user events and behaviors in your SMASHSEND account. Events are powerful tools for triggering automated workflows, segmenting contacts, and understa
S
docs- Words
- 2,058
- Reading time
- 9 min
- Last crawled
- 2026-09-27
- Language
- EN
Authentication & Base URL
Base URL: All API requests must include your API key in the Authorization header. You can manage your API keys in your SMASHSEND dashboard under Settings → API. Rate Limits: • Single events: 1,000 requests per minute • B
Events Endpoints
POST/v1/events Track a single event for a contact. This endpoint automatically creates or updates the contact if they don't exist, and enqueues the event for processing. Property Limits • Max 100 leaf keys per event • Ma
Event Naming Best Practices
Event names should be descriptive, consistent, and follow a clear naming convention. We recommend using a hierarchical structure with dots to separate namespaces. Recommended Format or Examples Naming Constraints • Max l
Event Deduplication
SMASHSEND automatically handles event deduplication to prevent duplicate events from being processed. This is especially useful for handling network retries or idempotent operations. Automatic Deduplication If you don't
Error Handling
The Events API uses standard HTTP status codes and returns detailed error information to help you debug issues. Common Error Responses 400 - Bad Request 401 - Unauthorized 413 - Payload Too Large 429 - Rate Limit Exceede
Common Use Cases
1. Product Analytics & User Behavior Tracking 2. E-commerce & Transaction Tracking 3. Content Engagement Tracking 4. SaaS Subscription Lifecycle 5. Workflow Automation Triggers Events can trigger automated workflows in S
Best Practices
1. Use Batch Endpoints for High Volume When tracking multiple events, always use the batch endpoint. It reduces network overhead, has higher rate limits, and is more efficient. 2. Implement Proper Error Handling Always h
Limits & Constraints Reference
Event Limits • Event name: max 60 characters • Message ID: max 128 characters • Event payload: max 32KB • Timestamp range: ±30 years from current time Property Limits • Max leaf keys: 100 • Max nesting depth: 3 levels •
9 in stockinsert query
