I have followed the steps of this guide : https://developers.google.com/identity/protocols/risc. My goal is to receive tokens-revoked events and this is working ! When I go to my google account and remove my app then my "receiver endpoint" is triggered by the event.
1 - My first issue is kind of the same as described here : what-is-the-payload-for-the-google-risc-api-callback. I can't find any trace of the JWT token. The body of the received request in an empty object and there is no Authorization header. So where can I find the JWT ?
2 - I'm trying to trigger the event using the https://risc.googleapis.com/v1beta/stream:verify endpoint but this error is returned :
{
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}
(I'm using the same token to make call on https://risc.googleapis.com/v1beta/stream/status, https://risc.googleapis.com/v1beta/stream:update and everything is working ...)
Related
I want to use the Speech-to-text API for an application made in nocode.
I get this error message:
There was a problem setting up your call.
Raw response for API
401 status code
{
"Mistake": {
"code": 401,
"message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie, or other valid authentication credentials. See https://developers.google.com/identity/sign- in/web/devconsole-project.",
"status": "NOT AUTHENTICATED"
Thanks in advance
I may be able to transcribe an audio file to text.
Is it possible to delete the message in the response?
{
"message": "PERMISSION_DENIED: The API targeted by this request is invalid for the given API key.",
"code": 403
}
I prefer not to expose information to users. In this particular case a 403 http error would be enough.
I'm testing OAuth 2.0 with facebook API, after receiving the authorization code and requesting the access token with the GET https://graph.facebook.com/v3.3/oauth/access_token? i got this response :
{
"error": {
"message": "Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request",
"type": "OAuthException",
"code": 100,
"fbtrace_id": "Dl3lYjJLKKy"
}
}
the redirect_uri is the same as the one in the login dialog since i'm just testing on localhost.
Everything was working fine till today,i even tested new callback url using localtunnel but it didn't work at all
I'm trying to receive realtime updates of user threads via graph api(2.x), and I work around with Graph API Explore posting a request like below to make a subscription;
https://graph.facebook.com/v2.1/MY_FB_ID/subscriptions
# with these params
access_token: MY_VALID_ACCESS_TOKEN
object: user
fields: threads
verify_token: foo-bar
callback_url: http://example.com/callbacks
then I get this error:
{
"error": {
"message": "(#100) Application cannot subscribe to notifications",
"type": "OAuthException",
"code": 100
}
}
And when I change threads with name, for example, it returns this response.
{
"error": {
"message": "(#2201) response does not match challenge, expected value = '1872122487', received='<!doctype html>\n<htm...'",
"type": "OAuthException",
"code": 2201
}
}
I think this error is good because Facebook API accepts a request and try to verify the server to send notifications exists and setup correctly, but the first one is not good apparently.
So what's odd is both threads and name are listed as valid fields for user object on the document, but only threads is not accepted.
https://developers.facebook.com/docs/graph-api/real-time-updates/v2.0#subscribefields
Any idea about what is wrong with this. I should not do this on explore? Or it's not even possible to subscribe user threads via graph api?
Thanks in advance.
I found we cannot receive realtime updates of user/threads unless being whitelisted by facebook, at least for now.
I'm using the Facebook Graph API to reply a direct message.
I have published my message issuing an HTTP POST request to /CONVERSATION_ID/messages with a valid access token.
But I receive the following error:
{
"error": {
"message": "(#3) Unknown method",
"type": "OAuthException",
"code": 3
}
}
The same test on the Graph API Explorer returned the same error.
Can anyone please help me out?
My Workplace (Facebook for business) GRAPH API application received a "(#3) Unknown method" error when it didn't have POST or DELETE permissions for the action it was attempting. Changing the integration/application permissions resolved the problem for me.
You don't need to add /messages to the API. Just call the API as https://graph.facebook.com/{message_id} to get the thread.