# Crustdata

> Crustdata versioned company, person, job and web data, plus watches.

App · 20 actions. Web page: https://docs.lodol.com/docs/integrations/crustdata

## Actions

### Cancel discovery watch

Cancel discovery watch.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Watch id (`watch_id`, number, required): The watch's `id`, returned when it was created.

**Outputs**

- `data` (object): Api result.

**Example output**

```json
{
  "data": {}
}
```

### Create discovery watch

Create discovery watch.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Preview (`preview`, true/false): Ask what this watch would do instead of creating it. The request is validated exactly as a create is, nothing is persisted, and no credits are charged or reserved , so a preview works even on an account with no credits left, which is the balance a preview is usually being run to inform. Answers `200` with the preview rather than `201` with a watch. Everything else in the body means the same thing it means on a create, so preview and create differ by this flag alone.
- Filters (`filters`, object): The search filter to re-run each interval. A single leaf or a nested AND/OR group, in the dataset's full search grammar. Required on an index watch, and refused on a realtime one. A realtime watch's records are new by construction, so asking this tree about one means asking an index that has never seen it, which drops every result. Narrow a realtime watch with `narrowing_filters` instead.
- Realtime filters (`realtime_filters`, object): What the live search is asked for on a realtime watch. Requires `config.is_realtime: true`, and sending one without the other is a `400` in both directions. This tree accepts fewer fields and a simpler shape than the dataset's full search grammar. Each leaf follows the leaf schema for the path's dataset: `RealtimeConditionPerson`, `RealtimeConditionCompany`, `RealtimeConditionJob`, or `RealtimeConditionSocialPost`. Each one lists the fields that dataset's live search accepts and the operators and values each field takes. The tree shape is in `RealtimeConditionGroup`. Fields the live search cannot express belong in `narrowing_filters`, when the dataset that owns them is one this watch may narrow on; the refusal names the block. Values are unchanged: you write the same ones here as you do on an index watch, and the watch translates them for the live search.
- Narrowing filters (`narrowing_filters`, object): What narrows a realtime watch, keyed by dataset. Requires `config.is_realtime: true`, and goes at the top level of the body rather than inside `config`. A record the live search just found is too new for its own index to hold, so narrowing asks about the durable entity behind it instead: the author of a post, the company hiring for a job, the person as the index already knows them. Each block is a plain single-dataset tree asked of that dataset's own index, in that dataset's own vocabulary, so a field belonging to another dataset is refused rather than resolved. A block keeps that dataset's **full search grammar**, unlike `realtime_filters`: an `or` across two different fields, nested `and` / `or` groups, and every negation operator all work, because an index answers it rather than the live search. The one restriction is that every leaf must belong to the block's own dataset. The fields and operators are exactly those of that dataset's search endpoint: `PersonSearchCondition` on `POST /person/search` for the `person` block, and `SearchCondition` on `POST /company/search` for the `company` block. Only `person` and `company` may be named, and which of the two depends on the watch: a `person` or `social_post` watch may narrow on either, and a `company` or `job` watch on `company` alone. Name one block. A job posting or a social post is the new record itself, so there is no older copy of it to ask about, and a condition about the record the search returned belongs in `realtime_filters`. A record whose entity the index does not hold is dropped rather than delivered unchecked. Immutable once set, like `realtime_filters`.
- Sorts (`sorts`, list): Delivery order within a run, for example newest first. Sorting does not change which records are new, only the order they arrive in when a run is capped.
- Fields (`fields`, list): Field groups or field paths to include in each delivered `record`. Defaults to the dataset's standard projection. Every requested field is checked against the key's entitlements at creation, and `fields` does not affect what a record costs.
- On (`on`, list): Which membership transitions notify you. Only `added`, records that newly match, is supported today, and it is the default. One or more of: `added`.
- Config (`config`, object, required): Schedule and per-run caps for a discovery watch.
- Notifications (`notifications`, list): Delivery channels. May be empty for a pull-only watch, which pushes nothing and whose results you read from the run-history endpoints instead.
- Overflow policy (`overflow_policy`, text): What happens to new records beyond `max_results_per_run`. `redeliver` leaves the overflow unseen so it comes back in a later run. `drop` marks every new record seen so the overflow never returns. One of: `redeliver`, `drop`.

**Outputs**

