> ## Documentation Index > Fetch the complete documentation index at: https://docs.seamless.ai/llms.txt > Use this file to discover all available pages before exploring further. # Search contacts ## OpenAPI ````yaml https://gist.githubusercontent.com/JustinAlia/6ff38a671f5f79895444b77c57f3afff/raw/v2-openapi.json post /search/contacts openapi: 3.0.0 info: title: Seamless API description: >- [Privacy Policy](https://seamless.ai/policies/privacy-policy) In order to dramatically improve our offerings to customers, Seamless will be introducing a Public API which can be used to search Companies & Contacts, Enrich Lists, and offer integrations as an Endpoint for our customers. The API is build using [RESTful](https://en.wikipedia.org/wiki/REST) principles and is secured using OAuth 2.0 with the implicit grant flow. # Authentication ## API Key ### 1. **Register Your Application** To use the Seamless API, you need to register your application to obtain an API key. To create a new API key, go to [Seamless.AI | Settings](https://login.seamless.ai/settings/public-api) > API Key and click the *Create New Connection* button. Note: The Public API Connections menu will only appear if your account has access to the Public API. ### 2. **Use the Access Token** For all authenticated API requests, include the API key in the header: ``` Token: API_KEY ``` ## OAuth 2.0 ### 1. **Register Your Application** Before integrating, you have to setup your client credentials. To create a new API client, go to [Seamless.AI | Settings](https://login.seamless.ai/settings/public-api) > OAuth Connections, and click the *Create New Connection* button. Note: The Public API Connections menu will only appear if your account has access to the Public API. - `client_id` - `client_secret` - `redirect_uri` You’ll use these to authenticate and obtain tokens. --- ### 2. **Obtain Authorization Code** Redirect the user to Seamless.AI's OAuth authorization endpoint: ``` GET https://login.seamless.ai/oauth/authorize ``` ### Query Parameters: | Name | Description | | --- | --- | | `client_id` | Your client ID | | `redirect_uri` | The URL users are redirected to | | `state` | (Optional) CSRF protection string | **Example URL**: ``` GET https://login.seamless.ai/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=https://yourapp.com/callback ``` Once the user authenticates, they will be redirected to your `redirect_uri` with a `code` parameter. If your `redirect_uri` contains any query parameters (such as `?foo=bar`), you must URL encode your `redirect_uri` for this step. --- ### 3. **Exchange Code for Access Token** ``` POST https://api.seamless.ai/api/client/v2/oauth/accessToken ``` ### Request Body (JSON): ```json { "client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_CLIENT_SECRET", "redirect_uri": "https://yourapp.com/callback", "grant_type": "authorization_code", "code": "AUTHORIZATION_CODE_FROM_STEP_2" } ``` ### Response: ```json { "token_type": "Bearer", "access_token": "ACCESS_TOKEN", "refresh_token": "REFRESH_TOKEN", "expires_in": 10800, "expires_at": "2026-06-25T12:00:00.000Z", "refresh_token_expires_in": 604800, "refresh_token_expires_at": "2026-07-02T12:00:00.000Z" } ``` Access tokens expire after **180 minutes** by default. Integrations must use the `refresh_token` grant before expiry to obtain a new token pair. Existing long-lived tokens issued before this change remain valid until their original expiry. --- ### 4. **Use the Access Token** For all authenticated API requests, include the token in the header: ``` Authorization: Bearer ACCESS_TOKEN ``` --- ### 5. **Refreshing the Token** To refresh the access token: ``` POST https://api.seamless.ai/api/client/v2/oauth/accessToken ``` ### Request Body: ```json { "client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_CLIENT_SECRET", "redirect_uri": "https://yourapp.com/callback", "grant_type": "refresh_token", "refresh_token": "YOUR_REFRESH_TOKEN" } ``` ### Response: ```json { "token_type": "Bearer", "access_token": "NEW_ACCESS_TOKEN", "refresh_token": "NEW_REFRESH_TOKEN", "expires_in": 10800, "expires_at": "2026-06-25T12:00:00.000Z", "refresh_token_expires_in": 604800, "refresh_token_expires_at": "2026-07-02T12:00:00.000Z" } ``` Each refresh rotates both the access and refresh tokens. Store the new `refresh_token` from every response. # Rate Limiting Rate limits are enforced at the **organization** level. All API usage for your Seamless organization counts against the same quota for each endpoint—limits are not applied separately per API key or per user. The default limit is **60 requests per minute** per endpoint. If you exceed the limit, the API responds with **429 Too Many Requests** and a JSON error body. Some endpoints may use different limits (for example, OAuth routes). Your organization may also have custom limits. The `X-RateLimit-Limit` header on each response always reflects the maximum number of requests allowed for that endpoint in the current rate limit window. Rate limit and remaining credits information will be returned in the response header of each request. The parameters are: | Name | Example | Description | | --- | --- | --- | | `X-RateLimit-Limit` | 60 | The maximum number of requests you're permitted to make in the current rate limit window for this endpoint. | | `X-RateLimit-Remaining` | 42 | The number of requests remaining in the current rate limit window. | | `X-RateLimit-Reset` | 1745587198 | The time at which the current rate limit window resets in epoch seconds. | | `X-PublicAPI-Credits` | 1000 | The number of credits remaining that can be used in requests. | version: 1.0.0 x-logo: url: https://s3.amazonaws.com/seamless.ai-public/logos/logo-full-dark.svg altText: Seamless logo href: https://login.seamless.ai termsOfService: https://seamless.ai/policies/terms-of-use servers: - url: https://api.seamless.ai/api/client/v2 description: Seamless API security: - OAuth2: [] - ApiKeyAuth: [] tags: - name: OAuth description: >- Exchange client credentials for an access token and inspect the authenticated caller. - name: Contact Search description: >- Search the Seamless.AI contact database. Searching does not consume credits; researching a result does. - name: Company Search description: >- Search the Seamless.AI company database. Searching does not consume credits; researching a result does. - name: Contact Research description: >- Resolve a contact's emails and phone numbers. Research is asynchronous: submit a request, then poll for results or receive them by webhook. - name: Company Research description: >- Resolve company firmographics and contact details. Research is asynchronous: submit a request, then poll for results or receive them by webhook. - name: Org Contacts description: >- Read and update the contacts already saved to your organization. These are the records research writes to, and the IDs other endpoints expect. - name: Org Companies description: Read and update the companies already saved to your organization. - name: Campaigns description: >- Create and run multi-step outbound campaigns, manage their steps, and enroll or remove contacts. - name: Emails description: Compose, preview, send, and track emails, individually or in bulk. - name: Tasks description: Read and act on the tasks a campaign generates for its assigned user. - name: Lists description: Group saved contacts and companies into named lists. - name: Templates description: Reusable email templates available to campaigns and one-off sends. - name: Saved Searches description: Persist search filters so a search can be re-run or shared later. - name: Calls description: >- Log call outcomes against saved contacts, and read the disposition and sentiment vocabularies. - name: Activity description: A chronological feed of engagement activity across your organization. - name: Credits description: Remaining research credits for the authenticated organization. - name: Features description: Feature access flags for the authenticated organization. - name: Reference description: >- Static lookup data — locations, statuses, and other vocabularies other endpoints accept. paths: /search/contacts: post: tags: - Contact Search summary: Search contacts operationId: searchContacts requestBody: required: true content: application/json: schema: type: object example: nextToken: null limit: 50 contactCountry: - United States contactZipCode: - '10001' locationType: bothOR department: - IT - Engineering industry: - Software Development jobTitle: - Chief Technology Officer seniority: - C-Level - VP companyFoundedOn: - Last 4-10 Years companySize: - 201 - 500 companyRevenue: - $5M - $20M technologies: - Salesforce technologiesIsOr: true lastModifiedAfter: '2025-09-01T11:00:00Z' properties: nextToken: description: >- An opaque cursor token for retrieving the next page of results. Returned as `supplementalData.nextToken` in the previous response. type: string default: null nullable: true limit: description: > The maximum number of contacts to return per page. Must be a positive integer. A larger value is reduced to 500 rather than rejected. type: integer default: 50 maximum: 500 example: 50 page: description: > Page number for offset-based pagination, starting at 1. `nextToken` is the preferred way to page through results and takes precedence when both are sent. type: integer default: 1 example: 2 savedSearchId: description: >- Run the filters held by a saved search instead of sending them. Get the id from `GET /saved-searches`. The saved search must be a contact search. Cannot be combined with any other filter; doing so returns a validation error. `limit`, `page` and `nextToken` are still accepted. type: integer example: 1234 companyName: description: >- Filter contacts by their company name. Accepts up to 100 company names. type: array items: type: string maxItems: 100 example: - Seamless.AI companyNameSearchType: description: > Controls how `companyName` values are matched. `default` matches the provided name using standard relevance matching. `related` broadens the search to include known subsidiaries, parent companies, and brand aliases. `exact` restricts results to only companies whose name is an exact match. type: string enum: - default - related - exact default: default example: default companyDomain: description: >- Filter contacts by their company's website domain. Accepts up to 100 domains. type: array items: type: string maxItems: 100 example: - seamless.ai contactState: description: > Filter by the contact's or company's state or region. Accepts a US state name or abbreviation and non-US subdivisions alike (`"CA"`, `"California"`, `"Ontario"`). A US state matches under either spelling whichever one you send. Prefix a value with `-` to exclude it. Behavior depends on the `locationType` parameter. Values match a fixed vocabulary of place names spelled the way our data spells them, which is usually the English exonym — Germany's state is `"Bavaria"`, not `"Bayern"`. US state names and abbreviations are both resolved, so neither needs a lookup. Use `GET /search/locations` to find the spelling for anything else; a value the vocabulary does not hold matches no contacts and comes back under `warnings`, with suggestions, rather than as an error. type: array items: type: string maxItems: 10 example: - California - New York contactCountry: description: > Filter by the contact's or company's country. Prefix a value with `-` to exclude it. Behavior depends on the `locationType` parameter, and values are combined with `locations` rather than replacing it. `"US"`, `"USA"` and `"United States of America"` all resolve to the United States. Use `GET /search/locations?types=country` to find any other country's spelling; a value the vocabulary does not hold matches no contacts and comes back under `warnings`, with suggestions, rather than as an error. type: array items: type: string maxItems: 10 example: - United States contactZipCode: description: > Filter by the contact's or company's zip/postal code. Prefix a value with `-` to exclude it. Behavior depends on the `locationType` parameter. Any zip/postal code is accepted; the values below are only examples. type: array items: type: string maxItems: 10 example: - '10001' locations: description: > Free-form location filter — city, state/region, or country — and the only filter that reaches city-level matching. Values may be a single place (`"Austin"`) or comma-separated to disambiguate (`"Austin, Texas"`, `"Ontario, Canada"`). Prefix a value with `-` to exclude it. Behavior depends on the `locationType` parameter, and values are combined with `contactCountry` rather than replacing it. Cities are the largest part of the vocabulary and the part no list can enumerate — use `GET /search/locations` to find one, and pass the returned `location` string verbatim. Its `count` is what separates a name meaning several places: `"Ontario"` is a Canadian province and a larger California city. type: array items: type: string maxItems: 10 example: - Austin, Texas - '-Dallas, Texas' locationRadius: description: > Widen `locations` (and `contactCountry`) to everything within a radius of each value. The value is the radius in miles, sent as a string or a number. Only geocodable values get a radius — a city or zip code resolves to coordinates, a country does not. Use `zipCodesRadius` for `contactZipCode`. This is the form `GET /saved-searches` reads a radius back in, so those values can be sent straight through here. The spelled-out label (`25 miles`) is accepted too, as are the options `1`, `2`, `3`, and `4` this filter originally took, which mean 25, 50, 100, and 250 miles respectively. type: string enum: - '25' - '50' - '100' - '250' default: null nullable: true example: '50' zipCodesRadius: description: > Widen `contactZipCode` to everything within a radius of each zip code. The value is the radius in miles, sent as a string or a number. The spelled-out label (`25 miles`) is accepted too, as are the options `1`, `2`, `3`, and `4` this filter originally took, which mean 25, 50, 100, and 250 miles respectively. type: string enum: - '25' - '50' - '100' - '250' default: null nullable: true example: '25' locationType: description: > Determines how location filters (`locations`, `contactState`, `contactCountry`, `contactZipCode`) are applied. `contact` matches the contact's personal location only. `company` matches the company's headquarters location only. `bothOR` matches if either the contact or the company location matches (default). `bothAND` matches only when both the contact and the company location match. type: string enum: - bothOR - bothAND - company - contact default: bothOR example: bothOR timezones: description: >- Filter by timezone. Up to 10 timezones can be specified. Behavior depends on the `timezoneType` parameter. type: array items: type: string enum: - Eastern (EST) - Central (CST) - Mountain (MST) - Pacific (PST) - Alaska (AKST) - Hawaii (HST) - New Zealand (NST) - Solomon (SST) - Australia Eastern (AET) - Australia Central (ACT) - Japan (JST) - China Taiwan (CTT) - Vietnam (VST) - Bangladesh (BST) - India (IST) - Indiana Eastern (IET) - Pakistan Lahore (PLT) - Near East (NET) - Middle East (MET) - Eastern African (EAT) - (Arabic) Egypt (ART) - Eastern European (EET) - European Central (ECT) - Greenwich Mean (GMT) - Central African (CAT) - Argentina (AGT) - Brazil Eastern (BET) - Canada Newfoundland (CNT) - Puerto Rico and US Virgin Islands (PRT) - Midway Islands (MIT) maxItems: 10 example: - Eastern (EST) - Central (CST) timezoneType: description: > Determines how the `timezones` filter is applied, using the same semantics as `locationType`. Ignored unless `timezones` is provided. type: string enum: - bothOR - bothAND - company - contact default: bothOR example: bothOR department: description: >- Filter contacts by organizational department. Up to 5 departments can be specified. type: array items: type: string enum: - Sales - Marketing - Engineering - Human Resources - Finance - IT - Operations - Support - Legal - Project Management - Other maxItems: 5 example: - IT - Engineering industry: description: >- Filter contacts by their company's industry classification. Up to 5 industries can be specified. Values are organized into parent categories (e.g., "Software & Information Technology") and specific sub-industries (e.g., "Computer Software"). type: array items: type: string enum: - Aerospace & Defense - Airlines & Aviation - Aviation & Aerospace - Defense & Space - Military - Agriculture - Farming - Horticulture - Ranching - Tobacco - Apparel & Fashion - Textiles - Automotive - Chemicals & Materials - Chemicals - Plastics - Consumer Goods & Retail - Consumer Goods - Luxury Goods & Jewelry - Retail - Sporting Goods - Education & Training - E-Learning - Education Management - Higher Education - Libraries - Primary/Secondary Education - Electronics & Hardware - Computer Hardware - Consumer Electronics - Electrical & Electronic Manufacturing - Semiconductors - Energy & Utilities - Oil & Energy - Utilities - Entertainment - Animation - Arts & Crafts - Computer Games - Fine Art - Gambling & Casinos - Mobile Games - Motion Pictures & Film - Music - Performing Arts - Photography - Recreational Facilities & Services - Sports - Environmental - Environmental Services - Renewables & Environment - Finance & Banking - Banking - Capital Markets - Financial Services - Investment Banking - Investment Management - Venture Capital & Private Equity - Food & Beverage - Dairy - Fishery - Food & Beverages - Food Production - Restaurants - Supermarkets - Wine & Spirits - Government & Public Policy - Executive Office - Government Administration - Government Relations - Judiciary - Law Enforcement - Legislative Office - Political Organization - Public Policy - Public Safety - Health & Wellness - Alternative Medicine - Health, Wellness and Fitness - Hospital & Health Care - Medical Practice - Mental Health Care - Veterinary - Hospitality & Tourism - Events Services - Hospitality - Leisure, Travel & Tourism - Museums & Institutions - Household, Personal, & Beauty - Consumer Services - Cosmetics - Furniture - Individual & Family Services - Insurance - Internet & E-Commerce - Internet - Manufacturing & Engineering - Civil Engineering - Industrial Automation - Machinery - Mechanical or Industrial Engineering - Railroad Manufacture - Shipbuilding - Marketing & Media - Broadcast Media - Graphic Design - Marketing & Advertising - Media Production - Newspapers - Online Media - Printing - Public Relations & Communications - Publishing - Writing & Editing - Metals, Mining & Materials - Building Materials - Glass, Ceramics & Concrete - Mining & Metals - Paper & Forest Products - Non-Profit - Fund-Raising - Non-Profit Organization Management - Philanthropy - Religious Institutions - Pharmaceuticals & Medical Devices - Biotechnology - Medical Devices - Nanotechnology - Pharmaceuticals - Professional Services & Consulting - Accounting - Alternative Dispute Resolution - Civic & Social Organization - Design - Human Resources - International Affairs - International Trade & Development - Law Practice - Legal Services - Management Consulting - Market Research - Outsourcing/Offshoring - Professional Training & Coaching - Program Development - Research - Security & Investigations - Staffing & Recruiting - Think Tanks - Real Estate & Construction - Architecture & Planning - Commercial Real Estate - Construction - Facilities Services - Real Estate - Software & Information Technology - Computer & Network Security - Computer Software - Information Services - Information Technology & Services - Software Development - Telecommunications & Networking - Computer Networking - Telecommunications - Wireless - Transportation & Logistics - Logistics & Supply Chain - Maritime - Package/Freight Delivery - Packaging & Containers - Translation & Localization - Transportation/Trucking/Railroad - Wholesale & Distribution - Business Supplies & Equipment - Import & Export - Warehousing - Wholesale maxItems: 5 example: - Software Development industrySicCodes: description: > Filter contacts by their company's SIC code. Applied independently of `industry`, so the two can be combined or used on their own. Prefix a value with `-` to exclude it. Up to 5 codes can be specified. type: array items: type: string maxItems: 5 example: - '7372' industryNaicsCodes: description: > Filter contacts by their company's NAICS code. Applied independently of `industry`, so the two can be combined or used on their own. Prefix a value with `-` to exclude it. Up to 5 codes can be specified. On API v2, unrecognized codes are rejected with a validation error. type: array items: type: string maxItems: 5 example: - '511210' fullName: description: >- Filter contacts by full name. Useful for finding specific individuals. Up to 10 names can be specified. type: array items: type: string maxItems: 10 example: - John Smith contactKeyword: description: >- Filter contacts by keyword matches against their profile (e.g., skills, bio, specialties). Up to 10 keywords can be specified. type: array items: type: string maxItems: 10 example: - sales enablement keywordsIsOr: description: > Controls how multiple `contactKeyword` values are combined. When `false` (default), a contact must match all of the keywords (AND logic). When `true`, matching any one of them is enough (OR logic). type: boolean default: false example: false jobTitle: description: >- Filter contacts by job title. Matches are based on relevance to the provided title strings. Up to 10 titles can be specified. type: array items: type: string maxItems: 10 example: - Chief Technology Officer titlesExactMatch: description: > Controls how `jobTitle` values are matched. When `false` (default), titles match on relevance, so `"VP of Sales"` also matches `"Vice President, Sales"`. When `true`, only exact title matches are returned. type: boolean default: false example: false seniority: description: >- Filter contacts by seniority level within their organization. Up to 5 values can be specified. type: array items: type: string enum: - C-Level - VP - Director - Manager - Senior - Entry Level - Mid-Level - Other maxItems: 5 example: - C-Level - VP companyFoundedOn: description: >- Filter contacts by how recently their company was founded. Up to 4 ranges can be specified. type: array items: type: string enum: - Less than 1 Year - Last 1-3 Years - Last 4-10 Years - 10+ Years maxItems: 4 example: - Less than 1 Year - Last 1-3 Years companySize: description: >- Filter contacts by their company's employee count range. Up to 10 ranges can be specified. type: array items: type: string enum: - 0 - 1 (Self-employed) - 2 - 10 - 11 - 50 - 51 - 200 - 201 - 500 - 501 - 1,000 - 1,001 - 5,000 - 5,001 - 10,000 - 10,001+ maxItems: 10 example: - 201 - 500 companyRevenue: description: >- Filter contacts by their company's estimated annual revenue range. Up to 10 ranges can be specified. type: array items: type: string enum: - $0 - $100K - $100K - $1M - $1M - $5M - $5M - $20M - $20M - $50M - $50M - $100M - $100M - $500M - $500M - $1B - $1B+ maxItems: 10 example: - $5M - $20M technologies: description: >- Filter contacts by technologies used at their company. Up to 10 technologies can be specified. Sample enum values shown for documentation only; actual values are not exhaustive and come from the API or typeahead. type: array items: type: string enum: - Salesforce - HubSpot - Marketo - Outreach - Apollo maxItems: 10 example: - Salesforce technologiesIsOr: description: >- Controls how multiple `technologies` values are combined. When `true` (default), returns contacts whose company uses any of the specified technologies (OR logic). When `false`, returns only contacts whose company uses all of the specified technologies (AND logic). type: boolean default: true example: true jobChanges: type: object description: | Filter contacts by job change activity. nullable: true default: null properties: changeType: type: string description: > Filters the job change by it's classification. Job Change classifications are made by `changeType` and can differ based on optionally provided `dayRange`. `New Hire` = contacts who joined a new company. `New Promotion` = contacts who received a new title at the same company. `New Hire or New Promotion` = either. enum: - New Hire - New Promotion - New Hire or New Promotion nullable: true default: null example: New Hire dayRange: type: string description: Rolling lookback window for the job change. enum: - Last 60 Days - Last 90 Days - Last 180 Days - Last 365 Days nullable: true default: null example: Last 90 Days pastCompany: type: object nullable: true description: > Filter contacts by past employer. When provided, `names` must be non-empty. `names` always match on relevance, so aliases and name fragments also match. default: null required: - names properties: names: type: array items: type: string minItems: 1 maxItems: 100 description: >- One or more company names to match against the contact's employment history. example: - Acme Inc onlyMostRecentDeparture: type: boolean default: false description: > When `true`, only matches contacts whose most recent departure was from one of the specified companies. When `false` (default), matches any contact who has ever worked at any of the specified companies (searches full job history). companyType: type: string description: > Filter by company type. `Public` = companies with a known stock ticker/exchange, `Private` = all others. enum: - Public - Private default: null nullable: true example: Public lastModifiedAfter: description: >- Return only contacts whose core data (name, title, company, phone, or email) was last updated on or after this date. Use ISO 8601 format. type: string format: date-time example: '2025-09-01T11:00:00Z' lastModifiedBefore: description: >- Return only contacts whose core data (name, title, company, phone, or email) was last updated on or before this date. Use ISO 8601 format. Combine with `lastModifiedAfter` to define a date range. type: string format: date-time example: '2025-09-07T11:00:00Z' newsTypes: description: >- Filter contacts by recent news or events at their company. Returns contacts whose company has been associated with the specified event types. Up to 8 types can be specified. type: array items: type: string enum: - Acquisition - Corporate Challenges - Cost Cutting - Expansion - Investment - Leadership - Partnership - Recognition maxItems: 8 example: - Acquisition - Expansion newsTypeDates: description: >- Restrict `newsTypes` results to a rolling window of recent days. Accepts a single value representing the number of days to look back. Only the first value is used if multiple are provided. type: array items: type: string enum: - '60' - '90' - '180' - '365' maxItems: 1 example: - '60' companyLatestFundingDates: type: array items: type: string enum: - '90' - '180' - '365' - '1095' description: >- Filter companies based on the date of their latest funding round (90, 180, 365 days or 3 years). example: - '90' maxItems: 1 companyLatestFundingClassifications: type: array items: type: string enum: - Angel - Pre-Seed - Seed - Series A - Series B - Series C - Series D - Series E - Series F - Series G - Series H - Series I - Series J - Other description: >- Filter companies based on the classifications of their latest funding round. example: - Series A - Seed maxItems: 14 companyLatestFundingTotals: type: array items: type: string enum: - $0 - $100K - $100K - $1M - $1M - $5M - $5M - $20M - $20M - $50M - $50M - $100M - $100M - $500M - $500M - $1B - $1B+ description: >- Filter companies based on the total funding amount they have raised. example: - $0 - $100K - $100K - $1M maxItems: 9 emailAddress: description: > **Requires API v2.** Filter contacts by email address. Finds contacts matching these email addresses. Accepts a single email string or an array of up to 100 emails. type: array items: type: string format: email maxItems: 100 example: - john.smith@example.com phoneNumber: description: > **Requires API v2.** Filter contacts by phone number. Accepts any format (e.g. "+1 (555) 123-4567"); non-digit characters are stripped automatically. Accepts a single phone number string or an array of up to 100 phone numbers. type: array items: type: string maxItems: 100 example: - +1 (555) 123-4567 responses: '200': description: Contact Search Results content: application/json: schema: type: object properties: data: description: A list of contacts type: array items: type: object description: >- A contact search result. Any field may be `null` when the underlying record lacks that attribute — search and research results are sparse, so treat every field below as optional and nullable. properties: searchResultId: description: >- Unique identifier for this search result. Use this ID when submitting contacts for research via the research endpoint. type: string example: 708dbb34-3849-3c06-abd1-238b9a0295b3 fullName: description: >- The contact's full name. Same vocabulary as the `fullName` search filter. type: string nullable: true example: Taylor Gonsalves name: deprecated: true description: >- Deprecated alias for `fullName`. Prefer `fullName`, which matches the search filter of the same name. type: string nullable: true example: Taylor Gonsalves companyName: description: >- The name of the company where the contact is currently employed. Same vocabulary as the `companyName` search filter. type: string nullable: true example: Seamless company: deprecated: true description: >- Deprecated alias for `companyName`. Prefer `companyName`, which matches the search filter of the same name. type: string nullable: true example: Seamless jobTitle: description: >- The contact's current job title. Same vocabulary as the `jobTitle` search filter. type: string nullable: true example: Customer Success Manager, Mid Market Accounts title: deprecated: true description: >- Deprecated alias for `jobTitle`. Prefer `jobTitle`, which matches the search filter of the same name. type: string nullable: true example: Customer Success Manager, Mid Market Accounts department: description: >- The organizational department the contact belongs to. type: string nullable: true example: Sales seniority: description: >- The contact's seniority level within their organization. type: string nullable: true example: Manager domain: description: The primary website domain of the contact's company. type: string nullable: true example: seamless.ai city: description: The city where the contact is located. type: string nullable: true example: Jacksonville state: description: The state or region where the contact is located. type: string nullable: true example: Florida country: description: The country where the contact is located. type: string nullable: true example: United States companyCity: description: >- The city where the contact's company headquarters is located. type: string nullable: true example: Columbus companyState: description: >- The state or region where the contact's company headquarters is located. type: string nullable: true example: Ohio companyCountry: description: >- The country where the contact's company headquarters is located. type: string nullable: true example: United States liUrl: description: The contact's LinkedIn profile URL. type: string nullable: true format: uri example: >- https://www.linkedin.com/in/taylor-gonsalves-b9b18b196 companyLIProfileUrl: description: >- The LinkedIn company page URL for the contact's employer. type: string nullable: true format: uri example: https://linkedin.com/company/seamlessai sicCode: description: >- The Standard Industrial Classification (SIC) code for the contact's company. type: string nullable: true example: '7389' naicsCode: description: >- The North American Industry Classification System (NAICS) code for the contact's company. type: string nullable: true example: '541512' industries: description: >- A list of industries associated with the contact's company. type: array nullable: true items: type: string example: - Software Development - Computer Software startedAtCurrentCompany: description: >- The date the contact started working at their current company (ISO 8601 date format). type: string nullable: true format: date example: '2024-04-01' titleStartedAt: description: >- The date the contact started their current job title (ISO 8601 date format). type: string nullable: true format: date example: '2024-04-01' timeAtRole: description: >- Human-readable tenure in the contact's current role, derived from `titleStartedAt` (e.g. "1 Yr 2 Mo", "3 Mo"). type: string nullable: true example: 1 Yr 2 Mo timeAtCompany: description: >- Human-readable tenure at the contact's current company, derived from `startedAtCurrentCompany` (e.g. "1 Yr 2 Mo", "3 Mo"). type: string nullable: true example: 1 Yr 2 Mo companyFoundedOn: description: >- The date the contact's company was founded (ISO 8601 date format). type: string nullable: true format: date example: '2018-01-01' companyRevenue: description: >- The estimated annual revenue range of the contact's company. Returned when the contact has been enriched. type: string nullable: true example: $5M - $20M companySize: description: >- The estimated employee count range of the contact's company. Same vocabulary as the `companySize` search filter. type: string nullable: true example: 201 - 500 employeeSizeRange: deprecated: true description: >- Deprecated alias for `companySize`. Prefer `companySize`, which matches the search filter of the same name. type: string nullable: true example: 201 - 500 timezone: description: The contact's local timezone. type: string nullable: true example: Eastern (EST) firstName: description: >- The contact's first name. Returned when the contact has been enriched. type: string nullable: true example: Taylor middleName: description: >- The contact's middle name, if available. Returned when the contact has been enriched. type: string nullable: true example: James lastName: description: >- The contact's last name. Returned when the contact has been enriched. type: string nullable: true example: Gonsalves companyDomainAlias: description: >- An alternative domain alias for the contact's company, if one exists. Returned when the contact has been enriched. type: string nullable: true example: seamless.com contactLIRecruiterUrl: description: >- The contact's LinkedIn Recruiter profile URL. Returned when the contact has been enriched. type: string nullable: true format: uri example: >- https://www.linkedin.com/talent/search/profile/AEMAAC3xxOcBgZ5bzU1FB2g9fsiZ04QNuvnv51k contactLISalesNavUrl: description: >- The contact's LinkedIn Sales Navigator profile URL. Returned when the contact has been enriched. type: string nullable: true format: uri example: >- https://www.linkedin.com/sales/lead/ACoAAC3xxOcB-G4e6iCxOPRDtiJ5RKGoeWMqfFI,NAME_SEARCH contactXUrl: description: >- The contact's X (Twitter) profile URL. Returned when the contact has been enriched. type: string nullable: true format: uri example: https://twitter.com/taylorgonsalves companyGRURL: description: >- A Google search URL for the contact's name combined with their company name. Returned when the contact has been enriched. type: string nullable: true format: uri example: >- https://www.google.com/search?q=Taylor%20Gonsalves%20Seamless contactCurrentCompanyYears: description: >- The number of years the contact has been at their current company. Returned when the contact has been enriched. type: string nullable: true example: '2' contactFBUrl: description: >- A Facebook people-search URL for the contact's name. Returned when the contact has been enriched. type: string nullable: true format: uri example: https://www.facebook.com/public/Taylor+Gonsalves contactGURL: description: >- A Google search URL for the contact's name. Returned when the contact has been enriched. type: string nullable: true format: uri example: https://www.google.com/search?q=Taylor+Gonsalves companyXUrl: description: >- An X (Twitter) search URL for the contact's company name. Returned when the contact has been enriched. type: string nullable: true format: uri example: https://twitter.com/search?q=Seamless companyFBUrl: description: >- A Facebook search URL for the contact's company name. Returned when the contact has been enriched. type: string nullable: true format: uri example: https://www.facebook.com/search/top/?q=Seamless newsAndEvents: type: array nullable: true description: Recent news articles related to the company. items: type: object properties: title: description: The headline of the news article. type: string nullable: true url: description: The URL to the full news article. type: string nullable: true date: description: The date the news article was published. type: string nullable: true format: date-time type: description: >- The type of news article (e.g., "Acquisition"). type: string nullable: true companyFundingTotal: type: string nullable: true description: Most recent total funding amount for the company. example: '135000000' companyLatestFundingDate: type: string nullable: true description: >- The date of the most recent funding round for the company. format: date example: '2018-01-01' companyLatestFundingClassifications: type: array nullable: true description: >- The classifications of the latest funding round for the company (e.g., "Series A", "Pre-Seed", etc.). example: - Series D items: type: string jobChangeAlert: type: string description: > Type of job change detected given provided or default job change date range. When detected; 'New Hire' = joined a new company, 'New Promotion' = new role at the same company. enum: - New Hire - New Promotion nullable: true formerCompany: type: string nullable: true description: Name of the contact's most recent previous employer. formerTitle: type: string nullable: true description: >- Job title at the contact's most recent previous employer. formerStartedAt: type: string format: date nullable: true description: >- Date the contact started at their former company (YYYY-MM-DD). formerEndedAt: type: string format: date nullable: true description: >- Date the contact left their former company (YYYY-MM-DD). companyType: type: string nullable: true description: >- Company type — "Public" or "Private" when determined. enum: - Public - Private example: Public stockTicker: type: string nullable: true description: >- Stock ticker symbol of the company, if publicly traded. example: AAPL supplementalData: type: object description: Pagination metadata for the current search result set. properties: isMore: description: >- Indicates whether additional pages of results are available beyond the current page. type: boolean example: true total: description: >- The total number of contacts matching the search criteria. type: integer example: 150 perPage: description: >- The number of results returned per page for this search request. Returned by contact search only — company search omits this field, so read the page size from the length of `data` rather than relying on it. type: integer example: 50 nextToken: description: >- An opaque pagination token. Pass this value in the `nextToken` field of your next request body to retrieve the next page of results. Null or absent when no more pages are available. type: string nullable: true example: eyJwYWdlIjoyLCJzZWFyY2hJZCI6ImFiYzEyMyJ9 '401': description: Unauthorized content: application/json: schema: type: object required: - message properties: message: description: A human readable error message type: string '422': description: Insufficient credits or missing license content: application/json: schema: description: Insufficient credits or missing license type: object properties: msg: type: string code: type: string data: type: object properties: productCategory: type: string additionalCreditsNeeded: type: integer '500': description: Unexpected error content: application/json: schema: type: object required: - message properties: message: description: A human readable error message type: string security: - OAuth2: [] - ApiKeyAuth: [] components: securitySchemes: OAuth2: type: oauth2 flows: authorizationCode: authorizationUrl: https://login.seamless.ai/oauth/authorize tokenUrl: https://api.seamless.ai/api/client/v2/oauth/accessToken scopes: {} ApiKeyAuth: type: apiKey name: Token in: header description: API key passed via the Token header. ````