Skip to content

Get Sdr Leaderboard

GET
/analytics/outbound/sdr-activity/leaderboard

Reps ranked by reply rate.

A rep is only ranked once they have sent at least ten emails - the app’s own floor, and the reason a rep who sent three and got one reply does not appear at 33%.

Not the same report as GET /analytics/sdr/leaderboard, which already ships: that one ranks on the SDR analytics service’s own activity roll-up, this one on outbound sequence performance. Different services, different numbers, both intentional.

Authorizations

Parameters

Query Parameters

days

Size of the trailing window, in days, ending today (UTC).

integer
default: 30 >= 1 <= 365

Size of the trailing window, in days, ending today (UTC).

limit

Reps to return.

integer
default: 20 >= 1 <= 100

Reps to return.

Header Parameters

X-Target-Org-Id
Any of:
string

Responses

200

Successful Response

object
data
required

An OPEN envelope around one report’s answer.

The app wraps every one of these reports in {success, data, meta}, where meta carries the cache state, the window and - on the agency reports - failed_org_ids, the orgs that contributed NOTHING to the totals above. That field is the difference between “this client sent no email” and “we could not query this client”, so it is forwarded rather than flattened away.

Open on purpose: data is dict | list in the app and its contents grow with the product. A closed model would turn every new metric into a silently dropped one.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string