- `data` (object): A discovery watch, as returned by create, get, list, and update.

**Example output**

```json
{
  "data": {
    "api_version": "example",
    "config": {
      "expires_at": "example",
      "is_realtime": false,
      "max_results_per_run": 1,
      "payload_delivery_type": "inline",
      "preferred_hour": 1,
      "trigger": {
        "every_hours": 1,
        "type": "interval"
      }
    },
    "config_version": "example",
    "created_at": "example",
    "credits_consumed": 1.0,
    "dataset": "person",
    "fields": [],
    "filters": {
      "field": "example",
      "type": "=",
      "value": "example"
    },
    "id": 1,
    "kind": "discovery",
    "last_notified_at": "example",
    "last_run_at": "example",
    "narrowing_filters": {},
    "notifications": [],
    "notifications_count": 1,
    "on": [],
    "realtime_filters": {
      "field": "example",
      "type": "=",
      "value": "example"
    },
    "sorts": [],
    "status": "active"
  }
}
```

### Enrich companies

Enrich companies.

**Inputs**

- Names (`names`, list): Names.
- Domains (`domains`, list): Domains.
- Crustdata company ids (`crustdata_company_ids`, list): Crustdata company ids.
- Professional network profile urls (`professional_network_profile_urls`, list): Professional network profile urls.
- Fields (`fields`, list): Field groups to include in `company_data`. When `fields` is omitted, only `crustdata_company_id` and `basic_info` are returned , sections such as `headcount`, `funding`, `people`, and `hiring` must be listed explicitly. Valid field groups for enrich: basic_info, revenue, headcount, funding, hiring, web_traffic, seo, competitors, employee_reviews, people, locations, taxonomy, followers, news, software_reviews, social_profiles, reviews, public_launches, market_intel, metadata, crustdata_company_id, updated_at, indexed_at. Also available: social_posts, which is never returned by default and must be requested explicitly. Not valid for enrich: roles, skills (search-only fields).
- Exact match (`exact_match`, true/false): Whether to use exact matching (null means auto-detect)

**Outputs**

- `data` (list): Top-level array returned by /company/enrich with one entry per submitted identifier.

**Example output**

```json
{
  "data": []
}
```

### Enrich contacts

Enrich contacts.

**Inputs**

- Professional network profile urls (`professional_network_profile_urls`, list): Array of professional-network profile URLs to enrich (max 25).
- Business emails (`business_emails`, list): Array of business emails to look up (max 25).
- Fields (`fields`, list): Contact tiers to enrich. Only contact fields are accepted: `contact.business_emails`, `contact.personal_emails`, `contact.phone_numbers`, `contact.phone_numbers_info`, and `contact.websites`. `contact.phone_numbers_info` belongs to the phone tier, so either phone field bills the tier once. `contact.phone_numbers` returns both phone lists. `contact.phone_numbers_info`, or one of its sub-fields, returns only `phone_numbers_info`. When omitted, the three contact tiers (business emails, personal emails, phone numbers) are enriched; `contact.websites` must be requested explicitly. Requesting any non-contact field returns a `400` error.
- Verified (`verified`, true/false): Return only business emails that pass a deliverability check at request time. Cached addresses marked `deliverable` or `unknown` are re-checked before they are served, and only `deliverable` and `catch_all` entries are returned. When no address survives, `contact.business_emails` is empty and `contact.business_emails_message` is set. Only affects `contact.business_emails`. Adds 0.5 credits per matched person who receives at least one verified business email.

**Outputs**

- `data` (list): Response from /person/contact/enrich. Returns a top-level array with one entry per submitted identifier.

**Example output**

```json
{
  "data": []
}
```

### Enrich people

Enrich people.

**Inputs**

- Professional network profile urls (`professional_network_profile_urls`, list, required): Array of professional-network profile URLs (max 25).
- Fields (`fields`, list): Fields to include in the response. Valid field groups for enrich: basic_profile, professional_network, skills, social_handles, experience, education, certifications, honors, dev_platform_profiles, assessment, social_posts, research_profiles. Use dot-notation for nested fields (e.g., "basic_profile.name", "experience.employment_details"). If omitted, a default set (basic_profile, social_handles) is returned. Request additional groups explicitly. Some groups (for example certifications, honors, and research_profiles) require field-level permission on your API key; research_profiles is enabled per account on request and returns `403 Access denied to fields: research_profiles` without the grant.
- Preview (`preview`, true/false): Enabled per account on request. Without the grant, the API returns `400 invalid_request` with the message `Preview feature is not available for your account. Please reach out to Crustdata team.` and charges 0 credits. Where enabled, preview mode returns only basic profile fields, charges 0 credits, and ignores `fields`. You cannot combine it with `enrich_realtime`.

