Skip to main content
GET
Get analytics overview
The metrics come back at the top level of the response, not inside data.

Which calls count

  • Finished calls only. Calls with is_completed: false are left out: attempts the rep moved on from to dial another of the contact’s numbers, and inbound calls answered in the app that are not logged yet.
  • Active members only, by default. Pass user_ids to choose the reps, including inactive ones.
  • Calls logged in the period. The period is a run of whole UTC days.
  • Matching dispositions, if you ask. With disposition_ids, only calls with those dispositions count. total_follow_up_tasks ignores this filter.
The same rules apply to List call performance by contact list and List call performance by SDR. Results are cached for up to 5 minutes, so a repeated request can return the same numbers.

Dates are whole UTC days

timezone is accepted but has no effect. To report on days in another time zone, pull calls from List call logs, which filters on exact timestamps, and group them yourself. The previous period has the same length and ends just before start_date. For September 1 to 30, it runs from 2 to 31 August.

Metrics

Reading growth_rate

Each metric is { "value": ..., "growth_rate": ... }. growth_rate is (current - previous) / previous as a ratio rounded to two decimals, so 0.13 means up 13% and -0.05 means down 5%. Multiply by 100 to show a percentage. When the previous value is 0, growth_rate equals the current value: 12 meetings after a period with none shows a growth_rate of 12. Check for an empty previous period before showing it as “+1200%”.

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

start_date
string<date>

First day of the period, as YYYY-MM-DD. The period starts at 00:00:00 UTC on this date. A full timestamp is accepted, but it is converted to UTC and only the date is kept. Defaults to 7 days before end_date.

end_date
string<date>

Last day of the period, as YYYY-MM-DD, included through 23:59:59.999 UTC. A full timestamp is accepted, but it is converted to UTC and only the date is kept, so 2026-09-30T23:00:00-05:00 ends the period on 1 October. Defaults to today (UTC).

user_ids
string[]

Reps to include, by user _id from Get the current team. Repeat the parameter (user_ids=...&user_ids=...) or send one comma-separated value. Each must be a valid user ID; one that is not fails with 400. Defaults to the team's active members; pass IDs to include inactive ones.

disposition_ids
integer[]

Count only calls with these disposition IDs from List dispositions. Repeat the parameter or send one comma-separated value, for example disposition_ids=1,4. total_follow_up_tasks ignores this filter.

timezone
string

Accepted but not applied: periods are always whole UTC days.

Response

Each metric with its growth against the previous period. Not wrapped in data.

Headline metrics for the period. Each is { value, growth_rate }.

  • total_calls: Calls counted in the period.
  • total_inbound_calls: Calls with direction: inbound.
  • connected_calls: Calls with outcome: answered, answered by a person or with no answering-machine result, and a disposition ID below 10, plus every call dispositioned Gatekeeper (12) or Bad Number (13).
  • conversations: Answered calls, by a person or with no answering-machine result, with a disposition ID below 10 that either set a meeting (disposition 1) or lasted at least 60 seconds. Gatekeeper and Bad Number calls never count.
  • connection_rate: connected_calls / total_calls, a ratio from 0 to 1 rounded to two decimals.
  • conversation_rate: conversations / connected_calls, a ratio from 0 to 1 rounded to two decimals.
  • avg_calls_per_day: total_calls divided by the number of UTC days in the period with at least one call, rounded to two decimals.
  • total_call_duration: Sum of call durations, in seconds.
  • total_meetings_set: Calls dispositioned Meeting Set (disposition 1).
  • total_follow_up_tasks: Follow-up tasks the same users created in the period. Not affected by disposition_ids.
  • unique_contacts: Distinct phone numbers called (to).
  • unique_companies: Distinct non-empty contact.company values among the calls.
total_calls
object
required
total_inbound_calls
object
required
connected_calls
object
required
conversations
object
required
connection_rate
object
required
conversation_rate
object
required
avg_calls_per_day
object
required
total_call_duration
object
required
total_meetings_set
object
required
total_follow_up_tasks
object
required
unique_contacts
object
required
unique_companies
object
required