Gaudio Index API

The Gaudio Index API exposes the Gaudio Indicator values over HTTPS, so you can read them from your own dashboard, trading platform or alerting system. Two endpoints: the latest snapshot, and every snapshot of the current session.

Access is not part of any subscription plan. It is granted under a separate, custom agreement, negotiated case by case, and is normally reserved for institutional clients — desks, funds and firms integrating the indicator into their own systems. No Gaudio OTT plan, Ultra included, includes API access.


Base URL	`https://api.gaudioott.com`
Authentication	Bearer token in the `Authorization` header
Symbols	`ES` and `SPX`, via the `symbol` query parameter
Format	JSON, ISO 8601 timestamps, nullable numeric fields
Namespace	`/v1`

What the API returns

The API serves the real-time values of the Gaudio Indicator plus the intraday history of the current session. Values are updated during market hours, typically once a minute.

It is designed for server-to-server consumption: proprietary dashboards, trading platforms, alerting systems and integrations.

Requesting access

The API is not self-service and there is no page in the app that issues a token. Access starts with a conversation:

Contact Gaudio OTT — a support request from inside the app is enough to open the discussion.
Describe the integration: what you are building, which of the two symbols you need, the expected request rate, and whether the data stays inside your organisation.
The commercial terms are agreed separately from any subscription — scope, duration, permitted use and price are set in that agreement, not by a plan.
The token is issued once the agreement is in place, by the Gaudio OTT team.

Requests are assessed individually, and access is not guaranteed.

Authentication

Every request must carry a Bearer token, issued by the Gaudio OTT team under the agreement described above.

Authorization: Bearer YOUR_API_TOKEN
Accept: application/json

Operational notes:

the token is shown once, at issue time — store it immediately;
keep it secret, and rotate it if you suspect it has leaked;
if it is compromised, ask for it to be revoked and reissued.

GET /v1/gaudio-index/current

Returns the latest available snapshot for the requested symbol. This is the endpoint to use for live dashboards, widgets and periodic polling.

GET https://api.gaudioott.com/v1/gaudio-index/current?symbol=ES
Authorization: Bearer YOUR_API_TOKEN
Accept: application/json

Element	Where	Description
`Authorization`	Header	Bearer token issued by Gaudio OTT. Required.
`symbol`	Query string	`ES` or `SPX`. Always send it explicitly.

Example ES response:

{
  "riferimento": 7008.5,
  "supMM": 6974.25,
  "resMM": 7042.75,
  "supDay": null,
  "resDay": null,
  "volGaudioIndex": 12.4,
  "vCall": 0.0031,
  "vPut": -0.0017,
  "vCallRaw": 0.000124,
  "vPutRaw": -0.000068,
  "data": "2026-05-12T14:32:00.000Z"
}

Example SPX response:

{
  "riferimento": 5240.13,
  "supMM": 5214.75,
  "resMM": 5265.5,
  "supDay": 5200,
  "resDay": 5275,
  "data": "2026-05-12T14:32:00.000Z"
}

GET /v1/gaudio-index/day

Returns every snapshot of the current session for the requested symbol. Use it for intraday charts, session replay and rebuilding the live history.

GET https://api.gaudioott.com/v1/gaudio-index/day?symbol=ES
Authorization: Bearer YOUR_API_TOKEN
Accept: application/json

{
  "date": "2026-05-12",
  "count": 346,
  "data": [
    {
      "riferimento": 7008.5,
      "supMM": 6974.25,
      "resMM": 7042.75,
      "supDay": null,
      "resDay": null,
      "volGaudioIndex": 12.4,
      "vCall": 0.0031,
      "vPut": -0.0017,
      "vCallRaw": 0.000124,
      "vPutRaw": -0.000068,
      "data": "2026-05-12T14:30:00.000Z"
    }
  ]
}

Each element of data follows the same schema as the /current payload. Analytic fields may be present, null, or not yet populated at some points in the session.

Field reference

Field	Type	Description	Notes
`riferimento`	`number \| null`	Main reference value of the requested feed.	On `SPX` it is the raw SPX reference.
`supMM`	`number \| null`	Market maker support level.	On `SPX` it exposes the raw SPX level.
`resMM`	`number \| null`	Market maker resistance level.	On `SPX` it exposes the raw SPX level.
`supDay`	`number \| null`	Lower daily level of the public contract.	On `SPX` it carries the max put strike of the GEX model.
`resDay`	`number \| null`	Complementary daily level.	On `SPX` it carries the max call strike of the GEX model.
`volGaudioIndex`	`number \| null`	Synthetic Gaudio volatility index.	`null` while the value is not yet available.
`vCall`	`number \| null`	Normalised change in average call implied volatility.	Typically populated on the `ES` feed.
`vPut`	`number \| null`	Normalised change in average put implied volatility.	Typically populated on the `ES` feed.
`vCallRaw`	`number \| null`	Unnormalised counterpart of `vCall`.	Optional analytic field.
`vPutRaw`	`number \| null`	Unnormalised counterpart of `vPut`.	Optional analytic field.
`data`	`string`	ISO 8601 timestamp of the update.	In the `/day` payload, the timestamp of each sample.

