# Action Required: Pyth Pro History API Auth Required Starting July 24

**URL:** <https://dev-forum.pyth.network/t/action-required-pyth-pro-history-api-auth-required-starting-july-24/808>\
**Category:** Announcements\
**Tags:** announcements\
**Created:** [July 8, 2026, 2:01pm UTC](https://dev-forum.pyth.network/t/action-required-pyth-pro-history-api-auth-required-starting-july-24/808 "2026-07-08T14:01:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aditya520](https://yyz2.discourse-cdn.com/flex034/user_avatar/dev-forum.pyth.network/aditya520/32/12_2.png) [@Aditya520](https://dev-forum.pyth.network/u/Aditya520)\
**Post date:** [July 8, 2026, 2:01pm UTC](https://dev-forum.pyth.network/t/action-required-pyth-pro-history-api-auth-required-starting-july-24/808/1 "2026-07-08T14:01:37Z")

</div>

Hey everyone,

Starting **July 24, 2026** , the following **Pyth Pro History API** endpoints will require API key authentication:

- `GET /v1/{channel}/price`
- `GET /v1/{channel}/history`
- `POST /v1/price`

API key authentication is already supported in production today. Please update your requests to include:

```bash
http
Authorization: Bearer <PYTH PRO API KEY>

```

If you call these endpoints from a browser or frontend app, **do not expose your API key client-side**. The recommended setup is to route requests through your own backend or proxy.

For frontend apps that need a client-safe option and do not want to run their own proxy, we expect JWT-based authentication to be available around **July 10**.

Unauthenticated access to these endpoints will be disabled on **July 24**.

---

<div class="post-metadata">

**Author:** ![KemarTiti](https://yyz2.discourse-cdn.com/flex034/user_avatar/dev-forum.pyth.network/kemartiti/32/6_2.png) [@KemarTiti](https://dev-forum.pyth.network/u/KemarTiti)\
**Post date:** [July 13, 2026, 11:16am UTC](https://dev-forum.pyth.network/t/action-required-pyth-pro-history-api-auth-required-starting-july-24/808/2 "2026-07-13T11:16:56Z")

</div>

Quick update for teams using these endpoints from a browser/frontend:

The preferred setup is still to keep your Pyth Pro API key server-side, behind your own backend or proxy. Please don’t expose the API key directly in client-side code.

For teams that need a frontend-safe option and don’t want to route every request through their own proxy, the JWT auth flow is now available here:

> **[Swagger UI](https://pyth.dourolabs.app/docs/?urls.primaryName=Auth+API#/Auth/mint-token)**

The basic flow is:

1. Your browser client asks your backend for a JWT.
2. Your backend calls `POST /auth/token` using your secret Pyth Pro API key.
3. Your backend returns the JWT to the browser client.
4. The browser client uses that JWT as a bearer token:

```http
Authorization: Bearer _*_

```

Docs: [Frontend Authentication | Pyth Developer Hub](https://docs.pyth.network/price-feeds/pro/frontend-auth)  
Example app: [pyth-examples/pro/frontend-jwt-auth at main · pyth-network/pyth-examples · GitHub](https://github.com/pyth-network/pyth-examples/tree/main/pro/frontend-jwt-auth)