Update Company Profile
Update company profile
Overview
Replaces the workspace’s full company profile: user background, company positioning, content strategy, and ICP/market context. The body is validated as a complete profile object; partial updates are rejected. Use this when setup or a human edit changes the profile that downstream workflows should use. The response returns the newly persisted full context.AI agent notes
Fetch Get Company Profile first, apply the user’s requested edits locally, and PUT the complete object back. Preserve every section the user did not ask to change. Do not synthesize ICP, company, or voice details without user-provided source material. If the user only gives a small correction, update that field and keep the rest of the current context intact.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Whole-object replacement for context. There is no field-level PATCH — fetch with GET /api/context, mutate client-side, and PUT the full object back.
Full context object. Validated against FullUserContextSchema; all four sub-objects (user, company, content, market) must be present, extra may be null.
Optional identity fields to update alongside the context JSONB columns. Only keys present in the body are applied.
Response
Context saved. Returns the newly persisted full context.
Assembled company profile. Each sub-object is stored as a separate JSONB column on user_profiles and merged at read time.