Skip to main content
Use this mapping when building OpenSearch DSL queries against the v3 Search Profiles and Relationships endpoints. The mapping defines which fields are indexed and how (keyword, text, nested, etc.), which determines the query clauses you can use against each field. v3 adds hiring, open_to_work, and the nested team_connections.origins field to the profile index, among other changes from v2.
Querying team_connections.origins — accepted values (provisional, may change): csv, plugin, overlaps, google, google-calendar, user-profile, manual-csv, education-overlaps, investor-overlaps, manual-url. Use a nested query scoped to your team_connections.team_id — see Relationships endpoint examples. This query-side vocabulary differs from the response-side connections[].sources[].origin enum.
opensearch_profile_mapping_v3