• Ask a question
  • Spaces
    • TT® Platform
    • Autospreader®
    • Autotrader™
    • Charting & Analytics
    • Options
    • ADL®
      • ADL Samples
    • RTD
    • APIs
      • TT .NET SDK
      • TT API & XT API
      • TT REST API
    • Cryptocurrencies
    • Topics
    • Questions
    • Articles
    • Ideas
    • Badges
  • Sign in
  • Home /
  • APIs /
  • TT REST API /
avatar image
0
Question by gbenoit · Jan 18, 2019 at 10:59 AM · TT REST API

TT REST API Risk : /ordertagdefaults?nextPageKey= not working

Hi,

I'm trying to get the full list of OrderTagDefaults but even the endpoint reply contains lastPage=false and a nextPageKey value, when I request the next page I always get the first page. It looks like the nextPageKey parameter is not used/read by the API. Are you aware of that issue and is there a fix soon?

Comment
Add comment
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

6 Replies

· Add your reply
  • Sort: 
avatar image
0

Answer by Zack · Jan 23, 2019 at 03:56 PM

Apologies I initially missed this post. Thank you for bringing this to our attention. I will put in the request for the fix and post an update here with when the fix will be released.

Thanks,
Zack

Comment
Add comment · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image
0

Answer by gbenoit · Jan 24, 2019 at 09:22 AM

Hi @Zack, thanks for your answer. I confirm it's fix on uat as I'm now able to request next pages.

I still have an issue with that endpoint: we try to translate the ordertagdefault.fieldId value using the fields list from /ordertagdefaults/fields but on some ordertagdefaults, the fieldId is missing from the fields list.

For example we have ordertagdefaults with fieldId 263, 264, 331, 373 or 418 and these ids are not in the result from /ordertagdefaults/fields, so we are unable to translate them to human readable format. The fieldId 418 is even worst as this is a ValueEnum one

Thanks for your help

Comment
Add comment · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image
0

Answer by Zack · Jan 24, 2019 at 05:49 PM

Still looking in to these issues. I will let you know what I find.

Comment
Add comment · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image
0

Answer by AndrewR · Jan 26, 2019 at 02:36 AM

A fix has been released. Please let us know if you are having further issues.

Comment
Add comment · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image
0

Answer by gbenoit · Feb 07, 2019 at 07:58 AM

Hi,

the nextPageKey issue was fixed, but now it's back, not taking the nextPageKey parameter so I can request on ly the first page/first 500 items

Comment
Add comment Show 1 · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Zack ♦ · Feb 07, 2019 at 04:17 PM 0
Share

Apologies, looking in to this again and will release a fix again soon. Thank you for bringing this to our attention again.

avatar image
0

Answer by Zack · Feb 07, 2019 at 08:05 PM

@gbenoit

We have fixed this again and ensured that it will not be reverted with the next release again. The fix is currently in UAT and will be in production either or tomorrow with the rest of the release. What environment are you in?

Comment
Add comment · Share
10 |1800 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Your answer

Hint: You can notify a user about this post by typing @username

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Community

Ask questions and share ideas about the TT® and X_TRADER® platforms.

First time here? See our Getting Started Guide and FAQs.

Follow

Follow this Question

Answers Answers and Comments

8 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

TT Rest API 2 Answers

TTREST - No Support -is it ready for Prime Time? 1 Answer

TT Rest API 1 Answer

Fills, which fields are mandatory? i.e. if we wanted to query all fills, do we simply leave them all blank? or do we need to query by account product etc.? 1 Answer

How far back does data available to TT REST API go?,How far back does data go for trade and position histories when using the TT REST API? 2 Answers

Trading Technologies Home - Legal - Privacy - Contact

© 2017 Trading Technologies International, Inc. All rights reserved.

Powered by AnswerHub

  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Post an idea
  • Spaces
  • TT® Platform
  • Autospreader®
  • Autotrader™
  • Charting & Analytics
  • Options
  • ADL®
    • ADL Samples
  • RTD
  • APIs
    • TT .NET SDK
    • TT API & XT API
    • TT REST API
  • Cryptocurrencies
  • Explore
  • Topics
  • Questions
  • Articles
  • Ideas
  • Badges