G
Garrett Fitzgerald
Support Ticket: Hume Prompt Version Endpoint Failure
Subject:
Unable to create new prompt versions with
/prompts/{id}/version
(returns 404)
## Summary
We can no longer create prompt versions via the documented endpoint
POST /v0/evi/prompts/{id}/version
. The call worked previously but now consistently returns
404 – No static resource prompts/{id}/version.
even when the prompt was created moments earlier using the same API key.
## Environment
  • API base:
    https://api.hume.ai/v0/evi
  • Date observed: November 5–6, 2025
  • Issue reproduces across multiple newly created prompts
## Steps to Reproduce
  1. Create a prompt (works):
```bash
curl -X POST https://api.hume.ai/v0/evi/prompts \
-H "Content-Type: application/json" \
-d '{
"name": "Test Prompt 1762399433623",
"text": "<system_prompt>Initial test prompt 1762399433623</system_prompt>"
}'
```
Response returns ID
2267531d-3ae7-4640-a102-65a659954174
, version
0
.
  1. Attempt to create a new version (fails):
```bash
curl -X POST https://api.hume.ai/v0/evi/prompts/2267531d-3ae7-4640-a102-65a659954174/version \
-H "Content-Type: application/json" \
-d '{
"text": "<system_prompt>Updated prompt text</system_prompt>",
"version_description": "Test update"
}'
```
Actual response:
```json
{
"timestamp": "2025-11-06T03:24:00.488+00:00",
"status": 404,
"error": "Not Found",
"message": "No static resource prompts/2267531d-3ae7-4640-a102-65a659954174/version.",
"path": "/prompts/2267531d-3ae7-4640-a102-65a659954174/version"
}
```
  1. Listing prompts with
    GET /v0/evi/prompts
    still shows the prompt at version
    0
    ; no new version is created. Fetching
    GET /v0/evi/prompts/{id}/versions
    also returns 404.
  2. When we reuse an existing prompt name we get a
    409 Conflict
    plus a prompt ID (example
    dba3da91-2c85-44ce-90c4-f919b770b703
    ), but attempting to access that prompt with this API key returns 404/unauthorized. So we cannot reuse names or create versions; creating an entirely new prompt is the only option.
## Expected Behavior
POST /prompts/{id}/version
should create a new prompt version and return the new version details so we can iterate on the same prompt ID.
## Actual Behavior
The endpoint returns 404 for every prompt ID created with the same API key. Prompt version APIs appear unusable.
## Impact
We are forced to create a new prompt ID for every update, which breaks our editor workflow, complicates config updates, and loses prompt history.
## Scripts / References
  • test-create-hume-assets.js
    — programmatically creates a prompt, config, and attempts the version endpoint (fails with 404).
  • test-access-hume-prompt.js
    — helper to inspect prompt accessibility; duplicated prompt IDs reported by the API are not readable with the same key.
## Request
Please confirm whether
POST /prompts/{id}/version
is still supported. If this is a regression, we’d appreciate a fix or guidance on how to update prompt text without minting new prompt IDs each time.
Thanks!