---
title: "Resolve search-filter IDs (Sales Navigator)"
method: GET
path: "/v1/{account_id}/sales-navigator/search/parameters"
tags: ["Sales Navigator: Search"]
---

# Resolve search-filter IDs (Sales Navigator)

`GET /v1/{account_id}/sales-navigator/search/parameters`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/sales-navigator/search/parameters`
- Auth: HTTP bearer

Resolves human-readable terms to opaque Sales Navigator filter IDs for people or company search. type selects the filter family; an unrecognized value is rejected with 400. Requires a Sales Navigator seat.

## Path parameters

- `account_id` string, required

## Query parameters

- `type` 'COMPANY' | 'ACCOUNT_LIST' | 'LEAD_LIST' | 'LOCATION' | 'POSTAL_CODE' | 'JOB_FUNCTION' | 'JOB_TITLE' | 'INDUSTRY' | 'GROUP' | 'SCHOOL' | 'RELATION' | 'PERSONA' | 'SAVED_PEOPLE_SEARCH' | 'SAVED_COMPANY_SEARCH' | 'RECENT_SEARCH' | 'PROFILE_LANGUAGE', required
- `keywords` string
- `limit` integer
- `cursor` string

## Response `200`

Resolved Sales Navigator filter parameter IDs. Pass the returned id values in structured filter include/exclude arrays.

- object
  - `object` 'sn_search_parameter_list', required: Response type discriminator.
  - `items` object[], required: Resolved filter items.
    - `id` string, required: Opaque filter ID to pass in structured filter include/exclude arrays.
    - `name` string, required: Human-readable filter name (e.g. 'Software Development').
    - `metadata` object: Additional metadata. Present only for the saved-search types (SAVED_PEOPLE_SEARCH, SAVED_COMPANY_SEARCH). Pass-through; not stored.
  - `paging` object, required: Pagination metadata.
    - `total_count` number, nullable: Total number of items. May be null.
  - `cursor` string, nullable, required: Opaque cursor for the next page, or null when exhausted.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: Invalid request, malformed or missing account_id, limit, cursor, or body field.
- `401`: Unauthenticated, missing or invalid API key.
- `403`: Forbidden. Either NO_ACTIVE_SEAT (the account is not attached to an active seat), or LINKEDIN_FEATURE_NOT_SUBSCRIBED (the connected LinkedIn account lacks the Sales Navigator subscription; activate it on LinkedIn, reconnecting will not help). The code field distinguishes the two.
- `404`: RESOURCE_NOT_FOUND, the account_id or list does not exist or does not belong to this tenant. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `422`: ACCOUNT_RESTRICTED, the account cannot perform this operation.
- `429`: RATE_LIMIT_ACCOUNT, request rate exceeded.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)