campaigns

get/api/campaigns/{id}/runs/count

Request

  • Base URL: https://app.heykairon.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.heykairon.com/api/campaigns/{id}/runs/count
  • Auth: API key in header x-api-key

Path parameters

idstring required

Query parameters

bucket'waiting' | 'didnt_accept' | 'didnt_answer' | 'replied' | 'skipped' | 'error' | 'interested'

Filter to one activity bucket: waiting, didnt_accept, didnt_answer, replied, interested (a subset of replied), skipped (an ICP / enrollment-filter verdict or an operator stop), or error. Omit for every run.

string
OR
string[]

Activity states to include; several read as "any of these".

nodeKeystring

Only runs that reached this step, by the node key the graph gave it — including runs that have since moved past it or finished. Pair it with dateFrom/dateTo to ask who completed THIS step on those days, which is the only way to tell a first message apart from a follow-up in a sequence with more than one message step.

qstring

Find a person by name, headline, company or LinkedIn handle.

dateFromstring

Earliest day to include, inclusive (YYYY-MM-DD). Dates each run by its LAST event — unless nodeKey is also set, which dates it by that step instead.

dateTostring

Latest day to include, inclusive (YYYY-MM-DD). Dates each run by its LAST event — unless nodeKey is also set, which dates it by that step instead.

string
OR
string[]

Only people enrolled from these source lists.

string
OR
string[]

Only people with these ICP verdicts; several read as "any of these".

funnel'invite_sent' | 'invite_accepted' | 'message_sent' | 'replied' | 'interested'

Only the people one Performance funnel card counts: invite_sent, invite_accepted, message_sent, replied or interested.

Changes

No recorded changes to this operation across all 7 revisions of this API.