Skip to main content
POST
Generate Agent Tone
Read only Generate Agent Tone uses your workspace API key. Drafts an agent tone and inferred locale from the supplied context without changing an agent.

Before you begin

Use a server-side API key for the intended workspace.

Generate Agent Tone request

The request panel lists supported query parameters and body fields. For a request body, the example below supplies the required fields. Replace sample values with your own inputs.

Verify the result

Expect HTTP 201. Read the data property in the success envelope; the response panel documents its fields. This operation also accepts the matching /v1/assistant path. The request and result contracts are shared. Use one path consistently for your integration.

Retry safety

This operation does not modify workspace resources. Retry after a transient connection failure.

Errors and recovery

  • 401: Missing, expired, or invalid API key.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
company_and_offering
string
required
target_customer
string
required
primary_goal
string
required
success_criteria
string
required
information_to_collect
string
required
objections_and_faqs
string
required

Response

Generated agent tone

success
enum<boolean>
required
Available options:
true
error
enum<boolean>
required
Available options:
false
statusCode
integer
required
Example:

201

message
string
required
Example:

"Success"

data
object
required
timestamp
string<date-time>
required