Update Prompt
Update a prompt with new content or properties. Your production prompt stays safe—updates create new versions without affecting what’s currently active.
How it Works:
- Updating components: Creates a new immutable version with fingerprinting. The new version is created but NOT activated, so you can test before going live.
- Updating only properties (name/description): Updates the prompt in-place without creating a new version.
Version Safety: Old versions always point to their original prompts, preserving your message history and allowing you to roll back if needed.
PUT
cURL
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The prompt ID to update
Body
application/json
Updated prompt name.
Updated prompt description.
Role key in the product mapping.
Prompt source.
Available options:
customer, participant, greenflash, agent Updated components (if provided, creates new immutable prompt and version).
Response
Prompt updated successfully
Previous
Archive PromptArchive a prompt you no longer need. Archived prompts are soft-deleted (we set an `archived_at` timestamp) so you can still access them for historical data.
**Safety First:**
- Can't archive a prompt that's currently active. You must activate a different version first.
- Historical data is preserved—old conversations continue to reference archived prompts so your message history stays intact.
- Archived prompts remain accessible for reporting and analysis.
Next
cURL

