Skip to main content
Endpoints are the foundation of Endprompt. They provide stable API URLs that your applications call, while giving you complete flexibility to change the underlying prompts and models.

​
What is an Endpoint?

An endpoint is a stable API contract that defines:
  • URL Path — Where your API lives (e.g., /api/v1/summarize)
  • Input Schema — What data your API accepts
  • Output Schema — What data your API returns
  • Default Prompt — Which prompt handles requests
POST https://yourcompany.api.endprompt.ai/api/v1/summarize
     └────────────────────────────────┘ └──────────────┘
              Your tenant domain           Endpoint path

​
Why Endpoints Matter

Stable Integration

Your application code calls the same URL forever. Change prompts without deployments.

Schema Validation

Invalid requests are rejected before hitting the LLM, saving costs and preventing errors.

Multiple Prompts

Attach multiple prompts to one endpoint. A/B test, version, and rollback independently.

Auto-Generated Docs

Every endpoint gets OpenAPI documentation with code samples automatically.

​
Endpoint Properties

PropertyDescription
NameHuman-readable name (e.g., “Text Summarizer”)
PathAPI URL path, must start with /api/v1/
CategoryOrganizational grouping (e.g., “Content”, “Analysis”)
DescriptionWhat the endpoint does
VisibilityPublic (visible to all team members) or Internal
Default PromptThe prompt used when no specific prompt is requested

​
Endpoint Lifecycle

1

Create

Define the endpoint with a name, path, and description.
2

Configure Schema

Add input fields with types and validation rules. Optionally define output schema.
3

Attach Prompts

Create one or more prompts with different models or approaches.
4

Test

Use the built-in test runner to validate your prompts work correctly.
5

Set Default

Promote a prompt to Live status and set it as the endpoint default.
6

Deploy

Your endpoint is ready! Call it from your application.

​
Organizing Endpoints

​
Categories

Group related endpoints with categories:
  • Content — Summarization, rewriting, translation
  • Analysis — Sentiment, classification, extraction
  • Generation — Creative writing, code generation
  • Conversation — Chatbots, Q&A systems
Create categories that match your product domains. You can filter and search by category in the endpoints list.

​
Naming Conventions

We recommend these patterns:
PatternExampleUse Case
Resource + Actiontext-summarizerSingle-purpose endpoints
Domain / Actionsupport/classify-ticketDomain-specific endpoints
Version prefixv2/enhanced-summaryWhen you need breaking changes

​
Viewing Endpoints

The Endpoints page shows all your endpoints in a list or grid view:
  • Search — Find endpoints by name or path
  • Filter by Category — Show only specific categories
  • Sort — By name, creation date, or recent activity
  • Quick Stats — See request counts and success rates at a glance

​
Next Steps

Create an Endpoint

Step-by-step guide to creating your first endpoint

Define Input Schema

Learn to specify what data your endpoint accepts