@mdnifaz can you please share the snippet of the place order API?

@algo_trader IP needs to be unique per customer. Please check that IP through which the order is being placed is same as that of registered IP.

@algo_trading_50 We were testing with this account for the specific use-case and no other api endpoint was being invoked during the test.

@admin Thanks for looking into it
I checked by putting redirect url in link and it works

@karthik_sunkari unable to see your image.

@admin It works with trading API key. Trading api keys allows history and market data also now

@d321860 you can edit the secondary static IP from the dashboard.

@sejpalsinh As mentioned earlier, create a new static IP from Networking page and attach the IP with your instance of droplet.

@prashant_extreme Outside of market hours, this is very common error.

@admin

Facing similar issue , although this is the first time I am trying to place order via SmartAPI.

Attaching curl request , replaced my sensitive credentials with placeholder values :

curl -X POST "https://apiconnect.angelone.in/rest/secure/angelbroking/order/v1/placeOrder" \ -H "Authorization: Bearer AUTH_TOKEN" \ -H "Content-Type: application/json" \ -H "Accept: application/json" \ -H "X-UserType: USER" \ -H "X-SourceID: WEB" \ -H "X-ClientLocalIP: 127.0.0.1" \ -H "X-ClientPublicIP: PUBLIC_IP" \ -H "X-MACAddress: MAC_ADDRESS" \ -H "X-PrivateKey: PRIVATE_KEY" \ -d '{ "variety": "NORMAL", "tradingsymbol": "BANKNIFTY30MAR2658300CE", "symboltoken": "52534", "transactiontype": "BUY", "exchange": "NFO", "ordertype": "MARKET", "producttype": "CARRYFORWARD", "duration": "DAY", "quantity": "30", "price": "0", "triggerprice": "0", "disclosedquantity": "0", "ordertag": "test-order", "scripconsent": "yes" }'

Getting response as

{"success":false,"data":""}

No idea on what's wrong , no direction on debugging the same

@Renjith New Login - https://smartapi.angelone.in/publisher-login/v2/login/

@sujeetboran It is always recommended to verify the candle interval before saving in database or csv. You can try fetching data in batches and then can verify each batch before saving. In case of missing OHLCV, you can try to re-fetch the complete batch. Verification may add delay in processing but is always worth it.

@akshayrana Use "Publisher" app API key. You might be using "Trading" app API key.

@rithvik Currently OpenAPIScripMaster.json is ~40MB. You can try syncing the instruments from other broker that has smaller file size as backup, in case there is no response from the API. Select the broker whose token are matching with the tokens mentioned the OpenAPIScripMaster.json file.

@mohan-0 Intermittent issue because of service disruption. Try re-creating the API key if issue persists.