Get the accepted prospect-search filter values

The whole people-search filter contract, keyed by search field name. fields.<field>.valueShape says how that field's value must be shaped on the wire — include_exclude takes [{ status, value }] entries, include_exclude_or_string takes entries or a bare string / array of strings (bare strings are includes), term takes a string or an array of strings — and fields.<field>.values lists the accepted { label, value } pairs (send value). Free-text fields such as job_title or location_name have no vocabulary and come back with values: []; use GET /prospects/autocomplete for those. jobTitleRoleToSubRole maps every job_title_role to the job_title_sub_role values beneath it. A static vocabulary generated from the provider's schema: no tenant data, no credits, and callable with any valid token regardless of scope. Values outside a field's vocabulary match nothing, so POST /prospects/search rejects them with 422 before anything is billed.

Errors:

• 429 RATE_LIMITED — Per-token rate limit for this bucket exhausted; retry after the window in the RateLimit-Reset header.
• 500 UNEXPECTED_ERROR — The request failed inside the service; nothing was billed and the request_id identifies the failure.