Skip to main content
Use this workflow when you want to manage reusable prompts outside the Humm UI.

Before You Begin

You will need:
  • Your organization ID
  • A Humm API token
  • The Analyst API base URL, usually https://analyst.heyhumm.ai
The public resource is called a command. If you see older internal references to “slash commands” or “slashies,” use the Commands API instead.
  1. List existing commands
  2. Fetch the command you want to update
  3. Draft the revised content locally
  4. Review the diff
  5. Apply the PUT
  6. Re-fetch the command and inspect version history
  7. Restore an earlier version if you need to roll back the change

1. List Commands

2. Fetch the Current Command

3. Apply the Update

Python Example

TypeScript Example

Prompt Your Assistant

Verification

Fetch the command again:
You can also inspect version history:
Confirm:
  • The prompt content matches the approved version
  • The description is still accurate
  • The command history reflects the update

Restore a Previous Version

If a revision did not work out, restore a prior snapshot instead of rebuilding the command from scratch.
  1. List command history and choose the version you want to restore
  2. Call the restore endpoint for that snapshot
  3. Fetch the command again and confirm the restored content is live
  4. Re-check history to confirm the restore was recorded

Restore with curl

Verify the restore

Fetch the command again:
Then fetch history again:
Confirm:
  • The live command now matches the restored snapshot
  • updated_at changed
  • History includes a new restore event

Notes

  • Keep command names stable unless you are intentionally renaming them.
  • Use descriptive placeholders like {{account_name}} instead of vague variables.
  • If a command is widely used, review the content carefully before updating it for the whole team.