“token check failed” when saving a Tradier token in Senzoukria

What you see

In API Keys → Tradier, clicking Save shows an error beginning with “token check failed:” followed by the HTTP status and body returned by Tradier. An empty field is refused with “Token cannot be empty.” On success: “Saved - the key answered. What it gives you depends on your plan with that provider, and it is only used once you pick that source in the GEX header.”

Why it happens

The app never stores a dead credential: it asks Tradier for a SPY quote with the token and saves only if that works. The request goes to Tradier’s production API. The app’s own help says real-time OPRA needs a funded Tradier brokerage account and that the free sandbox key is 15-minute delayed; a token issued for another environment can therefore be refused by the production API.

How to fix it

• Create the token in your Tradier brokerage account: Settings → API Access → personal access token, as the in-app help describes.
• Paste it without spaces and save again.
• Once saved, pick “Tradier RT” in the GEX header, “More options” → “Option chain source”.
• If GEX then reports “no usable chains … (token entitlement?)”, check with Tradier that the token can read option chains.

What it is not

• Not a Senzoukria connectivity issue when the error carries a Tradier status code.
• Not a saved token: a failed check leaves the vault unchanged.

When to contact support

If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Copy the error without the token. Eligibility for a Tradier account outside the US is a question for Tradier.