Sign in
context

Create or update a context entry

Save context (ICP, Messaging Playbook, user profile) the moment the user says save or remember, identity facts as type "user-profile". A playbook write AMENDS the saved document: send the fields that change, a field left out is kept, a field sent as null is removed. Every other type replaces the whole entry, so merge the new information into what is already saved. Renaming is not a rewrite: send the saved scope with the new label and no content.

put/context

Request body

typestring required

One of four closed slots, user-profile, offering, icp or playbook, chosen by what the content means for outreach (global identity or offering, per-chat targeting, or a named first-DM voice), never a free-form custom:* slug.

contentstring

Markdown content, or the document itself when it is structured.

scopestring

Omit scope and pass label so the server derives and attaches "user:icp:<slug>" or "user:playbook:<slug>" (identity/offering fields keep plain "user", rejected for icp/playbook); to reuse an asset already saved instead of rewriting it, send its existing scope alone with no content.

labelstring

Display label

postTicketIdstring

Internal ticket id from a prior tool result. Omit unless a result supplied it.

Response

Context saved

successtrue required
creditsUsedinteger required

Credits consumed by this call. 0 for free endpoints, cached results, duplicates, and for every query that does not touch LinkedIn.

retryAfterinteger required

Seconds to wait before another call of the same type. 0 means no wait is needed.

Changes