Skip to main content
GET
Get buying-committee coverage
Shows how well the team is threaded into each account: which buying-committee seats its contacts there already fill, and which are empty.

Example

GET /v2/sequencer/tasks/account-coverage?account_keys=acme,globex Take the identifiers from task rows you already have: each task’s contact.account_key, or contact.account when there is no key. The response is keyed by exactly the strings you sent, so you can join it back to your rows without normalizing anything.

Reading the response

Good to know

  • Seats come from job titles, read through the team’s buying-committee map in Get sequencer settings, or the shipped defaults when the team has none.
  • Every contact on the team at the account counts, whether or not it is in a sequence.
  • Up to 100 identifiers and 2,000 contacts per request. Split a larger page of rows into several calls.
  • Identifiers are split on commas, so a company name that contains one, such as Acme, LLC, must be sent as its normalized key (acme).

Authorizations

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Query Parameters

account_keys
string

Comma-separated account identifiers, up to 100. Each is a normalized company name as carried on a task's contact.account_key (lowercase, punctuation and legal suffixes removed, so Acme, LLC is acme), or a company name exactly as stored in contact.account. A company name containing a comma cannot be sent this way; use its normalized form.

Response

Coverage per account.

data
object
required

One entry per identifier sent, keyed by that identifier exactly as sent.