**Outputs**

- `data` (list): Response from /person/enrich. Returns a top-level array with one entry per submitted identifier.

**Example output**

```json
{
  "data": []
}
```

### Fetch web pages

Fetch web pages.

**Inputs**

- Urls (`urls`, list, required): List of URLs to fetch web content for. Each URL must include the protocol prefix (http:// or https://). Maximum of 10 URLs per request.
- Human mode (`human_mode`, true/false): Whether to use a browser-like retrieval path when standard access is blocked.

**Outputs**

- `data` (list): Array of fetch results, one per URL in the request.

**Example output**

```json
{
  "data": []
}
```

### Get credits

Get credits.

**Inputs**: None.

**Outputs**

- `data` (object): Wrapper object for the account credit summary. The balance always sits under the `account` key, never at the top level.

**Example output**

```json
{
  "data": {
    "account": {
      "credit_topups": [],
      "credits": 1.0,
      "recurring_credits": 1,
      "recurring_credits_frequency": "example",
      "recurring_credits_refresh_date": "example",
      "wallets": []
    }
  }
}
```

### Get discovery watch

Get discovery watch.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Watch id (`watch_id`, number, required): The watch's `id`, returned when it was created.

**Outputs**

- `data` (object): A discovery watch, as returned by create, get, list, and update.

**Example output**

```json
{
  "data": {
    "api_version": "example",
    "config": {
      "expires_at": "example",
      "is_realtime": false,
      "max_results_per_run": 1,
      "payload_delivery_type": "inline",
      "preferred_hour": 1,
      "trigger": {
        "every_hours": 1,
        "type": "interval"
      }
    },
    "config_version": "example",
    "created_at": "example",
    "credits_consumed": 1.0,
    "dataset": "person",
    "fields": [],
    "filters": {
      "field": "example",
      "type": "=",
      "value": "example"
    },
    "id": 1,
    "kind": "discovery",
    "last_notified_at": "example",
    "last_run_at": "example",
    "narrowing_filters": {},
    "notifications": [],
    "notifications_count": 1,
    "on": [],
    "realtime_filters": {
      "field": "example",
      "type": "=",
      "value": "example"
    },
    "sorts": [],
    "status": "active"
  }
}
```

### Get entity watch

Get entity watch.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. Entity watches support `person` and `company`; there is no job entity watch, and `job` returns `404` here. Use `/watch/job/search` for jobs. One of: `person`, `company`.
- Watch id (`watch_id`, number, required): The watch's `id`, returned when it was created.

**Outputs**

- `data` (object): An entity watch, as returned by create, get, list, and update.

**Example output**

```json
{
  "data": {
    "api_version": "example",
    "config": {
      "expires_at": "example",
      "max_results_per_run": 1,
      "payload_delivery_type": "inline",
      "preferred_hour": 1,
      "refresh_frequency_days": 1,
      "trigger": {
        "every_hours": 1,
        "type": "interval"
      }
    },
    "config_version": "example",
    "created_at": "example",
    "credits_consumed": 1.0,
    "dataset": "person",
    "entities": {
      "business_emails": [],
      "crustdata_company_ids": [],
      "domains": [],
      "names": [],
      "professional_network_profile_urls": []
    },
    "fields": [],
    "id": 1,
    "kind": "entity",
    "last_notified_at": "example",
    "last_run_at": "example",
    "notifications": [],
    "notifications_count": 1,
    "status": "active",
    "track": {
      "field": "example",
      "keys": [],
      "type": "changed",
      "value": "example"
    }
  }
}
```

### Get watch run summary

Get watch run summary.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Watch id (`watch_id`, number, required): The watch's `id`, returned when it was created.
- Run id (`run_id`, number, required): The run's id, from `runs[].id` on the run-history endpoint.

**Outputs**

- `data` (object): One run in full, with its counts, its activity log, and its deliveries.

**Example output**

```json
{
  "data": {
    "completed_at": "example",
    "credits_deducted": 1.0,
    "failure_reason": "example",
    "id": 1,
    "logs": [],
    "new_records_count": 1,
    "notifications": [],
    "payload_delivery": {
      "bytes": 1,
      "expires_at": "example",
      "format": "ndjson",
      "type": "inline",
      "url": "example"
    },
    "records_after_filter": 1,
    "records_matched": 1,
    "records_searched": 1,
    "records_stale": 1,
    "started_at": "example",
    "status": "RUNNING"
  }
}
```

### Identify companies

Identify companies.

**Inputs**

- Names (`names`, list): Names.
- Domains (`domains`, list): Domains.
- Crustdata company ids (`crustdata_company_ids`, list): Crustdata company ids.
- Professional network profile urls (`professional_network_profile_urls`, list): Professional network profile urls.
- Fields (`fields`, list): Field groups to include in `company_data`. Valid field groups: `crustdata_company_id`, `basic_info`, `social_profiles`. Identify resolves a company to its identity and basic profile only; requesting any other group returns `400 Invalid fields`. For `headcount`, `funding`, `people`, `hiring`, `revenue` and other sections, use `/company/enrich`.
- Exact match (`exact_match`, true/false): Whether to use exact matching (null means auto-detect)

**Outputs**

- `data` (list): Top-level array returned by /company/identify with one entry per submitted identifier.

**Example output**

```json
{
  "data": []
}
```

### Identify people

Identify people.

**Inputs**

- Professional network profile urls (`professional_network_profile_urls`, list): Person profile URLs. 1 credit per match.
- Emails (`emails`, list): Email addresses, business or personal. An address not on file is matched by name at the domain's company, then looked up with a contact vendor, in the same request. 1 credit per match.
- Research profile urls (`research_profile_urls`, list): Google Scholar profile URLs, for example `https://scholar.google.com/citations?user=VGjeKSMAAAAJ`. Only Google Scholar is supported. 1 credit per match.

**Outputs**

- `data` (list): Response from /person/identify. A top-level array with one row per submitted identifier, in request order.

**Example output**

```json
{
  "data": []
}
```

### List discovery watches

List discovery watches.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Status (`status`, text): Return only watches in this state. Omit to return every state. One of: `active`, `paused`, `suspended`, `expired`, `cancelled`.
- Limit (`limit`, number): Watches per page. Values above the maximum are clamped rather than rejected, as is a non-numeric value, which falls back to the default. From 1 to 500.
- Offset (`offset`, number): Number of watches to skip. Negative values are clamped to `0`. At least 0.

**Outputs**

- `data` (list): Api result.

**Example output**

```json
{
  "data": []
}
```

### List endpoint permissions

List endpoint permissions.

**Inputs**

- Path (`path`, text): Return only the endpoint at this exact path, for example `/company/enrich`. The match is exact and case-sensitive: the leading slash is required, a trailing slash does not match, and a prefix such as `/company` matches nothing. Any path that does not match returns an empty `endpoints` array rather than `404`.
- Category (`category`, text): Return only endpoints in this product category. Matching is case-insensitive, so `Company`, `company`, and `COMPANY` all return the same 8 entries. On the `2025-11-01` version the categories are `Company`, `Person`, `Jobs`, `Web`, `Social`, and `Other`. An unknown category returns an empty `endpoints` array.
- Status (`status`, text): Return only endpoints with this access status. The value is case-sensitive and must be lowercase. Any other value, including `Enabled`, returns `400`. One of: `enabled`, `disabled`.

**Outputs**

- `data` (object): Endpoint permission overview for the account. Holds one entry per product endpoint unless a `path`, `category`, or `status` filter narrowed it.

**Example output**

```json
{
  "data": {
    "api_version": "example",
    "endpoints": [],
    "token_limit_rpm": 1
  }
}
```

### List entity watches

List entity watches.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. Entity watches support `person` and `company`; there is no job entity watch, and `job` returns `404` here. Use `/watch/job/search` for jobs. One of: `person`, `company`.
- Status (`status`, text): Return only watches in this state. Omit to return every state. One of: `active`, `paused`, `suspended`, `expired`, `cancelled`.
- Limit (`limit`, number): Watches per page. Values above the maximum are clamped rather than rejected, as is a non-numeric value, which falls back to the default. From 1 to 500.
- Offset (`offset`, number): Number of watches to skip. Negative values are clamped to `0`. At least 0.

**Outputs**

- `data` (list): Api result.

**Example output**

```json
{
  "data": []
}
```

### List watch runs

List watch runs.

**Inputs**

- Dataset (`dataset`, text, required): The dataset the watch is built on. One of: `person`, `company`, `job`, `social_post` (Social post).
- Watch id (`watch_id`, number, required): The watch's `id`, returned when it was created.
- Limit (`limit`, number): Runs per page. From 1 to 1000.
- Cursor (`cursor`, number): The `next_cursor` from the previous page. Runs with an id below this are returned.
- Only credited (`only_credited`, true/false): Return only runs that deducted credits.

**Outputs**

- `data` (object): A page of runs, newest first.

**Example output**

```json
{
  "data": {
    "next_cursor": 1,
    "runs": [],
    "total_count": 1
  }
}
```

### Search companies

Search companies.

**Inputs**

- Filters (`filters`, object): Search filters. Required when `search` is omitted. When combined with ranked search, filters are hard constraints applied before retrieval.
- Cursor (`cursor`, text): Pagination cursor from the previous response's `next_cursor`. For ranked search, keep query, mode, filters and API version unchanged; limit and authorized fields may change. Cursors expire 20 minutes after the initial ranked search. Restart without cursor if the cursor or cached search is no longer valid.
- Limit (`limit`, number): Results per page. The maximum is 1000 for filter-only search and 100 for ranked search. Ranked search covers at most 1000 candidate positions across pages. From 1 to 1000.
- Sorts (`sorts`, list): Sort directives applied to filter-only results. Not supported with ranked search.
- Fields (`fields`, list): Fields to return in the response. Use dot-notation for nested fields (e.g., "basic_info.name", "headcount.total"). Each company always includes `crustdata_company_id`, even when you do not request it. Every requested field is in the response, and a field with no data for the company is `null`. When a requested group has no data, the whole group is `null`, even if you asked for one of its sub-fields. Valid top-level groups for search: basic_info, revenue, headcount, funding, hiring, locations, taxonomy, followers, social_profiles, software_reviews, metadata, updated_at, indexed_at, crustdata_company_id. Some groups are filter-only and cannot be selected here (for example roles, skills, seo, competitors), and groups not in the search index (for example news, people, web_traffic, employee_reviews) are rejected. Use /company/enrich for those.
- Search (`natural_language_query`, text): Describe the companies to find.
- Search mode (`search_mode`, text): How the search matches your description. One of: `hybrid`, `lexical`, `semantic`.

**Outputs**

- `data` (object): Paginated response from the /company/search endpoint.

**Example output**

```json
{
  "data": {
    "companies": [],
    "next_cursor": "example",
    "query": {},
    "total_count": 1
  }
}
```

### Search jobs

Search jobs.

**Inputs**

- Filters (`filters`, object): Search filter conditions. Can be a single condition or a nested group combined with AND/OR logic. Only indexed fields are filterable , see `SearchCondition.field` for the full list.
- Cursor (`cursor`, text): Opaque pagination cursor returned in a prior response's `next_cursor` field. Pass this to fetch the next page of results with the same filter, sort, and field selection.
- Limit (`limit`, number): Maximum number of job listings to return per page. Set to 0 when you only want aggregations. From 0 to 1000.
- Sorts (`sorts`, list): Sort specifications for ordering results. Sorts are applied in order.
- Fields (`fields`, list): Fields to return in each job listing. Use dot-notation for nested fields (e.g., "job_details.title", "company.basic_info.name"). If omitted, all available fields are returned. Valid top-level groups: `crustdata_job_id`, `job_details`, `company`, `location`, `content`, `metadata`. Nested fields are supported (e.g., `company.basic_info`, `company.headcount`, `company.funding`).
- Aggregations (`aggregations`, list): Aggregation queries to run alongside the search. Set `limit: 0` if you want only aggregation results and no job rows.

**Outputs**

- `data` (object): Paginated response from the indexed job search endpoint.

**Example output**

```json
{
  "data": {
    "aggregations": [],
    "job_listings": [],
    "next_cursor": "example",
    "total_count": 1
  }
}
```

### Search people

Search people.

**Inputs**

- Filters (`filters`, object, required): Filter criteria , a single `PersonSearchCondition` or a `PersonSearchConditionGroup` combining conditions with `and`, `or`, or `all_of` (cross-element matching on nested-array fields).
- Sorts (`sorts`, list): Sort directives applied to matched people in order.
- Limit (`limit`, number): Limit. From 1 to 1000.
- Count (`count`, number): Alias for limit. From 1 to 1000.
- Cursor (`cursor`, text): Pagination cursor from a previous response's `next_cursor`. Omit on the first page.
- Post processing (`post_processing`, object): Post-processing options applied to search results (e.g., exclusions).
- Return query (`return_query`, true/false): Debug flag - include search query in response
- Preview (`preview`, true/false): Preview mode - return only basic fields for faster response
- Explain (`explain`, true/false): Explain an empty result. When true and a filters-only request returns `total_count` 0, `remarks` names the condition whose removal recovers profiles. Not the `search.explain` flag on semantic search, which returns per-hit scoring.
- Fields (`fields`, list): Optional list of field paths to include in each returned profile. When omitted, a default set of profile fields is returned. Use dot notation for a nested field (for example `experience.employment_details.current.title`) or a top-level family name (for example `basic_profile`) to include the whole family. Each profile always includes `crustdata_person_id`, even when you do not request it. A requested field with no data for the profile is `null`. An unsupported value returns a `400` whose `metadata.available_fields` lists every selectable field. `research_profiles` and its sub-paths are enabled per account; without the grant they return `403 Access denied to fields: research_profiles`. `skills` is also enabled per account and returns `403 Access denied to fields: skills` without access. `certifications`, `honors`, `years_of_experience`, `years_of_experience_raw`, and `experience.recently_changed_jobs` are enabled per account too, and return `403` with each denied path without access. `dev_platform_profiles` is filter-only and returns `400 Invalid fields: dev_platform_profiles`.

**Outputs**

- `data` (object): Paginated response from the person search endpoint containing matched profiles and pagination metadata.

**Example output**

```json
{
  "data": {
    "next_cursor": "example",
    "profiles": [],
    "remarks": [],
    "total_count": 1,
    "total_count_relation": "example"
  }
}
```

### Search web

Search web.

**Inputs**

- Query (`query`, text, required): The search query text. Keep queries concise and specific for better results. Supports standard search operators (e.g., site:, filetype:).
- Location (`location`, text): ISO 3166-1 alpha-2 country code for location targeting. Use this to get region-specific search results. Valid values include US, CA, MX, BR, AR, CL, CO, PE, VE, GB, DE, FR, IT, ES, PT, NL, BE, CH, AT, PL, SE, NO, DK, FI, IE, RU, UA, CZ, GR, TR, RO, HU, JP, CN, KR, IN, ID, TH, VN, MY, SG, PH, TW, HK, SA, AE, IL, EG, AU, NZ, ZA, NG, KE.
- Sources (`sources`, list): List of search sources to query. If omitted, all sources are searched. Use specific sources to narrow results. One or more of: `news`, `web`, `scholar-articles`, `scholar-articles-enriched`, `scholar-author`, `ai`, `social`.
- Site (`site`, text): Restrict search results to a specific site domain. For example, use "linkedin.com/company" to find company LinkedIn pages, or "site:github.com" for developer profiles.
- Start date (`start_date`, number): Unix timestamp (seconds since epoch) for the start date filter. Must be less than end_date if both are provided.
- End date (`end_date`, number): Unix timestamp (seconds since epoch) for the end date filter. Must be greater than start_date if both are provided.
- Human mode (`human_mode`, true/false): Whether to use a browser-like retrieval path when standard access is blocked.
- Page (`page`, number): Number of search result pages to aggregate into a single response. Values above 15 are rejected with a 400. When greater than 1, `sources` must contain exactly one source. From 1 to 15.

**Outputs**

- `data` (object): Response object for a web search request.

**Example output**

```json
{
  "data": {
    "metadata": {
      "empty_pages": [],
      "failed_pages": [],
      "total_results": 1
    },
    "query": "example",
    "results": [],
    "success": false,
    "timestamp": 1
  }
}
```
