Skip to content
telipot
telipot
Join the waitlistSign in

Saved contacts in the account by keyword, stage or label.

Use the search for contacts endpoint to search for the contacts that have been added to your team's Apollo account.

Job people.contacts.search

Your AI asks

choose input values first
telipot inspect apollo.people.contacts.search

Provider's rate

Free
Inspect· before choosing inputs

apollo.people.contacts.search

FreeYour plan

Whose account it uses

1The person asking
not needed
2Your company’s Apollo plan
Selected identity for this example
3Our account
not used

Choose inputs

q_keywords · Keywords over names, job titles, employers or company names, or email addresses. Examples: CEO; Sumware Software.

contact_stage_ids · Apollo IDs of contact stages; a contact matches any one. List contact stages returns the IDs.

No complete example input is recorded. Inspect reads the schema; it does not run the task.

What it costs

Free

no charge from the provider

For developers · inspect first

Read the schema and choose input values

telipot inspect apollo.people.contacts.search

No complete example input is recorded. Read the field notes below before building the call.

q_keywords

string

Keywords over names, job titles, employers or company names, or email addresses. Examples: CEO; Sumware Software.

contact_stage_ids

array

Apollo IDs of contact stages; a contact matches any one. List contact stages returns the IDs.

contact_label_ids

array

Apollo IDs of labels; a contact matches any one.

sort_by_field

string · one of "contact_last_activity_date", "contact_email_last_opened_at", "contact_email_last_clicked_at", "contact_created_at", "contact_updated_at"

Sort field, most recent first.

sort_ascending

boolean · default false

Set true for ascending order; needs sort_by_field.

per_page

integer · 1 to 100

Results per page, up to 100.

page

integer · 1 to 500

Page to return, up to 500 pages of 100; use with per_page.

contacts

object[]

pagination

object

Full output schema · JSONNested fields and constraints

Output JSON Schema

{
  "type": "object",
  "properties": {
    "contacts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "first_name": {
            "type": "string"
          },
          "last_name": {
            "type": "string"
          },
          "name": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "email_status": {
            "type": "string"
          },
          "linkedin_url": {
            "type": [
              "string",
              "null"
            ]
          },
          "organization_name": {
            "type": "string"
          },
          "organization_id": {
            "type": "string"
          },
          "account_id": {
            "type": "string"
          },
          "contact_stage_id": {
            "type": "string"
          },
          "owner_id": {
            "type": "string"
          },
          "source": {
            "type": "string"
          },
          "created_at": {
            "type": "string"
          },
          "updated_at": {
            "type": "string"
          },
          "label_ids": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "phone_numbers": {
            "type": "array"
          }
        }
      }
    },
    "pagination": {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer"
        },
        "per_page": {
          "type": "integer"
        },
        "total_entries": {
          "type": "integer"
        },
        "total_pages": {
          "type": "integer"
        }
      }
    }
  }
}

A real answer

No example captured yet: one is recorded when telipot catalog verify passes.