> ## 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. # Place order batch > Submit multiple orders (maximum 1024) at once to be processed in a batch. This operation does not make guarantees about the successful execution of all orders, it only places each in the matching engine queue. We book every order or none. We price each order on its own, not the batch total. We refuse the batch when your balance cannot cover its largest order by itself. The batch total may exceed your balance. Each order still needs collateral when it reaches the book, so we can reject an order after we book it. - `201`: we booked every order. - `422`: we booked no order. A balance refusal sets `code` to `INSUFFICIENT_BALANCE`. Its `errors` list each order your balance cannot cover on its own. `index` is the order's position in your request, counting from zero. Your order-volume budget is charged for the orders you send, not for the orders we book. **Rate limit:** 64 requests per second. ## OpenAPI ````yaml /deprecated/api-reference/spec-files/openapi31.json post /nbx/v2/emm/orders/batch 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.com/nbx/v2` - **Constraints:** - **Rate limits:** - Single-order placement: 1024 requests per second - Batch placement: 64 requests per second - Order cancellation: 1024 requests per second - Kill switch: 1 request per 30 seconds - Data retrieval: 256 requests per second - User history (`/fills`, `/orders`, `/transactions`): 32 requests/second burst, 512 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.com/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.com/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.com email: tech@novig.com servers: - url: https://api.novig.com 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/orders/batch: post: tags: - Orders summary: Place order batch description: >- Submit multiple orders (maximum 1024) at once to be processed in a batch. This operation does not make guarantees about the successful execution of all orders, it only places each in the matching engine queue. We book every order or none. We price each order on its own, not the batch total. We refuse the batch when your balance cannot cover its largest order by itself. The batch total may exceed your balance. Each order still needs collateral when it reaches the book, so we can reject an order after we book it. - `201`: we booked every order. - `422`: we booked no order. A balance refusal sets `code` to `INSUFFICIENT_BALANCE`. Its `errors` list each order your balance cannot cover on its own. `index` is the order's position in your request, counting from zero. Your order-volume budget is charged for the orders you send, not for the orders we book. **Rate limit:** 64 requests per second. operationId: placeMultipleOrders parameters: [] requestBody: required: true content: application/json: schema: type: array items: $ref: '#/components/schemas/OrderRequestDto' responses: '201': description: We booked every order. content: application/json: schema: type: array items: $ref: '#/components/schemas/OrderResponseDto' '400': description: Bad request '422': description: >- We booked no order. A balance refusal names each order your balance cannot cover in `errors`. content: application/json: schema: $ref: '#/components/schemas/BatchPlaceError' components: schemas: OrderRequestDto: type: object properties: outcomeId: type: string description: >- The server-generated UUID of the outcome for which the order will increase exposure example: 123e4567-e89b-12d3-a456-426614174000 price: type: number description: >- The price of the order in decimal probability, up to 3 decimal places example: 0.667 qty: type: number description: >- The number of minimal currency units for the order. Note that this must be a positive integer. For CASH orders, 1 unit = 0.01 Novig Cash (e.g., 100 units = 1.00 Cash). For COIN orders, 1 unit = 1 Novig Coin example: 110 currency: type: string description: Denomination of the order, i.e. `CASH` or `COIN` example: CASH tif: type: string description: >- `GTC`, `GTT`, `IOC`, `FOK`, or `PO` (default is `GTC`). `PO` (post only) rejects the order instead of matching it immediately as a taker, so it only ever rests as a maker order. example: GTC ttl: type: number description: >- Time to live for the order (milliseconds) after which the order will be automatically canceled if not totally filled. Required under `GTT` time-in-force; optional under `PO`, where it self-expires if provided and otherwise rests until canceled example: 2400 flags: type: string description: >- Custom 8-character string field for storing trader-specified flags or metadata about the order example: ABC12345 maxLength: 8 required: - outcomeId - price - qty - currency - tif OrderResponseDto: type: object properties: id: type: string description: The unique identifier of the order example: 123e4567-e89b-12d3-a456-426614174002 outcomeId: type: string description: The ID of the outcome associated with this order example: 123e4567-e89b-12d3-a456-426614174000 marketId: type: string description: The ID of the market associated with this order example: 123e4567-e89b-12d3-a456-426614174003 price: type: number description: The limit price at which the order is placed example: 0.125 qty: type: number description: >- The remaining quantity of the order, denominated in Minimum Currency Units example: 4200 originalQty: type: number description: >- The original quantity of the order, denominated in Minimum Currency Units example: 4200 currency: type: string description: The currency in which the order is denominated example: COIN timestamp: type: string description: The timestamp when the order was placed example: '2023-10-05T12:00:00Z' status: type: string description: The current status of the order example: FILLED flags: type: string description: The trader-specified metadata associated with the order example: ABC12345 BatchPlaceError: type: object description: >- The `422` body of a refused batch place. A balance refusal sets `code` and `errors`. properties: message: type: string example: Insufficient balance error: type: string example: Unprocessable Entity statusCode: type: integer example: 422 code: type: string enum: - INSUFFICIENT_BALANCE errors: type: array description: >- Each order your balance cannot cover on its own, in request order. Present on a balance refusal. items: type: object properties: index: type: integer description: The order's position in your request, counting from zero. outcomeId: type: string format: uuid reason: type: string example: Insufficient balance required: - index - outcomeId - reason required: - message - error - statusCode ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.