Endpoints are named references to one or more policy versions. Instead of pointing your API call at a specific policy version, you point it at an endpoint, and control which policy versions the endpoint runs from the app.

Endpoints are useful in the following ways:

1. Separate environments. Define one endpoint for Production that points to your active policy version, and another for Development that points to a version you are still working on. You can test and deploy new policy versions without changing your API call: update which version the endpoint points to, and the switch happens in the app.
2. Run multiple policies at once. Point one endpoint at several policies to evaluate the same content against all of them in parallel, and get a label and decision from each. An endpoint can run up to 10 policies.
3. Switch to new policy versions. If you've made an update in your policy that you want to make live, update the endpoint to put your policy into production. You can either update to a new version or a different policy completely.

Create an endpoint

1. Open Manage Endpoints.
2. Click Create New Endpoint.
3. Enter a name (alphanumeric, underscore, and dash only).
4. Select the policy version or versions this endpoint should run.
5. Add an optional description, like "Production policy for moderating usernames."
6. Click Create Endpoint.

Manage your endpoints

The Manage Endpoints table lists each active endpoint, sortable by name, date created, or date modified. Each endpoint has two actions:

• Show cURL for a ready-to-use API call that evaluates content against the endpoint.
• Edit to change which policies the endpoint runs, or its name or description.

See which endpoints use a policy

Each policy's page shows the endpoints attached to it, so you can check what an endpoint change will affect before you make it.