Skip to main content
Talk to salesStart

Resolve engagement context

Resolve a browser page into organization-scoped CRM context without changing records.

POST/api/engagement-context/resolve
HTTP referenceScope authenticated user session (developer API keys blocked)Updated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Session-only endpoint. Profile surfaces require person_hints; developer API keys are blocked. The response model includes match status/candidates and organization-scoped lead, company, task, fit, and action context when available.

Body parameters

  • schema_version · optional

    string

    engagement_context.resolve.v1

  • surfacerequired

    string

    linkedin_profile, sales_navigator_profile, linkedin_company, sales_navigator_company, or generic.

  • page_urlrequired

    string

    HTTP(S) URL, maximum 4,096 characters.

  • person_hints · optional

    object

    PersonHints; needed for profile surfaces. Each string hint maximum 500 characters.

  • company_hints · optional

    object

    CompanyHints; each string hint maximum 500 characters.

Errors

StatusMeaning
401Signed-in user JWT required.
403Developer API keys are blocked for this session-only route.
422Invalid URL, surface, hint size, or missing person_hints for a profile surface.

Docs