Publish-agent-version API: expose version_title (version name) as a writable field

Support Help
1

The Retell UI allows setting both a version name and a version description when publishing an agent (see screenshot). However, the POST /publish-agent-version endpoint only accepts version_description, there is no version_title (or equivalent) field documented or accepted in the payload.

Impact: Teams using the API or CI/CD pipelines to publish agents (e.g., on every merge to main) cannot set a meaningful version name programmatically. The Retell dashboard then shows versions with auto-generated names only, making it harder to correlate a deployed version to a specific git commit, PR, or change description.

Request: Add a version_title (or version_name) field to the POST /publish-agent-version request body, mirroring what the UI already supports.

image
image378×306 16 KB

image
image599×1061 60.4 KB

2

Hey @nicolas.costa I check with the team on this. We’ll keep you updated as soon as we have more information.

Best regards

3

Hello @nicolas.costa

I checked with the team and There is a working path for this today, it just is not documented yet.
POST /publish-agent-version is intentionally limited to version and version_description. The “Version Name” field in the Publish modal is not sent on that call. Under the hood, the dashboard sets the version name via a separate PATCH /update-agent/{agent_id} call with {"version_title": "<your name>", "version": <N>}, then calls publish. version_title is supported on update-agent and is explicitly the one field allowed to be edited on an already-published version, so you can set it either before or after publish.
For your CI/CD pipeline, the equivalent two-step is:

PATCH /update-agent/{agent_id}
body: { "version": 15, "version_title": "PR-1234 / abc1234" }

POST /publish-agent-version/{agent_id}
body: { "version": 15, "version_description": "..." }

One caveat: version_title is not currently listed in the public OpenAPI spec or SDKs, so depending on your SDK you may need to pass it as an extra property or use a raw HTTP call. Treat this as the workaround today.
Your underlying ask, exposing version_title directly on publish-agent-version and documenting it on update-agent, is a fair API ergonomics gap. I have filed this with the product team. I cannot commit to a timeline from here, but will follow up once there is movement.

Thank You