> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://partner.ninjatrader.com/eval/overview/quick-setup/api-keys/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://partner.ninjatrader.com/_mcp/server.

# API Keys

Secure API key authentication for server-to-server communication and automated trading systems, providing high-performance access to the NinjaTrader Partner API.

## Overview

API Keys provide a secure, efficient authentication method for server-to-server integrations, automated trading systems, and backend applications. API keys don't require user interaction, making them ideal for automated workflows and risk management.

You will be provided with a Staging API key to use for development and testing. Once you are ready to go live, you will be provided with a Production API key to use for real users and production environments. Your Production API key should be beta tested for at least 1 week before actually going live. This will ensure the prop firm application you build will work with the Production API key and the production environment.

## API Key Types

### Production API Keys

* **Use Case**: Real users & production environments

### Staging API Keys

* **Use Case**: Development & testing

## API Key Structure

When you receive an API key, it will include the following fields:

```json
{
  "name": "string",
  "password": "string", 
  "appId": "string",
  "appVersion": "1.0",
  "sec": "string",
  "cid": 0
}
```

`appId` and `appVersion` are free-form strings you choose; they are shown to end users in the Tradovate Trader UI.

When you request an access token, you can also include a `deviceId`: a string of up to 64 characters that uniquely and permanently identifies the device. It's optional but recommended.