# Endpoints

> Add upstream RPC connections, check health, attach them to Gateway Routes, and manage their lifecycle.

Canonical page: https://rpc.aurpay.net/docs/endpoints

An Endpoint is one upstream connection that a Gateway Route can call after a cache miss or for a request outside Endpoint-free RPC. Endpoints are owned by your Account and can be reused by multiple Apps when their chain, network, and protocol match.

## In brief

- Manual Endpoints are connections you create and maintain; an Account can create up to 20 undeleted manual Endpoints.
- Provider Endpoints are discovered and maintained through a [Provider](https://rpc.aurpay.net/docs/providers.md) and do not count toward the manual Endpoint limit while they remain Provider-managed.
- An Endpoint does not receive traffic until a matching Gateway Route references it.

## Manual and Provider Endpoints

| Origin | Connection owner | Editable fields | Removal |
|---|---|---|---|
| Manual | You | Name, enabled state, URL, and authentication; chain, network, and protocol are fixed after creation | Delete from **Endpoints** or the Management API |
| Provider | Provider synchronization | Name and enabled state; synchronized connection fields are read-only | Remove through the owning Provider |

Deleting a Provider can retain its Endpoints as detached manual inventory or archive unreferenced Endpoints. See [Disable, update, or delete a Provider](https://rpc.aurpay.net/docs/providers.md#disable-update-or-delete-a-provider).

## Add a manual Endpoint

1. **Open the Endpoint registry**

   Open **Endpoints**, stay on the **Endpoints** tab, and select **New endpoint**.

2. **Configure the connection**

   Choose the chain, network, and protocol that the upstream actually serves. The URL must use `http://` or `https://` and must pass the Gateway's outbound destination policy.

   Supported authentication types are no authentication, Bearer, API Key in a named Header, API Key in a query parameter, and API Key in a URL path. The path form uses the placeholder shown by the dashboard, with the secret stored in the structured authentication field.

   Endpoint names are unique within the Account. An Account can create up to 20 undeleted manual Endpoints. Synchronized Provider Endpoints are counted separately while they remain managed; an Endpoint retained and detached during Provider deletion becomes manual inventory and counts against later manual creation.

3. **Check health**

   Select **Check health** to run the Gateway's fixed protocol-specific probe. The result is **Healthy** or **Unhealthy** and records when it was observed. A new Endpoint can show **No recent health data** until a manual probe or forwarded traffic produces an observation.

   A manual health check validates the upstream connection. Validate required methods, archive heights, and vendor namespaces separately against the upstream plan. Runtime routing health and latency are described in [Health and latency](https://rpc.aurpay.net/docs/failsafe/health.md).

4. **Attach the Endpoint to a Route**

   Open the target App, select its Gateway for the same chain and network, and add the Endpoint to the default JSON-RPC or HTTP API Route. You can then configure priority failover or weighted load balancing. A JSON-RPC method Route can select a different Endpoint set for specific methods.

## Route bindings

An Endpoint's Route bindings show every active Gateway Route that references it, including the App and Gateway, Route type, JSON-RPC method scope, strategy, Route version, and target count.

You can remove one binding without deleting the Endpoint. Binding updates use the Route's expected version, so reload and retry after a version conflict rather than overwriting a newer Route configuration.

- Removing the final target from a JSON-RPC method Route deletes that empty method Route; those methods fall back to the default Route.
- Default JSON-RPC and HTTP API Routes remain present when their final target is removed, with an empty target list.
- Removing one target preserves the ordering of the remaining targets.

## Update or delete an Endpoint

Endpoint updates use an expected version. Reload the record before retrying a version conflict.

Deleting a manual Endpoint atomically removes it from all active Routes and soft-deletes the Endpoint. A bulk deletion accepts up to 50 unique, existing, account-owned manual Endpoint IDs and deletes the complete set atomically.

Remove Provider-managed Endpoints through their owning Provider. Review the Provider deletion impact before deciding whether to retain detached Endpoints or archive unreferenced ones.

> Before deleting an Endpoint, keep at least one matching target on every default Route that requires stable upstream coverage.

## Security guidance

- Treat upstream URLs containing credentials and all authentication secrets as sensitive.
- Use the structured authentication fields instead of embedding credentials into application source code.
- Use redacted Endpoint identifiers in logs, support requests, and public issue trackers.
- A PAT needs `endpoint-secrets:read` to receive effective URLs and secret-bearing Endpoint details; other Endpoint responses are redacted.

## Related

- [Providers](https://rpc.aurpay.net/docs/providers.md)
- [Routing and reliability](https://rpc.aurpay.net/docs/reliability.md)
- [Failsafe](https://rpc.aurpay.net/docs/failsafe.md)
- [Management API](https://rpc.aurpay.net/docs/management-api.md)