Infinn API Documentation
Order and Trades

Product Conversion

POST/NorenWClientAPI/ProductConversion

Authorization token is required. Enter your access_token from GenAcsTok above.

"Use proxy" sends this request through this website's server, which never logs request or response bodies. Infinn sees the docs server's IP, not yours. Turn it off to send directly from your browser instead.

jData fields

Values are sent as a JSON string in the jData form field.

Exchange

  • Example: NSE
  • Where to get it: 'exarr' array in the UserDetails response.
  • Allowed: NSE, NFO, BSE, MCX, CDS, NCX, BFO, BCD

Unique id of contract on which order was placed. Can’t be modified, must be the same as that of original order. (use url encoding to avoid special char error for symbols like M&M)

  • Example: RELIANCE-EQ
  • Where to get it: SearchScrip reply, or the TradingSymbol column of the exchange symbol file.

Quantity to be converted.

  • Example: 1
  • Where to get it: Quantity in units (for F&O a multiple of the lot size).

User id of the logged in user.

  • Example: YOUR_USER_ID
  • Where to get it: The ID you log in with at trade.infinn.in (User ID = Client ID). Also returned as uid by GenAcsTok.

Account id

  • Example: YOUR_USER_ID
  • Where to get it: Same as User ID for individual accounts. Returned by GenAcsTok / UserDetails.

Product to which the user wants to convert position.

  • Example: C
  • Allowed: C = Delivery, M = Margin, H = Cover, I = Intraday, B = Bracket, F = MTF, S = Special, P = Special2

Original product of the position.

Transaction type

  • Example: B
  • Allowed: B = buy, S = sell

Converting Day or Carry forward position

For Logging

  • Example: API
  • Allowed: MOB, WEB, TT, API

Authorization Token

Required for all API calls. Use the access_token from the GenAcsTok response as a Bearer token.

⚠ When "Use proxy" is on, this token is sent through this website's server on its way to Infinn. It is never logged here, but if you would rather it never leave your browser, turn off "Use proxy" above or use the ready code with your own client instead.

Request to be POSTed to url : /NorenWClientAPI/ProductConversion

Request Details
Parameter NamePossible valueDescription
jData*Should send json object with fields in below list
Authorization*Bearer <access_token>access_token from GenAcsTok response. Required for all API calls.
Json FieldsPossible valueDescription
exch*ExchangeExchange
tsym*Unique id of contract on which order was placed. Can’t be modified, must be the same as that of original order. (use url encoding to avoid special char error for symbols like M&M)Unique id of contract on which order was placed. Can’t be modified, must be the same as that of original order. (use url encoding to avoid special char error for symbols like M&M)
qty*Quantity to be converted.Quantity to be converted.
uid*User id of the logged in user.User id of the logged in user.
actid*Account idAccount id
prd*Product to which the user wants to convert position.Product to which the user wants to convert position.
prevprd*Original product of the position.Original product of the position.
trantype*Transaction typeTransaction type
postype*Day / CFConverting Day or Carry forward position
ordersource*MOBFor Logging
Response Details

Response data will be in json format with below fields:

Json FieldsPossible valueDescription
statOk or Not_OkPosition conversion success or failure indication.
emsgThis will be present only if Position conversion fails.
Sample Success Response
{
   "request_time":"10:52:12 02-06-2020",
   "stat":"Ok"
}
Sample Failure Response
{
   "stat":"Not_Ok",
   "emsg":"Invalid Input :  Invalid Position Type"
}

</details>
curl --request POST \
  --url 'https://api.infinn.in/NorenWClientAPI/ProductConversion' \
  --header 'Authorization: Bearer PASTE_ACCESS_TOKEN_HERE' \
  --header 'Content-Type: text/plain' \
  --data 'jData={"exch":"NSE","tsym":"RELIANCE-EQ","qty":"1","uid":"YOUR_USER_ID","actid":"YOUR_USER_ID","prd":"C","prevprd":"","trantype":"B","postype":"","ordersource":"API"}'
Response will appear here after sending a request