Fetch every order placed today for the account, across all products, exchanges, and states.
Overview
Order Book returns the full list of orders for the logged-in account for the current trading day — Open, Trigger Pending, Complete, Rejected, and Cancelled orders all come back in the same array, differentiated by status. There's no separate "list open orders" call — filter client-side.
This is the endpoint to reconcile against after every Place Order, Modify, or Cancel call whose HTTP response was ambiguous (timeout, network error) — never assume an order's fate from a failed request alone.
Parameters
Field
Type
Required
Description
uid
string
Required
Logged-in user ID. Handled by the SDK if you're using it.
Request example
import requests, json
payload = {"uid": "AB1234"}
data = f"jData={json.dumps(payload)}&jKey={accessToken}"
resp = requests.post("https://api.shoonya.com/NorenWClientAPI/OrderBook", data=data)
orders = resp.json()
open_orders = [o for o in orders if o.get("status") in ("OPEN", "TRIGGER_PENDING")]
print(f"{len(open_orders)} open/trigger-pending orders")
Noren order number — the key to pass to Modify/Cancel/Exit.
status
See Order Status values — OPEN, TRIGGER_PENDING, COMPLETE, REJECTED, CANCELED, PENDING.
fillshares / avgprc
Cumulative filled quantity and average fill price so far — non-zero even for a partial fill on an otherwise OPEN order.
rejreason
Present only when status is REJECTED.
exchordid
Exchange-side order ID, distinct from norenordno.
Every row carries its own statOrder Book returns an array where each element repeats "stat": "Ok" — this reflects each individual record having rendered correctly, not per-order success. A failed order shows up as a normal array element with status: "REJECTED", not as an error.
Poll sparingly — Order Book is a REST snapshot, not a stream. For real-time state, drive your strategy off the Order Update Feed and use this endpoint only for startup reconciliation and periodic sanity checks.
Match on remarks + tsym + qty when reconciling after a timeout, since Shoonya has no client-order-ID field — tag every order with a unique remarks value at send time (see Place Order best practices).
Don't assume array order is chronological or stable — sort by norentm/ordenttm client-side if you need order sequencing.
Notes
Field names shown follow standard NorenOMS conventions used across this documentation — confirm exact casing against your onboarding packet before going to production.
Overview
Order Book returns the full list of orders for the logged-in account for the current trading day —
Open,Trigger Pending,Complete,Rejected, andCancelledorders all come back in the same array, differentiated bystatus. There's no separate "list open orders" call — filter client-side.This is the endpoint to reconcile against after every Place Order, Modify, or Cancel call whose HTTP response was ambiguous (timeout, network error) — never assume an order's fate from a failed request alone.
Parameters
Request example
Response
OPEN,TRIGGER_PENDING,COMPLETE,REJECTED,CANCELED,PENDING.OPENorder.statusisREJECTED.norenordno."stat": "Ok"— this reflects each individual record having rendered correctly, not per-order success. A failed order shows up as a normal array element withstatus: "REJECTED", not as an error.Error handling
Best practices
remarks+tsym+qtywhen reconciling after a timeout, since Shoonya has no client-order-ID field — tag every order with a uniqueremarksvalue at send time (see Place Order best practices).norentm/ordenttmclient-side if you need order sequencing.Notes
Field names shown follow standard NorenOMS conventions used across this documentation — confirm exact casing against your onboarding packet before going to production.