> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/faq/endpoints-and-tokens.md).

# Endpoints and tokens

Finding your endpoint URL and token, regions, rotating and sending tokens, and connecting over WebSocket.

<details>

<summary>Where do I find my endpoint URL and token?</summary>

In the [customer dashboard](https://customers.triton.one), click the subscription whose **Type** is your chain and network, for example **Solana Mainnet**.

* **Hostname:** **Endpoints** → **Hostname(s)**.
* **Token:** **RPC / gRPC Tokens** → **Secret token**.
* **Full URL with the token:** **Copy** under **Connection String for Endpoint**.
* **No Endpoints card:** the subscription has no endpoints yet. Contact support to add one.

See [Endpoints and tokens](https://docs.triton.one/account-and-billing/platform-overview.md#endpoints-and-tokens) and [Endpoint hostnames](https://docs.triton.one/using-your-endpoint/endpoints-regions-routing.md#endpoint-hostnames).

</details>

<details>

<summary>Which region do my requests reach?</summary>

* Standard endpoints use BGP Anycast, so requests reach the closest of Triton's 8 cities automatically.
* **Pin a city on shared Solana mainnet:** use `https://<city-code>.rpcpool.com/<your-token>` with `slc`, `nyc`, `pit`, `ams`, `fra`, `lon`, `sgp` or `tyo`. You lose failover between cities.
* Support can also add a hostname for your endpoint that points at one city.

See [Pin a region](https://docs.triton.one/using-your-endpoint/endpoints-regions-routing.md#pin-a-region).

</details>

<details>

<summary>How do I rotate or replace a token?</summary>

These steps also apply if a token leaks.

1. Create a new token and update your services to use it.
2. Before you delete the old token, check its usage in **Metrics**, which doesn't show deleted tokens.
3. Delete the old token, or deactivate it with its toggle. It can take a few minutes to stop working. Delete can't be undone.

* Creating, deactivating and deleting tokens needs the operator role. Otherwise, contact support from the dashboard chat.
* If the dashboard says `Please disable an existing token to create a new one`, your organization has a token limit. Deactivate a token you don't need, or contact support.

See [If a token leaks](https://docs.triton.one/security/authentication.md#if-a-token-leaks).

</details>

<details>

<summary>How do I send my token with a request?</summary>

* **URL path (JSON-RPC and WebSocket):** `https://<your-endpoint>.mainnet.rpcpool.com/<your-token>` or `wss://<your-endpoint>.mainnet.rpcpool.com/<your-token>`.
* **`x-token` header (JSON-RPC, WebSocket and gRPC):** send `X-Token: <your-token>`. On gRPC it is metadata.
* **gRPC:** use the header only. A token in the URL path doesn't work.
* **Browsers:** never put a token in frontend code. Use an allowed origin.

See [Secret tokens (backend)](https://docs.triton.one/security/authentication.md#secret-tokens-backend).

</details>

<details>

<summary>How do I connect over WebSocket?</summary>

* **Connect:** `wss://<your-endpoint>.mainnet.rpcpool.com/<your-token>`, or send the token in the `x-token` header. Browser apps use an allowed origin and no token.
* **Version:** use WebSocket version 13. Other versions get `426`.
* **Reconnect:** a node failure, a load balancer restart or a network path change can close a connection, so reconnect automatically.
* **Limit:** your IP can hold a limited number of open connections. Over it you get `429`. Put many subscriptions on one connection.

See [Protocols and authentication](https://docs.triton.one/using-your-endpoint/endpoints-regions-routing.md#protocols-and-authentication) and [Connection limits](https://docs.triton.one/using-your-endpoint/rate-and-connection-limits.md#connection-limits).

</details>

<details>

<summary>Why are my requests not reaching the region I expect?</summary>

* Anycast sends traffic to the point of presence closest in network terms to where it enters the internet. That is usually the nearest one geographically.
* A VPN or proxy moves that entry point. Test without it.
* Or use a city hostname on shared Solana mainnet. It accepts your token only, and you lose failover between cities.
* If your traffic still reaches the wrong region, contact support.

See [Pin a region](https://docs.triton.one/using-your-endpoint/endpoints-regions-routing.md#pin-a-region).

</details>

***

<i class="fa-life-ring">:life-ring:</i> Contact support by clicking the chat icon in your [customer dashboard](https://customers.triton.one)\ <i class="fa-briefcase">:briefcase:</i> Sales questions? [Contact us](https://triton.one/contact)\ <i class="fa-sparkles">:sparkles:</i> AI agent? Read [llms.txt](https://docs.triton.one/llms.txt)\ <i class="fa-rss">:rss:</i> Follow updates: [Blog](https://blog.triton.one) · [X](https://x.com/triton_one) · [YouTube](https://www.youtube.com/@triton_one_ltd) · [Telegram](https://t.me/tritonone) · [GitHub](https://github.com/rpcpool)
