Novig API keys: what each key can do, and what handing one over means.

• Whoever holds a key can do everything its scope allows, without the account’s password, until the key is revoked. Novig’s docs say a revocation takes effect within 60 seconds.
• A trading key lets the holder place and cancel orders in one subaccount. A management key lets the holder move funds between the cash wallet and subaccounts; the docs describe no withdrawal endpoint.
• A tool that only reads history needs neither, since a management::read key reads it. A narrower scope limits what a leaked or misused key can do.

Novig issues a management key by default, and that scope can move money between the wallet and subaccounts. Realize uses whichever key it is given only to read the account’s fills, transactions, transfers and positions: its venue clients implement no order, transfer or withdrawal call and hold no customer funds, the same rule the Kalshi API key guide describes for Kalshi.

A Novig year can also be assembled by hand. The trading history statement and the other sources are on Novig trade history and data, and the steps from them to a filed return are in How to file Novig taxes.

Does Realize need a Novig API key?

Yes. The key Novig issues by default is the management key, which can move money but places no orders. Realize calls only read endpoints with it: its Novig client implements no order, transfer or withdrawal call. A management::read key, created from the management key, reads the same history and can move nothing.

Can a Novig API key move money?

Only inside the account. As of October 22, 2026, Novig’s API docs mark the management key Money: Yes, which means moving funds between the cash wallet and its subaccounts. The trading key is marked Money: No, and the docs describe no withdrawal endpoint.

What kinds of Novig API key are there?

As of October 22, 2026, Novig’s API docs describe: management key (scope management) (reaches the whole account; Orders: No; Money: Yes; one live per trader. It opens, funds and labels subaccounts, creates and revokes keys, and reads every wallet (orders, fills and positions), but never places an order); trading key (scope trading) (reaches one subaccount; Orders: Yes; Money: No; one live per subaccount. It places and cancels orders and streams the order book and your fills); read-only scopes (management::read, trading::read) (management::read is bound to the trader and trading::read to a subaccount wallet, both with Read access; up to 128 live of each per trader. A management::read key is created with POST /v3/keys, and no key creates a key above itself).

Do I need an API key to get my Novig trade history?

Not for the statement: Novig’s Help Center route is a trading history statement, requested through Live Chat with the period you need; 1 to 2 business days. Reading fills, transactions and transfers from the API takes a key, and a read-only management::read key is enough for it.

What does a Novig key’s scope decide when an app holds it?

What the app can do. A key acts for whoever holds it, so a trading key lets an app place orders and a management key lets it move funds between the wallet and subaccounts. Reading history takes neither: a management::read key reads it.