Hi, I was moving all the account stuff related to v4, when I noticed that the old Get /account has not been yet migrated. Is there any way to call successfully Get 3/account providing the v4 accesssToken instead of session_id? I guess no, but still.. Is the migration of GET /account happening anytime soon?
Would it eventually be possible, to include a valid v3 session_id as part of the response of v4 auth/access_token? I tried to rate a movie with the v4 AccessToken but it failed with 401. I am still able to retrieve favorites and watchlists
Please advise, Cheers
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by Travis Bell
on January 29, 2017 at 11:36 AM
Hi @blackbelt
Yes, there will definitely be a v4 account details request call, I just haven't added it yet. I'll try to find time to look at this in the near future.
I have some outstanding work to create either a v3 session migration process, or, simply allow the Authentication header to authenticate some v3 calls. I haven't decided which way I'm leaning on this quite yet.
I'll let you know once this has been looked at.
Reply by Ema
on January 29, 2017 at 11:43 AM
@travisbell thanks. How long do you think, will it take to have both v3 and v4 working? Cheers
Reply by Travis Bell
on January 29, 2017 at 11:58 AM
I'll try to get to this end of week-ish. I just have to wrap up some stuff I'm in the middle of.
Reply by Ema
on January 29, 2017 at 11:59 AM
nice! Looking forward then. Keep up the good work Cheers
Reply by Ema
on January 29, 2017 at 1:01 PM
I just noticed that the fild public of 4/list is marked as boolean in the documentation, but the endpoint expects/returns an int Cheers
Reply by vankasteelj
on January 29, 2017 at 2:21 PM
will the v4 eventually support all calls? maintaining both v3 & v4 side-by-side is a nightmare.
Reply by Ema
on February 1, 2017 at 11:34 AM
@vankasteelj I guess that's the intent, but, of course, it will take time, so for some time we will have to maintain both, side by side, migrating the endpoints when new v4 are added. @travisbell Any update on the AccessToken/session_id situation?
Thanks
Reply by Travis Bell
on February 1, 2017 at 11:40 AM
Eventually, sure. But I am only working on the stuff that really needs it right now, and accounts and lists were the top of that batch.
None yet. I'm hoping to find some time this week still.
Reply by TheLittleNaruto
on February 10, 2017 at 6:35 AM
Hey Travis,
Any update on migration of GET/account?
Thanks
Reply by Ema
on February 15, 2017 at 1:51 PM
@travisbell any update on this ?
Reply by Travis Bell
on February 15, 2017 at 2:52 PM
Unfortunately, no. All of this IMDb stuff has taken 100% of my attention. I'm planning to get back to my normal scheduled programming next week.
Reply by Ema
on February 25, 2017 at 5:24 AM
@travisbell any update on this ? is there a way to follow the progress of this task ? cheers
Reply by Ema
on March 10, 2017 at 7:17 AM
@travisbell sorry to bother you again with this . Any progress on the AccessToken/session_id situation? Thanks
Reply by Travis Bell
on March 10, 2017 at 10:10 AM
Soon now, I'm just wrapping up the new account pages which had me look at some of this so it will be complete on the API side soon. I have an open ticket for this here.
Reply by Travis Bell
on July 24, 2018 at 12:41 PM
There's now a method to convert a v4 access token to a v3 session id. You can read more about this here.