Update guidelines
Change an agent’s guidelines and response style.
Only the fields sent change. sections is the whole set of guideline sections, so a request with it needs
If-Match: a section left out is deleted, a new type is added, and a section sent as it is stays as it is. Answers
with the agent’s guidelines. Applies from the next call. In the web app, the API key’s name shows as who last
changed each section.
Authorizations
An org API key: Authorization: Bearer phk_…
Headers
The ETag from your last read: the change is made only if the resource still has it, otherwise 412. Optional, except that a change replacing a list needs it (428 without it).
Optional. Must be the key's org.
Path Parameters
The agent's ID.
Body
What to change. Only the fields sent change; sections is the whole set, so send If-Match.
Whether the agent adds natural speech habits, such as short pauses and filler words.
Known values: casual, humorous, direct, formal, persuasive, friendly. More can be added, so handle values you don't recognize.
All the guideline sections the agent has, in any order. A section left out is deleted, a new type is added, and a section sent as it is stays as it is.
7Response
Successful Response
How an agent behaves in conversation: its guideline sections and response style.
The agent's ID.
Whether the agent adds natural speech habits, such as short pauses and filler words.
The type of this object, always agent_guidelines.
"agent_guidelines"The tone the agent takes with callers. Known values: casual, humorous, direct, formal, persuasive, friendly. More can be added, so handle values you don't recognize.
The guideline sections the agent has, in the order the web app shows them. Each type appears at most once.

