Why did saving succeed if the keys are wrong?

Alpaca keys are not tested at save time in 0.46.0; the test happens on the first data request.

Is the Alpaca GEX real time?

Without the paid OPRA add-on, the indicative feed is labelled “ALPACA · 15 MIN DELAY”.

“Alpaca unauthorized (HTTP 401/403) — check your API keys” on GEX

Alpaca keys are stored in Senzoukria without an online test, so a wrong key only fails when GEX or Option Flow asks Alpaca for data. The failure shows as “Alpaca unauthorized (HTTP 401/403) — check your API keys”; a rate limit shows as HTTP 429.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Unauthorized: “Alpaca unauthorized (HTTP 401/403) — check your API keys”
Rate limit: “Alpaca rate limited (HTTP 429) — retry later”
Missing keys: “Alpaca API keys not configured — set them in Settings”
Default feed: Indicative options feed: “ALPACA · 15 MIN DELAY”

What you see

The GEX page shows an error banner and the status chip turns to “NO DATA” (“The last request failed: …”) or “PROVIDER ERROR” when an older chain is still displayed. The error text is “Alpaca unauthorized (HTTP 401/403) — check your API keys”, or “Alpaca rate limited (HTTP 429) — retry later”.

Why it happens

Saving Alpaca keys only checks that both the Key ID and the secret are filled (“Key ID and secret are both required.”). The keys go to the OS keychain without calling Alpaca. The first real request tells whether Alpaca accepts them. A 401 or 403 means Alpaca refused the pair: a typo, a key regenerated since, or keys from another environment. A 429 means too many requests in a short time.

The OPRA checkbox (“OPRA real-time subscription (paid Alpaca add-on)”) switches the label to “ALPACA OPRA · REAL-TIME”; tick it only if your Alpaca account has that subscription.

How to fix it

Open Account → Broker Connections → API Keys → Alpaca, click Remove, then paste the Key ID and the secret again and save.
Regenerate the keys in Alpaca if you are not sure they are current.
On 429, wait a few minutes; turning off “Auto-refresh every 5 s” in the GEX header menu lowers the request rate.
Or switch the chain source to Tradier or Market Data in “More options” → “Option chain source”.

What it is not

Not a Senzoukria licence problem.
Not the delay: a 15-minute delay on the indicative feed is shown by the source chip, not as an error.

When to contact support

When none of this helps, write to support through Menu → Report a problem or on the Senzoukria Discord. Include the exact error line and whether the OPRA box is ticked. Never paste your keys.

In the same section

This page in other languages

Frequently asked questions

Why did saving succeed if the keys are wrong?: Alpaca keys are not tested at save time in 0.46.0; the test happens on the first data request.
Is the Alpaca GEX real time?: Without the paid OPRA add-on, the indicative feed is labelled “ALPACA · 15 MIN DELAY”.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.