Current API Functionaliy

đź’ˇ Feature suggestions & ideas
1

I am programming a personal desktop to use with my T212 accounts. I have tested much of the available functionality, and with the current API (at 26 Jan 2026) I can confirm the following is working well:

With A DEMO Account, INVEST Account and ISA account I am able to do the following
(you need a different password and secret key for each account)

  1. Display account details (Value, invested, free, P/L, % )
  2. Display a continuously updatable list of all my portfolio holdings (Ticker Qty Avg.Paid Curr.Price Tot.Cost Value P/L %)
  3. Display a list of pending orders with details, overall and per equity
  4. Display a list of historic orders (per equity) ( not yet succeeded in reading more than 50 transactions per equity by paging).
  5. Buy and Sell stocks at market and set up pending orders using limit prices. (only working in demo account)
  6. Cancel pending orders (only working in demo account)

Except for items 5 and 6 above, this functionality works well with all 3 account types - demo, invest and Isa. I don’t have a CFD account.

Wish List

Historic paging needs fixing, I haven’t tried it for a while so maybe it is fixed!
Buying and selling needs to be fully enabled with limit prices and cancellation for invest and Isa accounts.
It ought to be possible to retrieve a quote for any equity the T212 handles, currently you can only get this for portfolio holdings, which means relying on other sources for current prices of stocks you don’t currently hold.
Better messaging. When a call fails there should be a useful response returned. The response should be useful for non technical users not just programmers.
Better API documentation.
Better interaction between T212 programmers with API users like me. The users are the test bed and should be encouraged.

All in all this is becoming an excellent API and is far simpler to get working than many API’s I’ve encountered in the past!

I’m using a combination of javascript and php.

2 Likes
2

I trust your experience is better than mine. I programmed the whole building of my own database only for T212 to make wholesale changes in November to the data delivered by the endpoints.

I also trust you don’t find bugs in the data, as I have. Dealing with T212 on bugs is truly a nightmare.

3

That’s sadly negative. Is there any way of dealing with T212. The API doesn’t even have it’s own category here. Have you found any other chat groups on this API. I’ve pretty much done this in isolation. It would be nice to chat with their engineers and get replies!