Write
update_profile
Updates the display name (title) shown on an Outli.ne profile.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| outlineId | string | — | The numeric ID of the outline to update. Omit to target the authenticated creator's own outline. Pass explicitly only when a creator owns multiple outlines and you need a specific one. |
| name | string | Yes | The new display name to set on the profile. Must be between 1 and 200 characters. This maps to the outline's `title` field in Payload. |
Response
| Field | Type | What it means |
|---|---|---|
| outlineId | string | The numeric ID (as a string) of the outline that was updated. Use this to chain into further write calls on the same outline. |
| updated | object | Echo of what was written. Contains a single key `name` with the new display name value that was persisted. |
| updated.name | string | The display name that was just saved to the outline. |
Example
Request
json
{
"name": "Maya Chen — Wedding & Portrait Photographer"
}Response
json
{
"outlineId": "42",
"updated": {
"name": "Maya Chen — Wedding & Portrait Photographer"
}
}When to use
Call this early in the create→curate→optimize loop, right after establishing which outline you are working on, to set or correct the creator's display name before building out stacks and cards. Also use it any time the creator wants to rebrand or refine how their name appears on the profile.
Watch out
Watch out
- outlineId defaults to the authenticated creator's own outline — omitting it is the common case and is safe
- The name maps to the Payload `title` field, not a separate `name` column — tools that read the outline will see it as `title`
- No confirm flag and no dry-run mode — the write happens immediately on call
- IDOR is enforced inside resolveOutlineDoc; passing another user's outlineId returns NOT_FOUND, not FORBIDDEN, to avoid confirming existence