# Publish-agent-version API: expose version\_title (version name) as a writable field

**URL:** <https://community.retellai.com/t/publish-agent-version-api-expose-version-title-version-name-as-a-writable-field/2837>\
**Category:** Support Help\
**Tags:** bug\
**Created:** [May 22, 2026, 4:05pm UTC](https://community.retellai.com/t/publish-agent-version-api-expose-version-title-version-name-as-a-writable-field/2837 "2026-05-22T16:05:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicolas.costa](https://avatars.discourse-cdn.com/v4/letter/n/4af34b/32.png) [@nicolas.costa](https://community.retellai.com/u/nicolas.costa)\
**Post date:** [May 22, 2026, 4:05pm UTC](https://community.retellai.com/t/publish-agent-version-api-expose-version-title-version-name-as-a-writable-field/2837/1 "2026-05-22T16:05:28Z")

</div>

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`](https://docs.retellai.com/api-references/publish-agent) 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](https://canada1.discourse-cdn.com/flex008/uploads/retell1/original/2X/d/d1acb70a2c865995c651b9d006b33dd40a7219cf.png)

 ![image](https://canada1.discourse-cdn.com/flex008/uploads/retell1/original/2X/6/661a0f20ef936383109fb3a974faae7cbdef2cd1.png)

---

<div class="post-metadata">

**Author:** ![Shah-Fazal](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/shah-fazal/32/2522_2.png) [@Shah-Fazal](https://community.retellai.com/u/Shah-Fazal)\
**Post date:** [May 23, 2026, 8:10pm UTC](https://community.retellai.com/t/publish-agent-version-api-expose-version-title-version-name-as-a-writable-field/2837/2 "2026-05-23T20:10:29Z")

</div>

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

Best regards

---

<div class="post-metadata">

**Author:** ![Shah-Fazal](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/shah-fazal/32/2522_2.png) [@Shah-Fazal](https://community.retellai.com/u/Shah-Fazal)\
**Post date:** [May 25, 2026, 12:56pm UTC](https://community.retellai.com/t/publish-agent-version-api-expose-version-title-version-name-as-a-writable-field/2837/3 "2026-05-25T12:56:30Z")

</div>

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:

```auto
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