Skip to main content
The Salesfinity API is a JSON-over-HTTPS REST API for the Salesfinity parallel dialer. Use it to manage contact lists, run outbound sequences end to end, read call logs and AI call scores, pull team and SDR analytics, work with notes, and enrich phone numbers and email addresses. Everything on this page is plain text, so a person skimming, a search crawler, and an autonomous agent all get the same answer without running any JavaScript.

At a glance

Quickstart

Generate a key in the Salesfinity dashboard under Settings → Connections & API, then confirm it works by reading the team it belongs to. Every key is scoped to exactly one team, and every response is filtered to that team.
A successful call returns the team name and its members, each with a user record, a status, and a license. If the key is missing or wrong you get an HTTP 403 with a JSON body rather than an HTML error page — see Errors. Once the key works, the usual next step is to list the team’s contact lists and then read one:

Authentication

Every endpoint requires an API key in the x-api-key header. There is no OAuth flow, no bearer token, and no unauthenticated endpoint. Keys are long-lived until you revoke them in the dashboard. A missing, malformed, revoked, or wrong-team key returns HTTP 403 Forbidden, not 401. That is worth encoding in client code, because the conventional “retry auth on 401” branch will never fire against this API.
Because a key is team-scoped, requesting a resource that belongs to a different team returns 404 Not Found rather than 403 — the API does not confirm that records outside your team exist. There is no separate sandbox host. See the developer portal for how to test against live data safely.

Conventions

Errors

Every error response, on every endpoint and every status code, uses the same JSON envelope: Branch on error or statusCode rather than on message. Retry 429 and 5xx with exponential backoff; 400, 402, 403, and 404 will not succeed on an identical retry. The full envelope, per-status examples, and recovery steps are on the Errors page.

Webhooks

Webhook subscriptions are created and managed inside the Salesfinity application, not through this API. Configure them in the dashboard under Settings → Connections & API; there are no webhook endpoints to call. The enrichment endpoints are the exception: they accept a per-request callback_url rather than a standing subscription — see Enrich Email and Enrich Phone.

What you can do with the API

The REST API exposes 114 operations across 21 groups. Every operation has a unique operationId, a description, typed parameters, and a JSON response schema in the OpenAPI description.

Complete endpoint index

Every operation in the API, with its HTTP method, path, and reference page. This table is generated from the OpenAPI description, so it is always in sync with the spec.

Contact Lists

Teams

Dispositions

Sequences

Call Logs

Analytics

Snoozed Contacts

Follow-up Tasks

Custom Fields

Scored Calls

Notes

Enrichment

Sequencer Sequences

Sequencer Steps

Sequencer Templates

Sequencer Enrollments

Sequencer Enrolment Runs

Sequencer Tasks

Sequencer Suppression

Sequencer Policies

Sequencer Settings

Resources for agents and crawlers

  • /llms.txt — a compact index of every page on this site.
  • /llms-full.txt — the full documentation as a single plain-text file.
  • /api-reference/openapi.json — the complete OpenAPI 3.0.1 description, also served at /openapi.json.
  • /sitemap.xml — every canonical URL.
  • Any page also serves Markdown. Append .md to a page URL, or send Accept: text/markdown, to get the source instead of the rendered page.

Getting help

Email [email protected] or browse the help center. When reporting an API problem, include the request path, the timestamp, and the error and statusCode from the response body — that is usually enough to find the request in Salesfinity’s logs.