Client rule: treat every numeric field as nullable, do not assume the analytic metrics exist on every symbol, and drive your UI from the symbol you requested.

Symbol modes

Both endpoints accept symbol=ES and symbol=SPX, and it is best to send it explicitly rather than rely on a default.

In SPX mode the public field names stay the same, but the values represent raw SPX levels: in particular supDay and resDay carry SPX levels derived from the GEX put and call strikes. Clients written before the symbol parameter existed should add it to the URL and tolerate optional fields; the base numeric format is unchanged.

Errors

// 401 Unauthorized
{ "error": "Unauthorized", "message": "Missing or invalid API token" }

// 403 Forbidden
{ "error": "Forbidden", "message": "The API token has been disabled" }

Timeouts and network errors: retry with exponential backoff and log the failed requests.
Inconsistent parameters: validate symbol client-side before sending the request.

Integration examples

const API_TOKEN = process.env.GAUDIO_API_TOKEN;
const symbol = 'ES';

async function getGaudioCurrent() {
  const response = await fetch(
    `https://api.gaudioott.com/v1/gaudio-index/current?symbol=${symbol}`,
    {
      headers: {
        Authorization: `Bearer ${API_TOKEN}`,
        Accept: 'application/json',
      },
    }
  );
  if (!response.ok) {
    throw new Error(`HTTP error ${response.status}`);
  }
  return response.json();
}

import os
import requests

API_TOKEN = os.environ["GAUDIO_API_TOKEN"]
SYMBOL = "SPX"

response = requests.get(
    "https://api.gaudioott.com/v1/gaudio-index/day",
    params={"symbol": SYMBOL},
    headers={
        "Authorization": f"Bearer {API_TOKEN}",
        "Accept": "application/json",
    },
    timeout=10,
)

response.raise_for_status()
payload = response.json()

curl -X GET "https://api.gaudioott.com/v1/gaudio-index/current?symbol=ES" \
  -H "Authorization: Bearer $GAUDIO_API_TOKEN" \
  -H "Accept: application/json"

Best practices and limits

The API is built for frequent but controlled reads. The recommended shape is one-minute polling, a short local cache, and robust handling of nulls and errors.

Token: keep it in environment variables or a secret manager, never in a public frontend.
Caching: a cache with a TTL of about 60 seconds reduces load and stabilises your UI.
Parsing: treat every numeric value as optional and design clear visual fallbacks.
HTTPS only: requests must go over HTTPS.
Rate: avoid aggressive polling below one minute unless agreed otherwise.
Market hours: some values are only populated during the market windows they belong to.
Compatibility: if you integrate SPX, validate the meaning of supDay and resDay inside your own application domain.

Common mistakes

Omitting symbol. Send it explicitly on every request; relying on an implicit default makes your integration fragile.
Assuming fields are always present. Any numeric field can be null, especially early in the session.
Polling faster than the data changes. Values update about once a minute; a tighter loop adds load without adding information.
Shipping the token to the browser. Proxy the call through your own backend instead.

Frequently asked questions

How do I get a Gaudio OTT API token?

API access is not part of any subscription plan, not even Ultra. It is granted under a separate custom agreement, negotiated case by case, and is normally reserved for institutional clients integrating the indicator into their own systems. Start by contacting Gaudio OTT, for example with a support request from inside the app, describing the integration you want to build. The token is issued by the team once the agreement is in place, and is shown once, so store it immediately.

Is the API included in my plan?

No. No plan includes API access, Ultra included. The API sits outside the subscription tiers entirely and requires its own agreement, which is normally made with institutional clients rather than individual traders.

Which symbols does the Gaudio Index API support?

Two: ES and SPX, passed as the symbol query parameter on both endpoints. In SPX mode the field names are unchanged but the values are raw SPX levels, and supDay and resDay carry SPX levels derived from the GEX put and call strikes.

How often is the API updated?

Typically once a minute during the market session. Polling once a minute with a local cache of about 60 seconds is the recommended pattern; anything faster adds load without adding information.

Why are some fields null?

Because they are nullable by contract. A metric can be null early in the session, in particular market windows, or when the value has not been computed yet. Treat every numeric field as optional and provide a visual fallback.

What is the difference between the current and day endpoints?

/v1/gaudio-index/current returns the single latest snapshot, and is the one to poll for live dashboards and widgets. /v1/gaudio-index/day returns every snapshot of the current session in one array, and is the one for intraday charts and session replay.

What happens if my API token is disabled?

The API answers 403 Forbidden with the message that the token has been disabled. Handle it distinctly from 401 Unauthorized, which means the token is missing or invalid, and contact Gaudio OTT to have a token reissued.

Ready to use Gaudio OTT?

Open your free account and put what you just read into practice.

Start free