Rithmic login failed: “permission denied” (rp_code 13) in Senzoukria

When Rithmic answers a Senzoukria login with rp_code 13 “permission denied”, the account is refused on that system for the R | Protocol API; the code does not say which layer refused it. The app lists the causes to check, cheapest first, and never treats it as a rights verdict.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Message
“Rithmic REFUSED this login on system « {system} » (rp_code 13, « permission denied ») FOR THE R | PROTOCOL API”
Where
“Test failed: …” in the connection form, the Authentication step of the connection diagnostic, or a Connect attempt
Step that refused
Login on the ticker plant
Applies to
Senzoukria desktop 0.46.0

What you see

The raw Rithmic refusal is replaced by an explanation that starts with “Rithmic REFUSED this login on system « {system} » (rp_code 13, « permission denied ») FOR THE R | PROTOCOL API — the interface this app speaks.” It then separates what the code establishes (the login was refused) from what it does not (which layer refused it), and ends with a line starting “DIAGNOSTIC — copy this line, it holds no secret”.

Why it happens

At login, rp_code 13 means Rithmic does not accept this account on this system for R | Protocol. An unknown system name is answered with a different code (1067), so the system name exists; but an account issued by one firm and presented to another firm’s system is simply unknown there and comes back with this same code. The refusal names no field, so a mistyped user ID or password is not ruled out either. The app deliberately does not read “permission” as “insufficient rights”: that reading turned out wrong four times in its bug register.

How to fix it

  • For a prop-firm account, check the user ID: the app warns when it looks like an e-mail address, because the R | Protocol login of a prop firm is the short user ID from the activation e-mail. On direct Rithmic systems (names starting with “Rithmic”) the login is an e-mail, and the app does not raise that warning there.
  • If the account is a free demo taken directly from Rithmic, stop here: R | Protocol is not available to demos with live market data.
  • Confirm the system: click “Fetch live system list from gateway” and pick the exact name your firm gave you, spaces and capitals included. If you recognise your prop firm in the list the explanation prints, your account lives there.
  • A brand-new account may not be provisioned yet: if you signed the market data agreements today, retry at the next session open.
  • If none of this applies, ask your broker in the words the app gives: “is my account enabled for the R | PROTOCOL API — not R | API+, not R | Trader Pro — and under which system name?”

What it is not

  • Not proof that your rights are short. Refusals worded identically have had different causes.
  • Not contradicted by R | Trader Pro connecting: it speaks another protocol with another entitlement.
  • Not a routing problem once the diagnostic step “Gateway and system agree” has passed.

When to contact support

Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Paste the DIAGNOSTIC line: it carries rp_code, step, system, API and app version, and deliberately leaves out your user ID. Your broker needs the same line for its own ticket.

In the same section

This page in other languages

Frequently asked questions

Why does the app not just say my permissions are insufficient?
Because the code does not establish it. At login, rp_code 13 most often means the account is unknown on that system; treating it as a rights problem sent users to the wrong fix several times.
Is my password stored while I test?
The test uses the password typed in the form; saved credentials live in the operating system keychain and are never written to a file, a log or a screen.

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.