Pinterest API v3 OAuth is it still working? - api

Is Pinterest API still supported or they dropped the majority of the endpoints ?
The documentation from https://developers.pinterest.com/ lacks any information of OAuth authentication.
I've already checked the old versions of the API so please don't mark the question as duplicate:
How to Get OAuth Access Token for Pinterest?
pinterest api documentation
Many of the endpoints from v2 were removed in v3 and v2 now returns 404.
There's no way to actually generate access token and the trick with iPhone app access token doesn't seem to work anymore.
The tasks I'm looking to accomplish with their API:
authenticate users with OAuth
upload pics on their boards based on access token
Thanks

use below link
https://www.pinterest.com/oauth/?consumer_id=1431594&response_type=token
and see
pinterest api documentation

Here is a link to the new V3 documentation: https://developers.pinterest.com/docs/redoc/pinner_app
Assuming your app has been approved, the "User Authorization" section (https://developers.pinterest.com/docs/redoc/pinner_app/#section/User-Authorization) provides details on how to authenticate.

Related

When using google's auth2 api, is it possible to submit a nonce or state

I'm using Google Sign-in for websites api and would like to submit a nonce and have it returned in the signed JWT id_token (in the JTI field).
The google identity platform mentions both a nonce and a state field, but none of these appear to work with with the auth2 api. What is the correct way to send and receive this value using auth2?
As per discussion from the comments, I see you are trying to mix raw OAuth protocol and Google Sign-In library.
While things mentioned in this page such as nonce or state are part of OAuth protocol, Google Sign-In is a JavaScript library that simplifies things down.
With Google Sign-In, you can let users sign in only with JavaScript. If you want to integrate with the server, send id_token you can obtain from JS API to the server. Further information can be found in the following resources.
Google Sign-In for Websites:
docs: https://developers.google.com/identity/sign-in/web/
videos: https://www.youtube.com/playlist?list=PLNYkxOF6rcIBQCKXOfi4AUtSpMj78pX5f
sample code: https://github.com/GoogleChrome/google-sign-in

Google get email proper scopes

A lot of the documentation on google talks about the email scope to replace the https://www.googleapis.com/auth/userinfo.email, pared with the endpoint https://www.googleapis.com/userinfo/v2/me. Documentation found here https://developers.google.com/+/api/oauth#email.
Yet there is more documentation that states even that is being replaced in favor of the plus api and endpoint and the people.get endpoint. Documentation found here https://developers.google.com/+/api/auth-migration#email.
I have an application that needs to request the user email for both authentication and to verify they have installed our app.. A bonus is when I try to add the email scope to the developer console, or use it in my app, it tells me that email is not a valid scope.
My question is what are the proper scopes that need be applied in my app and in the google developer console? Need to be sure of this since the Google Apps Marketplace V2 has rules about prompting users.
You need to use the "email+profile" scope. That's the only way you will comply with the marketplace requirements to hide the user consent window.
Don't worry about the API console saying this is not a valid scope, it works when you provide it to the OAuth endpoint.
Here's an explanatory blog post with a sample in Java and all the required configuration steps.

Sign In With Twitter

Looking at this site http://www.thefancy.com/ and clicking the Sign up button followed by the Twitter option it brings up a window for Twitter Login.
I assume this is the JS approach to Twitter login in a similar fashion to Facebooks.
On my site I have already implemented Connect With Facebook (using JS) and to keep my site consistent I would like to know how to do this using Twitter's Sign On service.
Does anyone have any useful advice or links to help me with this - I can only find guides that take the user to Twitter's website during login and then back again to mine which is not what I want.
Many thanks
EDIT:
I did notice this on Twitter's site:
"Reminder: It is strongly discouraged to use OAuth 1.0A with client-side Javascript."
Why do Twitter recommend against using JS with OAuth while Facebook and Google are happy to go with it?
tHave you looked into Twitter OAuth? In order for Twitter to grand your site details, it has to redirect your users momentarily to twitter for them to verify this access. This link explains it a bit better: https://developer.twitter.com/en/docs/basics/authentication/overview/3-legged-oauth
Temboo simplifies the process of developing Twitter sign up (via OAuth). See here for details: https://live.temboo.com/library/Library/Twitter/OAuth/
Temboo doesn't have a JS library though, so you will have to use the REST API.
Full disclosure: I work at Temboo.

iOS 5 Twitter framework. Getting OAuth access token for user

Has anyone been able to get the OAuth access token for a user after being granted access to that users account?
twitter mentions using a process called "Reverse Auth" in there iOS docs, but I can't seem to find any mention of it anywhere else.
I'm feeling a little lost here so if any one can provide some inside it would be much appreciated.
More information on using Reverse Auth has been released by Twitter here.

Does Facebook API video-upload work only with OAuth v1?

I cannot get video upload to work with OAuth 2 access-token. The request always fails to even connect (timeout).
http://developers.facebook.com/docs/reference/rest/video.upload
With almost identical code, I have successfully uploaded photos.
The only video-upload example code I can find uses OAuth 1.x. Does video not yet support OAuth 2?
Thanks to all who read this.
AFAIK this is the case. New graph api still missing some of the functionality from old REST api. And that includes uploading video. You should be able to use REST api with access token to do things not yet supported by graph api.