Quickstart

Authenticate with Ignite API and make your first request.

This guide shows the minimum flow for calling Ignite API.

Use {BASE_URL} as the firm host provided during onboarding. Dashboard pages use root-level paths on that host, while most API endpoints are prefixed with /api/. The login endpoint is /auth/login/.

​

Prerequisites

Before you begin, you must have:

• An Ignite user account with API access.
• The correct {BASE_URL} for your firm.
• The email and password for the account you want to authenticate.

If you do not have your firm slug or {BASE_URL} yet, start with URLs and credentials.

​

Authenticate

1. Request a session token

   Send your credentials to POST /auth/login/.

   curl -X POST "{BASE_URL}/auth/login/" \
     -H "Content-Type: application/json" \
     -d '{
       "email": "[e-mail]",
       "password": "your-password"
     }'
   
2. Read the token

   The response includes a key. Session tokens are short-lived and expire after 3 hours.

   {
     "key": "123abc456def789",
     "prop_firm": "demo-firm",
     "expires_at": "2026-02-04T12:00:00Z"
   }
   
3. Send the token with each request

   Use the token in the Authorization header with the Token prefix.

   curl "{BASE_URL}/api/accounts/summary/" \
     -H "Authorization: Token 123abc456def789"
   

​

Authorization header

Every authenticated request must include:

Authorization: Token <token>

​

Common IDs

Some endpoints require IDs from Ignite operational views:

• challenge_id: Prop Tech Configuration -> Challenges
• user_id: Tickblaze Manager -> Users
• account_id: Tickblaze Manager -> Accounts

After authentication, review account provisioning and entitlements before automating account creation. Market data access requires an explicit entitlement authorization step.