Skip to main content
Every time you save a prompt, Endprompt creates a new version. This gives you complete history, easy rollbacks, and safe iteration.

​
How Versioning Works

  • Each save creates an immutable version
  • Versions are numbered sequentially (v1, v2, v3…)
  • Only Live prompts can be set as the endpoint default
  • You can view, compare, and restore any version

​
Version Properties

PropertyDescription
Version NumberSequential identifier (v1, v2, v3…)
Created AtTimestamp of creation
StatusDraft, Live, or Archived
TemplateThe prompt text at that version
ModelLLM model used
SettingsTemperature, max tokens, etc.

​
Viewing Version History

1

Open the Prompt

Navigate to your endpoint’s Prompts tab and click on the prompt.
2

Open Version History

Click the History or Versions button in the prompt editor.
3

Browse Versions

See all versions with timestamps and status indicators.
4

View Details

Click any version to see its full configuration.

​
Comparing Versions

Compare two versions side-by-side:
  1. Open version history
  2. Select two versions to compare
  3. View a diff showing what changed
This helps you understand:
  • What changed between versions
  • Why a prompt started behaving differently
  • What to restore if something breaks

​
Status Workflow

​
Draft → Live

Promote a prompt when it’s ready for production:
1

Test Thoroughly

Ensure the prompt works correctly with various inputs.
2

Open Actions Menu

Click the ⋯ menu on the prompt.
3

Select Promote to Live

Click Promote to Live.
4

Confirm

The prompt is now Live and can be set as default.

​
Live → Default

Set a Live prompt as the endpoint’s default:
  1. Ensure the prompt has Live status
  2. Click Set as Default in the actions menu
  3. All requests to the endpoint now use this prompt
Only one prompt can be the default at a time. Setting a new default replaces the previous one.

​
Demote to Draft

If a Live prompt needs more work:
  1. Click ⋯ → Demote to Draft
  2. The prompt returns to Draft status
  3. If it was the default, you’ll need to set a new default

​
Archive

Remove a prompt from active use:
  1. Click ⋯ → Archive
  2. The prompt is hidden from lists
  3. History is preserved for reference
Archive old prompts instead of deleting them. You might need to reference or restore them later.

​
Rollback Scenarios

​
Something Broke in Production

1

Identify the Issue

Check logs to see when problems started.
2

Open Version History

Find the last working version.
3

Restore

Click Restore this version to create a new version with that content.
4

Promote and Set Default

Promote the restored version and set it as default.

​
A/B Testing Results

After testing two prompts:
  1. Review metrics (latency, success rate, user feedback)
  2. Promote the winning prompt to Live
  3. Set it as default
  4. Archive the losing prompt

​
Version Best Practices

Make each version a meaningful improvement. Avoid saving trivial changes.
Always test Draft prompts thoroughly before promoting to Live.
Your endpoint should always have a reliable default prompt.
Try new models, approaches, or major changes in Draft status.
Use the prompt name or description to note significant changes.

​
Calling Specific Versions

While your endpoint uses the default prompt by default, you can call specific prompts: 
# Use default prompt
curl -X POST https://yourcompany.api.endprompt.ai/api/v1/summarize

# Use specific prompt by name
curl -X POST "https://yourcompany.api.endprompt.ai/api/v1/summarize?prompt=detailed-summary"
Only Live prompts can be called directly. Draft prompts can only be tested through the UI.

​
Version Limits

PlanVersion History
FreeLast 10 versions
ProLast 50 versions
EnterpriseUnlimited
When you exceed version limits, oldest versions are archived but not deleted.

​
Next Steps

Testing Prompts

Learn to test prompts effectively

Prompt Snippets

Create reusable template fragments