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
Best Answer
@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.
@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
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.
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
