There used to be a YouTube api console for v2 that allowed generation of v2 api keys. Mentioned here by Jeff Posnick. I get a 404 error now.
I know that v2 has been deprecated but it takes time to switch to the new v3 version and we should be still be able to use v2 until the end date of April 2015. Does anyone know where to get v2 api keys?
At the bottom of the post you reference, Jeff mentioned that one goal is to make the old v2 API aware of new keys generated via the API console (now the cloud console). I just tested it and it seems to work now to use a "key for browser applications" for deprecated v2 calls as well as the read-only v3 API calls, but someone else may be able to comment if this is, in fact, accurate.
Related
I am trying to add an attachment to a task using Graph API. Previously you can create and list attachments using Outlook Tasks enpoints in Outlook rest API and Graph API beta.
https://learn.microsoft.com/en-us/graph/api/outlooktask-post-attachments?view=graph-rest-beta&tabs=http
However these are going to be deprecated soon and I am unable to find an equivalent feature in Graph Api v1.0.
Anyone knows how to do this in Microsoft To Do API? Thanks in advance
I'm having the same queston. It looks like it is not possible yet with the current 1.0 GraphApi. There is a feature request in Microsoft's techcommunity, feel free to upvote:
https://techcommunity.microsoft.com/t5/microsoft-365-developer-platform/implement-todo-task-attachment-apis-in-microsoft-graph-api/idi-p/3061321
I have Companies I authenticated with against V2. With V3 on the scene, can I safely make V3 API calls with their same tokens? Or do I need to have all of my users re-authenticate themselves?
I would think they are re-usable but during the run-up to V3 I vaguely remember reading/hearing some documentation which suggested otherwise. And I don't want to muck anything up by actually trying it out (it would be bad if Intuit somehow set a flag upon a V3 API call saying "this Company is now V3-enabled, disable V2" or something to that affect).
Yes, the tokens are the same, only the actual REST endpoints changed.
There is no need to get new tokens.
I'm using a twitter API to fetch latest tweets from some person.
It was working well until 16 June 2013.
But now it gives me error - "410 error - rest api v1 not active" while fetching tweets.
Can anyone please help me out to migrate api version 1.1 over 1.0?
or
any other solution
Thanks
I never worked with twitter http api directly. If your twitter codebase is small then you can refactor your code by using a library or implementing some kind of abstraction to make migration to later minor API changes less painful.
As I can see from this article migration seems pretty straightforward. You should always authenticate your requests for all API calls.
API v1 was retired recently, as outlined here. To get up and running again, look at the changes from 1.0 to 1.1 here or here.
I've started to read something about certain Twitter API 1.0 deprecation deadline around march 2013, inviting all their users to migrate onto the 1.1 version of said API. The main difference between the 2 of them (among others) seems to be "the OAUTH thing".
Currently, I've been developing an iOS/Android app, which uses the search.twitter.com/search.json API with no major issues.
The nice thing is that "search.twitter.com" API is an unauthenticated one, and for now, it's more than enough for my needs. I "don't currently want to invest time" onto the OAUTH authentication right now.
On the other hand, and to be honest, I have no idea if the "search.twitter.com" API is the same thing as the 1.0 Twitter API. Is it? Have I been using Twitter API 1.0 without knowing it?
Does anyone know for sure if the search.twitter.com "API" is going to become "also" deprecated on March 2013?
Thanks!!
Finally, it looks like this API will be deprecated.
You can find more information on Twitter developers forum.
https://dev.twitter.com/discussions/12727
https://dev.twitter.com/discussions/14587
https://dev.twitter.com/discussions/14785
So it's time to move 1.1 and OAuth.
The documentation currently does not mention OAuth 2. However, I was hoping the docs are out date, and that someone has gotten OAuth 2 to work with the Document List API. Even the Spreadsheet API supports it, so I'm having wishful thinking.
Turns out that support is in beta. Use scope=https://docs.google.com/feeds/