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
IANA timezone string (e.g., “America/New_York”)
string
Comma-separated client IDs
string
Comma-separated campaign IDs
string
Set to “true” to return full data set

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, how positive replies are counted) are documented once in How Analytics Metrics Are Calculated.
One row is returned per campaign, breaking its replies down by the sentiment category of the lead, attributed to the date the reply was received.
Unlike positive_replied on the other endpoints, these are response-event counts, not distinct leads — a lead that replies twice is counted twice. As a result, positive_reply here can be higher than the positive_replied shown by overall-stats-v2 for the same window, which counts each lead once. Don’t expect the two to match.
Counts are scoped to the date range inclusive on both ends; a single date returns that one full day. The lead category is mutable, so re-categorising a lead changes historical counts.