Skip to main content
GET

Query Parameters

string
required
Your SmartLead API key
string
required
Start date (YYYY-MM-DD format)
string
required
End date (YYYY-MM-DD format)
string
required
IANA timezone string (e.g., “America/New_York”)
string
Comma-separated client IDs
string
Comma-separated campaign IDs

Response Codes

Success
Request successful
Bad Request
Invalid request parameters or malformed request body
Unauthorized
Invalid or missing API key. Check your authentication.
Not Found
The requested resource (campaign, lead, email account, etc.) does not exist or you don’t have access to it
Validation Error
Request validation failed. Check parameter types, required fields, and value constraints.
Rate Limit Exceeded
Too many requests. Please slow down and retry after the rate limit resets.
Internal Server Error
Server error occurred. Please try again or contact support if the issue persists.
Service Unavailable
API is temporarily unavailable or under maintenance. Please try again later.

How these metrics are calculated

Shared rules (inclusive date boundaries, unique vs raw counts, rate formulas) are documented once in How Analytics Metrics Are Calculated.
Unlike the event-date day-wise endpoint, every metric here is bucketed by the day the email was sent (sent_time). An open or reply is counted on the date its email went out, regardless of when the open/reply actually happened — which is what makes this view useful for analysing send-schedule performance. The raw counts are additive across days; unique_lead_reached is not (a lead reached on two days is counted once per day). Dates are inclusive on both ends — sent_time >= start 00:00:00 AND sent_time <= end 23:59:59 — and a single date returns that one full day. timezone is required so the daily boundaries are drawn in your local time.