List snoozed contacts

curl --request GET \
  --url https://client-api.salesfinity.co/v1/snoozed-contacts \
  --header 'x-api-key: <api-key>'

const options = {method: 'GET', headers: {'x-api-key': '<api-key>'}};

fetch('https://client-api.salesfinity.co/v1/snoozed-contacts', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://client-api.salesfinity.co/v1/snoozed-contacts",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "x-api-key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://client-api.salesfinity.co/v1/snoozed-contacts"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("x-api-key", "<api-key>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://client-api.salesfinity.co/v1/snoozed-contacts")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["x-api-key"] = '<api-key>'

response = http.request(request)
puts response.read_body

{
  "data": [
    {
      "_id": "66f2b7d1c3a4e5f6a7b8c9d0",
      "team": "64f1a2b3c4d5e6f7a8b9c0d1",
      "user": {
        "_id": "680edc0d1504192884a148e0",
        "first_name": "Sam",
        "last_name": "Rivera",
        "email": "[email protected]"
      },
      "linkedin_username": "jane-doe-4b21a3",
      "external_contact_id": "0035e00000AbCdEfGh",
      "email": "[email protected]",
      "phone_number": "+14155552671",
      "snooze_until": "2026-11-02T15:00:00.000Z",
      "createdAt": "2026-10-03T14:12:09.330Z",
      "updatedAt": "2026-10-03T14:12:09.330Z"
    },
    {
      "_id": "66f2a9e0c3a4e5f6a7b8c9a7",
      "team": "64f1a2b3c4d5e6f7a8b9c0d1",
      "user": {
        "_id": "680edc0d1504192884a148e0",
        "first_name": "Sam",
        "last_name": "Rivera",
        "email": "[email protected]"
      },
      "contact_list": "6650c1f2a4b8e93d2c1f0a10",
      "email": "[email protected]",
      "phone_number": "+12125550147",
      "snooze_until": "2026-10-10T00:00:00.000Z",
      "createdAt": "2026-10-02T18:30:00.115Z",
      "updatedAt": "2026-10-02T18:30:00.115Z"
    }
  ],
  "total": 37,
  "page": 1,
  "next": 2
}

{
  "message": [
    "limit must not be greater than 100"
  ],
  "error": "Bad Request",
  "statusCode": 400,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Forbidden resource",
  "error": "Forbidden",
  "statusCode": 403,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Rate limit of 300 requests per minute exceeded. Retry in 12s.",
  "error": "Too Many Requests",
  "statusCode": 429,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Internal server error",
  "error": "Internal Server Error",
  "statusCode": 500,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

Snoozed contacts

List snoozed contacts

Returns the team’s snooze records, newest first. A rep creates a snooze by snoozing a contact from the dialer or by setting a snooze date when logging a call; there is no endpoint to create one. Each record holds the contact’s identifiers and snooze_until. When a list is imported into the dialer from the dashboard, every contact that matches a record whose snooze_until is still in the future is marked snoozed until that date. Records match on LinkedIn username first, then CRM contact ID, phone number and email.

Expired records are kept, so compare snooze_until with the current time to find active snoozes. The filters are exact, case-sensitive matches.

The page fields sit at the top level (data, total, page, next), not under pagination as in other list endpoints. sort takes one field, such as snooze_until or -createdAt; a comma-separated list passes validation but leaves the results unsorted.

GET

snoozed-contacts

List snoozed contacts

curl --request GET \
  --url https://client-api.salesfinity.co/v1/snoozed-contacts \
  --header 'x-api-key: <api-key>'

const options = {method: 'GET', headers: {'x-api-key': '<api-key>'}};

fetch('https://client-api.salesfinity.co/v1/snoozed-contacts', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://client-api.salesfinity.co/v1/snoozed-contacts",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "x-api-key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://client-api.salesfinity.co/v1/snoozed-contacts"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("x-api-key", "<api-key>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://client-api.salesfinity.co/v1/snoozed-contacts")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["x-api-key"] = '<api-key>'

response = http.request(request)
puts response.read_body

{
  "data": [
    {
      "_id": "66f2b7d1c3a4e5f6a7b8c9d0",
      "team": "64f1a2b3c4d5e6f7a8b9c0d1",
      "user": {
        "_id": "680edc0d1504192884a148e0",
        "first_name": "Sam",
        "last_name": "Rivera",
        "email": "[email protected]"
      },
      "linkedin_username": "jane-doe-4b21a3",
      "external_contact_id": "0035e00000AbCdEfGh",
      "email": "[email protected]",
      "phone_number": "+14155552671",
      "snooze_until": "2026-11-02T15:00:00.000Z",
      "createdAt": "2026-10-03T14:12:09.330Z",
      "updatedAt": "2026-10-03T14:12:09.330Z"
    },
    {
      "_id": "66f2a9e0c3a4e5f6a7b8c9a7",
      "team": "64f1a2b3c4d5e6f7a8b9c0d1",
      "user": {
        "_id": "680edc0d1504192884a148e0",
        "first_name": "Sam",
        "last_name": "Rivera",
        "email": "[email protected]"
      },
      "contact_list": "6650c1f2a4b8e93d2c1f0a10",
      "email": "[email protected]",
      "phone_number": "+12125550147",
      "snooze_until": "2026-10-10T00:00:00.000Z",
      "createdAt": "2026-10-02T18:30:00.115Z",
      "updatedAt": "2026-10-02T18:30:00.115Z"
    }
  ],
  "total": 37,
  "page": 1,
  "next": 2
}

{
  "message": [
    "limit must not be greater than 100"
  ],
  "error": "Bad Request",
  "statusCode": 400,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Forbidden resource",
  "error": "Forbidden",
  "statusCode": 403,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Rate limit of 300 requests per minute exceeded. Retry in 12s.",
  "error": "Too Many Requests",
  "statusCode": 429,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

{
  "message": "Internal server error",
  "error": "Internal Server Error",
  "statusCode": 500,
  "request_id": "0f6d3c52-9f3e-4c1a-a4b8-2b1f7e5d9c10"
}

Returns your team’s snooze records, newest first.

How snoozing works

A rep snoozes a contact from the dialer, or sets a snooze date when logging a call. Each snooze is a record holding the contact’s identifiers (LinkedIn username, CRM contact ID, phone number and email) and snooze_until. There is no endpoint to create one.
When a rep imports a list into the dialer from the dashboard, every contact that matches a record whose snooze_until is still in the future is marked snoozed until that date. Records match across the whole team, on LinkedIn username first, then CRM contact ID, phone number and email.
Reimport a contact list into the dialing queue copies saved contacts without these markings.
Expired records are not deleted. They stay in this list after snooze_until has passed.

Example

curl 'https://client-api.salesfinity.co/v1/[email protected]&sort=-snooze_until' \
  --header 'x-api-key: YOUR_API_KEY'

{
  "data": [
    {
      "_id": "66f2b7d1c3a4e5f6a7b8c9d0",
      "team": "64f1a2b3c4d5e6f7a8b9c0d1",
      "user": {
        "_id": "680edc0d1504192884a148e0",
        "first_name": "Sam",
        "last_name": "Rivera",
        "email": "[email protected]"
      },
      "linkedin_username": "jane-doe-4b21a3",
      "external_contact_id": "0035e00000AbCdEfGh",
      "email": "[email protected]",
      "phone_number": "+14155552671",
      "snooze_until": "2026-11-02T15:00:00.000Z",
      "createdAt": "2026-10-03T14:12:09.330Z",
      "updatedAt": "2026-10-03T14:12:09.330Z"
    }
  ],
  "total": 1,
  "page": 1,
  "next": null
}

The page fields sit at the top level (total, page, next), not under pagination as in List contact lists and List follow-up tasks.

user is the rep who created the snooze. contact_list appears only on snoozes set from the dialer’s contact table.

Filtering, sorting and paging

Each filter is an exact, case-sensitive match. Filters combine: a record must match all of them.
Expired records are included. To get active snoozes, keep the records whose snooze_until is later than now.
sort takes one field, such as snooze_until or -createdAt. A comma-separated list passes validation but leaves the results unsorted.
limit defaults to 10. Above 100 is treated as 100, and limit in the response says what was used. Request pages with page until next is null.

Errors

Status	When
400	`limit` or `page` is below 1, `sort` is malformed, or the query has a parameter this endpoint does not define, such as `search`.

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

page

integer

default:1

Page number, starting at 1.

Required range: x >= 1

limit

integer

Records per page. Default 10. Above 100 is treated as 100; below 1 fails with 400.

Required range: 1 <= x <= 100

sort

string

One field to sort by, such as snooze_until, createdAt or email. Prefix with - for descending. A comma-separated list passes validation but leaves the results unsorted. Defaults to -createdAt.

Example:

"snooze_until"

linkedin_username

string

Only records with exactly this LinkedIn username (case-sensitive).

Example:

"jane-doe-4b21a3"

external_contact_id

string

Only records with exactly this CRM contact ID.

Example:

"0035e00000AbCdEfGh"

string

Only records with exactly this email (case-sensitive).

Example:

"[email protected]"

phone_number

string

Only records with exactly this phone number, as stored (usually E.164).

Example:

"+14155552671"

Response

One page of snooze records.

data

object[]

Show child attributes

total

integer

Records across all pages that match the filters.

page

integer

The page returned, 1-based.

limit

integer

The page size used: your limit, or the default, and never more than the maximum.

Example:

10

integer | null

The next page number, or null on the last page.

Get started

MCP server

MCP reference

MCP use cases

Dialer API

Calls and analytics API

Enrichment API

Sequencer API

List snoozed contacts

How snoozing works

Example

Filtering, sorting and paging

Errors

Authorizations

Query Parameters

Response

​How snoozing works

​Example

​Filtering, sorting and paging

​Errors

Authorizations

Query Parameters

Response

How snoozing works

Example

Filtering, sorting and paging

Errors