We have problem with our prod pinterest application.
After getting token:
"{"access_token": "AabcYgRUKiaBI45HYM72teXO6fZaFQoEhVxkxaREoN3SR-
A4zAAAAAA", "token_type": "bearer", "scope": ["read_public",
"write_public", "read_private", "write_private", "read_relationships",
"read_write_all"]}"
Then we try get user info https://api.pinterest.com/v1/me
with this token Authorization: Bearer AabcYgRUKiaBI45HYM72teXO6fZaFQoEhVxkxaREoN3SR-A4zAAAAAA
and response
"{"status": "failure", "message": "Authorization failed.", "code": 3,
"data": null}"
Application status is In development now. Could it been changed by pinterest? Our dev app works as expected.
I got a response from Pinterest Help.
Feb 2, 09:32 PST
Thank you for providing all the information here. We're getting reports from multiple developers like yourself with the same issue. I'm going to be investigating further with our team and I'll let you know what we find!
No timeline right now on a fix, but I'll let you know when I get one.
"You're receiving that error response because your app has been denied policy approval."
Now only pinterest partners can use publish api.
Thanks for mentioning it in api doc and notification about changes.
I had the same error and wasted a few days trying to figure out why.
I have 2 accounts, user A and B. A is the dev and B is not a collaborator. I think that's why. The document says only collaborators can use the app without being approved by Pinterest.
The returned error message is useless. If it says so, I wouldn't have to create this ticket and the document is also lacking in my opinion.
Also, if non-collaborator can't be authenticated, the access_token step should fail first.
I know that my answer is weird but I was facing this error too. I just copy pasted the url from the Pinterest docs then added the access token then pasted it to the url search field. The mistake which I made is that there were extra spaces in the URL For example
https://api.pinterest.com/v1/me/pins/?
access_token=<YOUR-ACCESS-TOKEN>
&fields=id,creator,note
&limit=1
When you paste it to the url text field the "next line" (\n) would be replaced with spaces like %20. So you should rewrite your url in one line again in your editor or text file then paste it to the chrome url field.
Your final url should be like
https://api.pinterest.com/v1/me/pins/?access_token=<ACCESS-TOKEN>&fields=id,creator,note&limit=1
Related
I used files from "https://github.com/Omkar0231/Django-Login-API" with as is. The login request from Postman is resulting in error, "detail": "JSON parse error - Expecting value: line 1 column 1 (char 0)", while the terminal shows "Bad request...".
The developer of the source code in above git has also explained it in a video, "https://www.youtube.com/watch?v=6d0fiPj0dsA", however, in video everything seems to be working as expected.
Whatever I understood from Googling, I thought that a bearer token is to be included in the login request as header. But I don't know where to find the bearer token in my Django app. However, in the video, the original author/developer did not include any such header token for the login request from Postman.
Please help me figure out the issue.
I'm following the instructions given on this page:
https://stocktwits.com/developers/docs/authentication
I've managed to get the client id, client secret and the code without any problems (up to step 4). However, when trying to exchange these for an access token, I'm getting a blank page.
The instructions specify that the return is a json format response - maybe there are some browser settings that I need to check to allow this?
thanks in advance for any pointers.
Judging by the title of this post "returning a blank page" it sounds like you are trying to make this request through the browser. The page you referenced says that the request must be a POST request and browsers cannot make POST requests.
On the step you're stuck on (step 5) there is a link that says "View the token call" that links here https://stocktwits.com/developers/docs/api#oauth-token-docs which shows how to make this POST request using curl.
I'm using ruby-trello gem for creating cards in a Trello list.
For my testing credentials this works fine, for the credentials I use on a production setup I get "Trello::Error - Malformed URL:"
The "Malformed URL" is a direct response from Trello, and I can't get my head around why, and how to fix this.
There is little to no documentation on API response errors by Trello.
Maybe you should watch what you application is sending to Trello.
You should also aread the API that Trello offers and search for the specific request and its response. Also you can probe if the Keys are correct in Trello's Sandbox.
As last option write an issue on Github's gem or ask for assistance to Trello.
Hope it helps.
Our API requests have started failing with the error "Request header field yammer-capabilities is not allowed by Access-Control-Allow-Headers".
Before the weekend, everything was working correctly.
Anyone else seeing this?
Same problem here, but it is not the first time, and I think we shouldn't change anything: Yammer's API is slowly beginning to be migrated to Office365's API, maybe this is why there is so much errors in this API... (hope so!)
If you want to see what they're working on :
https://about.yammer.com/success/engage/grow-your-network/release-schedule
Btw, did you try to post this issue on yammer Developer Network ? This can really help, they are using there own social network to communicate ;)
I have a rails4 app, from which I can put a wall post to logged in users facebook wall. Now what I want to do is read the FB comments for that given post and show then in my application.
I'm using Rails 4 and koala gems. Following is my code
Koala::Facebook::API.new(<user.oauth_token>).get_object("<facebook post id>") but I'm keep on getting this error.
{
"error": {
"message": "Unsupported get request. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api",
"type": "GraphMethodException",
"code": 100
}
}
And I cannot see any mismatching in the API, strange thing is I remember I'm using the same code about 3-4 weeks back and If I remember correctly it was working fine that time,
it seems like its not an authentication problem because, If I use
Koala::Facebook::API.new(<user.oauth_token>).get_object("me") it works fine.
You will get the GraphMethodException Unsupported get request. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api when the user access token you specified does not have access to the Facebook object you are requesting. Here is a bug report with more specifics:
https://developers.facebook.com/bugs/1418832665047223/