> ## Documentation Index > Fetch the complete documentation index at: https://docs.novig.com/llms.txt > Use this file to discover all available pages before exploring further. # Request new market strike > Request a new strike for an existing market. This sends a notification to the Novig team, who may then choose to create the market. A successful response does **not** guarantee that the market will be created. The strike value accepts whole numbers or half-points (values ending in `.5`). Whole numbers are automatically converted to `.5` strikes (e.g. `300` becomes `300.5`). The request will be rejected if a market with the same event, type, player, and strike already exists. **Rate limit:** 100 Requests Per Second. ## OpenAPI ````yaml /api-reference/spec-files/openapi31.json post /nbx/v2/emm/strike-requests openapi: 3.1.0 info: title: NBX API description: >+ ## API Overview The NBX API is designed with a tri-interface architecture: - **REST API** - **URL:** `https://api.novig.us/nbx/v2` - **Constraints:** - **Rate limits:** - Order placement (single and batch): 20 requests per second - Order cancellation: 1,000 requests per second - Kill switch: 1 request per 30 seconds - Data retrieval: 100 requests per second - User history (`/fills`, `/orders`, `/transactions`): 16 requests/second burst, 256 requests/minute sustained - **Timeout:** 5 seconds - **Features:** - Place, cancel, and query orders. - Retrieve market data and positions. - Manage account settings and balances. - **Best Practices:** - Use appropriate HTTP methods. - Include `Authorization` and `Content-Type` headers. - Implement exponential backoff for handling rate limits and robust error handling. - **WebSocket API** - **URL:** `wss://api.novig.us/tape` - **Constraints:** - **Keepalive:** protocol-level WebSocket Ping every 15 seconds; standard clients respond automatically, and a client that misses a full interval is disconnected - **Features:** - Real-time order book ticks. - Real-time market lifecycle updates. - Private place, fill, and cancel notifications. - Protocol-level heartbeat to ensure connection health. - **Best Practices:** - Implement reconnection logic with exponential backoff. - Process messages sequentially to maintain order book integrity. - Appropriately handle various event types. - Subscribe to specific market events or to the global tape. - **GraphQL API** - **URL:** `https://gql.novig.us/v1/graphql` - **Constraints:** - **Rate limit:** 650 requests per minute - **Timeout:** 2 seconds - **Features:** - Interactive Explorer available via [**Hoppscotch GraphQL Sandbox**](https://hoppscotch.io/graphql) - Flexible querying of market data and prices with tailored filters. - Access historical data and statistics. - Role-based access control with baseline lurker permissions. - **Best Practices:** - Use GraphQL for historical analysis and non-time-critical queries. - Opt for the WebSocket API for real-time data needs. ## Authentication The NBX API uses [**OAuth 2.0 Client Credentials**](https://auth0.com/docs/get-started/authentication-and-authorization-flow/client-credentials-flow) with JSON Web Tokens (JWT). 1. **Obtain Credentials:** Request your client ID and secret from Novig. 2. **Request an Access Token:** Send a POST request to the OAuth endpoint. For example: ```bash curl --request POST --url https://auth.novig.us/oauth/token --header "Content-Type: application/json" --data '{ "audience" : "https://api.novig.us", "grant_type" : "client_credentials", "client_id" : "YOUR_CLIENT_ID", "client_secret" : "YOUR_CLIENT_SECRET" }' ``` 3. **Use the Token:** Include the token in your requests by setting the HTTP header: ```bash Authorization: Bearer YOUR_ACCESS_TOKEN ``` > **Note:** For integration in the QA environment, you'll need to use different endpoints: > - **Issuer:** `https://auth-qa.novig.us` > - **Audience:** `https://api-qa.novig.us` > - **API Base URL:** `https://api-qa.novig.us` version: 0.0.44 contact: name: Contact url: https://novig.us email: tech@novig.us servers: - url: https://api.novig.us description: Production - url: https://api-qa.novig.us description: QA security: [] tags: - name: Orders description: Endpoints for managing orders and trades - name: Markets description: Endpoints for accessing market data and order books - name: Events description: Endpoints for discovering events and fetching event-related data - name: Account description: Endpoints for managing account settings and balances - name: Positions description: Endpoints for accessing positions and fills - name: WebSockets description: Channels for real-time market data and order updates - name: GraphQL description: GraphQL API for querying market data and prices paths: /nbx/v2/emm/strike-requests: post: tags: - Markets summary: Request new market strike description: >- Request a new strike for an existing market. This sends a notification to the Novig team, who may then choose to create the market. A successful response does **not** guarantee that the market will be created. The strike value accepts whole numbers or half-points (values ending in `.5`). Whole numbers are automatically converted to `.5` strikes (e.g. `300` becomes `300.5`). The request will be rejected if a market with the same event, type, player, and strike already exists. **Rate limit:** 100 Requests Per Second. operationId: requestStrike parameters: [] requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/StrikeRequestDto' responses: '201': description: Strike request submitted content: application/json: schema: $ref: '#/components/schemas/StrikeRequestResponseDto' '400': description: >- Bad request — market not found, invalid strike value, or strike already exists for this market type x-code-samples: - lang: bash label: cURL Example source: |- curl -X POST "$API/emm/strike-requests" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "marketId": "550e8400-e29b-41d4-a716-446655440000", "strike": 300.5 }' components: schemas: StrikeRequestDto: type: object properties: marketId: type: string format: uuid description: The ID of an existing market to request a new strike for example: 550e8400-e29b-41d4-a716-446655440000 strike: type: number description: >- The requested strike value. Accepts whole numbers (e.g. 300) or half-points (e.g. 300.5). Whole numbers are automatically converted to .5 strikes. example: 300.5 required: - marketId - strike StrikeRequestResponseDto: type: object properties: message: type: string description: >- Confirmation message with the event description and final strike value example: Strike request created for TOR @ CLE at 300.5 ````