# Trade\_id versus signalid **URL:** \ **Category:** C2 Software Development\ **Created:** [June 21, 2020, 4:36am UTC](https://forums.collective2.com/t/trade-id-versus-signalid/14167 "2020-06-21T04:36:12Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![EyeForSee](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/eyeforsee/32/13320_2.png) [@EyeForSee](https://forums.collective2.com/u/EyeForSee)\ **Post date:** [June 21, 2020, 4:36am UTC](https://forums.collective2.com/t/trade-id-versus-signalid/14167/1 "2020-06-21T04:36:12Z")
I am using the stoploss with my BTO’s and I wish to monitor my positions - cross-referencing them to my own database of signals. When I submit my signals I capture the signalid locally and later, I use the requestTrades API call to get a history of all trades. The requestTrades API call does not return the original signalid, but does include a trade\_id for each trade. i have noticed - with limited testing - that this value is +1 on the signalid. If this is always the case, I could query the requestTrades JSON for the trade\_id that is related to my order and pull the closed price of the position. Has anyone used this trade\_id = signalid +1 ‘happenstance’, or is it a ‘bad idea’ to assume this applies consistently? ---
**Author:** ![BobSvan2](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/bobsvan2/32/21391_2.png) [@BobSvan2](https://forums.collective2.com/u/BobSvan2)\ **Post date:** [June 22, 2020, 3:25pm UTC](https://forums.collective2.com/t/trade-id-versus-signalid/14167/2 "2020-06-22T15:25:59Z")
Hello, it is a bad idea. 🙂 Re your: > [@EyeForSee](#): > > The requestTrades API call does not return the original signalid, but does include a trade\_id Look at “show\_component\_signals”. It should return signals too: ![image](https://canada1.discourse-cdn.com/flex028/uploads/collective2/original/2X/8/86255feda74eed6da51841e7892c59305e02f0e9.png)