• 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 simonegiuliani · Oct 21, 2019 at 02:21 PM · TT REST API

UAT to PROD - TT REST API switching day

Hi,

we are slightly concerned about the day you will push the changes that are currently on UAT to PROD. We need to be sure that everything will go smoothly as it would be undesirable to lose things :-)

I have two questions for now:
1) Is there a way to be constantly informed about the state of the release? This morning I have noticed that you have moved the date of the release ahead to the 6th of December. Is it possible to have updates on when things are going to happen? Do you have a shared board, or something similar? We need to plan our resources based on your delivery dates and having a shared picture to see what's going on on your side would help us a lot. I actually think it would benefit all dev-teams building things on top of your products.

2) Since this push is going to be disruptive we were wondering how you intend to perform the switch. We were wondering if you considered to deploy on different endpoints to guarantee a smooth experience for the overlapping period. E.g. pre-pending or appending a v2/3/4 to your base url: v2/risk.../user/..

In case there will be no overlapping period we absolutely need to have more info so that we can simulate or be prepared for the migration day. Things such: the exact timing, if there will be an immediate switch etc... We need as many information as possible so that we can plan ahead.

Have a good one

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

4 Replies

· Add your reply
  • Sort: 
avatar image
0
Best Answer

Answer by swatijain · Oct 22, 2019 at 08:30 PM

@simonegiuliani

Be careful because in your email you stated this:
"Second, we will revert the interface breaking changes made to the account and account risk limitPOST endpoints"
For right now, we reverted back the changes that we made to the account and account risk limit POSTS. It's now back to the old way, posting one risk limit at a time.

There are however more breaking changes in the next release. Remember that you have disruptively changed at least another endpoint that you didn't mention in the email but we are currently using: GET risk/{environment}/user/{userId}
You changed the structure of the response of this call, you didn't update the UAT documentation yet, and you also changed the company field names.They used to be: id, abbrevName,name and they are now renamed to: companyId, companyAbbrevName, companyName.
These changes were also reverted. We added more information to the user/{userId} endpoint, but they are not breaking. We updated the response model and it's deployed and documented now. Please let us know if you still see issues with this endpoint.

It may not sound as the end of the world to you but many processes may break (and lose trades) as a result of these undocumented changes. We realised it because we are scraping your exposed UAT endpoints, but this is something you definitely want to communicate in your updates.
We apologize for this. We try to send out a note if there are any breaking changes and it will definitely help if you subscribe to updates as Andrew suggested above.

Please let us know if you have any other questions or concerns.

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 · Oct 22, 2019 at 03:27 PM

@simonegiuliani

1) You can subscribe for release notes by clicking the "Subscribe" button on this page.

2) We've reverted the breaking changes as per the release notes and notice that was sent out. However, be aware that we plan to make the 'requestId' parameter required as of Friday, December 6. This is vital in tracking requests when there are issues.

Regards,
Andrew

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 simonegiuliani · Oct 22, 2019 at 04:24 PM

1) Thanks
2) I appreciate the email you sent yesterday to mitigate the effect of your migration (UPDATED: TT REST API - Breaking Change).

Be careful because in your email you stated this:
"Second, we will revert the interface breaking changes made to the account and account risk limit POST endpoints"

There are however more breaking changes in the next release. Remember that you have disruptively changed at least another endpoint that you didn't mention in the email but we are currently using: GET risk/{environment}/user/{userId}

You changed the structure of the response of this call, you didn't update the UAT documentation yet, and you also changed the company field names.They used to be: id, abbrevName,name and they are now renamed to: companyId, companyAbbrevName, companyName.

It may not sound as the end of the world to you but many processes may break (and lose trades) as a result of these undocumented changes. We realised it because we are scraping your exposed UAT endpoints, but this is something you definitely want to communicate in your updates.

Cheers guys, I appreciate the communication here.

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 simonegiuliani · Oct 23, 2019 at 09:52 AM

I confirm the structure of the response to this call on UAT: GET risk/{environment}/user/{userId} has changed so that it only has additional data and no breaking changes.

Good job, thanks

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