Forex Sentiment API

Quickstart

Bearer header only. Keys are never accepted in the URL or query string.

curl -H "Authorization: Bearer $FXNB_KEY" \
  https://fxnewsbias.com/api/v1/sentiment

Python

Official client, MIT licensed, no required dependencies.

pip install fxnewsbias

from fxnewsbias import Client

fx = Client("fxnb_live_...")

# the whole point: a yes or no on the pair you are about to trade
fx.sentiment().favours("AUD/USD")   # 'long', 'short', or None
fx.sentiment().spread("AUD/USD")    # 13  (AUD 68 - USD 55)

The scores move every few hours, so follow() waits for the next one instead of polling on a timer. A 15-minute loop spends 96 calls a day; this spends about 8.

for s in fx.follow():
    print(s["AUD"].score)   # blocks until the data actually changes

Gold, on Pro keys, from fxnewsbias 1.2.0 (pip install -U fxnewsbias). Details under Markets (Pro).

m = fx.markets()
gold = m.get("XAU")                # None until the first gold read
if gold:
    print(gold.score, gold.pair.bias)   # e.g. 64 Bullish

Source on GitHub · PyPI

Response shape

{
  "schema": "fxnb.sentiment.v1",
  "generated_at": "2026-08-21T09:00:12Z",
  "next_update_expected": "2026-08-21T12:00:00Z",
  "attribution": {
    "required": true,
    "text": "Data by FXNewsBias",
    "url": "https://fxnewsbias.com"
  },
  "data": [
    { "currency": "USD", "score": 72, "bias": "Bullish",
      "updated_at": "2026-08-21T09:00:00Z" },
    ... 7 more
  ]
}

Tiers and rate limits

• Both tiers reset at 00:00 UTC. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset
• One over the limit returns 429 with a Retry-After header
• The allowance follows the account, not the key, so regenerating a key does not reset it
• Free responses include "delayed": true, "delay_hours": 3 so the freshness is never ambiguous

Errors

• Branch on error, never on message. The code is part of the frozen contract, the wording is not
• Working integration suddenly returning 401? Regenerating a key replaces the previous one. If someone clicked regenerate in the panel, anything still sending the old key stops there. Create a new key and update your integration
• 502 and 500 are ours and safe to retry. 400, 401 and 404 will not change on a retry, so fix the request instead

Attribution and terms

• Wherever the data is displayed or republished, keep the attribution "Data by FXNewsBias" linking to https://fxnewsbias.com. It ships in every response
• Free tier is for personal and non-commercial projects. A Pro subscription covers commercial use inside your own product
• No redistribution, resale, or using the data to build a competing sentiment service, on either tier
• One key per account. Sharing a key across separate users or products is not permitted and is detectable
• One key for the life of the account. It upgrades to Pro automatically when your subscription or trial starts, and returns to the free tier when Pro ends. The key string never changes, so your integration keeps working either way, on free limits afterwards
• Questions, higher volume, or a data licence: contact@fxnewsbias.com

curl

curl -H "Authorization: Bearer $FXNB_KEY" \
  https://fxnewsbias.com/api/v1/markets

curl -H "Authorization: Bearer $FXNB_KEY" \
  "https://fxnewsbias.com/api/v1/markets/history?symbol=XAU&from=2026-10-01&limit=100"

Python, with requests

import requests

H = {"Authorization": "Bearer " + FXNB_KEY}
BASE = "https://fxnewsbias.com/api/v1/markets"

r = requests.get(BASE, headers=H)
if r.status_code == 403:   # free key: gold is a Pro feature
    raise SystemExit(r.json()["message"])

# data is a list that grows, so look gold up by symbol
gold = next((m for m in r.json()["data"]
             if m["symbol"] == "XAU"), None)
if gold:
    # e.g. 64 Bullish Bullish
    print(gold["score"], gold["bias"], gold["pair"]["bias"])

# settled, aligned, contra, aligned_pct, gold only
calls = requests.get(BASE + "/session-bias/history",
                     headers=H, params={"symbol": "XAU"}).json()
print(calls["summary"])

The official Python client covers the same four endpoints from fxnewsbias 1.2.0: fx.markets(), fx.markets_history("XAU"), fx.market_session_bias("XAU") and fx.market_session_bias_history("XAU"). A free key raises PlanError with the server's message.

Response shape

{
  "schema": "fxnb.markets.v1",
  "generated_at": "2026-10-05T09:00:14Z",
  "next_update_expected": "2026-10-05T12:00:00Z",
  "attribution": { ... same object as every response ... },
  "data": [
    {
      "symbol": "XAU", "name": "Gold",
      "score": 64, "bias": "Bullish",
      "drivers": ["Softer US inflation data lifts rate cut expectations",
                  "Central bank gold buying continues"],
      "updated_at": "2026-10-05T09:00:09Z",
      "pair": { "name": "XAU/USD", "quote": "USD",
                "quote_score": 51, "gap": 13, "bias": "Bullish" }
    }
  ]
}

Fields

Behaviour

• A free key gets 403 {"error":"pro-only","message":"Gold and other markets are a Pro feature.","upgrade":"https://fxnewsbias.com/pricing"}, before any allowance is claimed
• A missing or unsupported symbol is a 400 {"error":"bad-symbol"}, and a bad date or page parameter gets the same codes as the sentiment history. Both are checked before the allowance is claimed
• Each call that passes those checks counts once against the same 1,000-a-day Pro allowance. /api/v1/usage shows the combined total
• Gold is scored every 3 hours, on the same cycle as the currencies. Session calls are published on weekdays for the Asia, London and New York sessions, like the forex scorecard, and are never mixed into the forex scorecard or its hit rate
• /api/v1/markets lists only markets that already have a reading, so data can be an empty list before a market's first read. Find a market by symbol, never by position
• /api/v1/markets/session-bias returns "data": null until a first call exists. The history endpoints give the start of each gold series in coverage_from
• Gold prices used to settle session calls are an hourly reference, indicative and not an official benchmark