Google Oauh2 Verification Invalid Argument - google-apps

I'm trying to submit an application for a verification through the Google Console as it has opened from today.
I have verified the domain in question through Goofle Search Console, I have ensured that all the links are set(Policy, Terms of Usage etc), filled the form with information and explanation about the scopes rhat requires verification.
When I submit the form I get no response that it's submited but the response from Network in Developer tools I see it's 400 HTTP Status and I see the following error message:
{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT"
}
}
I have double checked my steps but still not able to resolve this, any information that you can provide would be great.
Adding Request:
https://clientauthconfig.clients6.google.com/v1/brands/ID/submitReview?alt=json&key=AIzaSysnipsnip0DjtiCwWBwQ1djDy741g
Above request is PUT, here is the body content
{"brandId":"ID","scopeRationale":"","additionalInfo":"","contactEmail":"contactmeialaddress#gmail.com","pendingScopes":["https://mail.google.com/","https://www.googleapis.com/auth/gmail.modify","https://www.googleapis.com/auth/gmail.compose","https://www.googleapis.com/auth/gmail.insert","https://www.googleapis.com/auth/gmail.readonly","https://www.googleapis.com/auth/contacts.readonly"],"category":[1,3,5],"scopeDetails":[{"apiGroup":1,"pendingScopes":["https://mail.google.com/","https://www.googleapis.com/auth/gmail.modify","https://www.googleapis.com/auth/gmail.compose","https://www.googleapis.com/auth/gmail.insert","https://www.googleapis.com/auth/gmail.readonly"],"scopeRationale":"Why we need access to this scope."},{"apiGroup":2,"pendingScopes":["https://www.googleapis.com/auth/contacts.readonly"],"scopeRationale":"Additional info why we need this."}]}

Related

Facebook API error subcode 33

I have an app that gets leads from facebook after webhook request when leads fill out forms: Some pages are throwing this error:
{
"error": {
"message": "Unsupported get request. Object with ID '233332620530416' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api",
"type": "GraphMethodException",
"code": 100,
"error_subcode": 33,
"fbtrace_id": "HIItB4mggfk"
},
"__debug__": {}
}
I cannot find the error subcode description in Facebooks API docs.
Check you access token at https://developers.facebook.com/tools/debug/accesstoken
Your app might be missing a needed permission scope.
Visit Business Settings > Users > System Users > Chose «Conversions API System User» > Add Assets. Add your Pixel with ID from your request to the list of assets System User can access.
I have had this issue a few times and the error led me to spend an hour or two combing the docs. The real issue for me each time has been malformed json in the request body (I'm using curl). Dumb I know, but in case a poor soul comes across this. Be sure to validate your json before you decide you query is wrong.
I got this error when adding access_token in post body, worked when adding parameters to url.
Success result using postman
Not success result using postman
Add your access token in the Authorization tab, then choose Oauth2.0 and add your access token on the right side. Please refer to the screenshot for the postman.Click here for the screenshot
I found the answer recently
Follow this steps using postman
https://graph.facebook.com/page-name/feed
headers:
Content-Type: application/x-www-form-urlencoded
Body:
message: "your message"
link:"your web link "
access_token:'Your access token '

Simple REST GET request to youtube API return error

I'm quite new to working with REST API of various services.
I'm trying to search for videos in youtube.
In GCP I enabled Youtube Data API, generated key and set Referrer Restriction.
In Postman (or in browser - same result) I call GET method with the URL (got from API explorer)
https://content.googleapis.com/youtube/v3/search?part=snippet&q=angular&key=MY_API_KEY
and add Referrer field with correct value into the header.
This is the answer from the service:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "ipRefererBlocked",
"message": "The referrer ReferreValue does not match the referrer restrictions configured on your API key. Please use the API Console to update your key restrictions.",
"extendedHelp": "https://console.developers.google.com/apis/credentials?project=589726014278"
}
],
"code": 403,
"message": "The referrer ReferreValue does not match the referrer restrictions configured on your API key. Please use the API Console to update your key restrictions."
}
}
Problems:
1. My project id is not 589726014278;
2. Referrer value is OK, of course not against unknown project id.
Question:
How can I make it work? I want to keep it so simple as possible; w/o OAuth anything. Is it possible?
Try to recreate your Youtube api key and set the refer value to null based on the answer from this discussion.
http://valvepress.com/how-to-get-a-youtube-api-key-to-post-from-youtube-to-wordpress/

Payments REST API generating invalid redirect urls

Yesterday we were able to create payments and get redirect urls that could be used to approve payments. However today the redirect urls that get returned all result in pages with the message "At this time, we are unable to process your request. Please return to and try another option."
We are also unable to GET previous payments that have not been approved/refunded. Instead we get
{
"name": "INVALID_RESOURCE_ID",
"message": "The requested resource ID was not found",
"information_link": "https://developer.paypal.com/docs/api/#INVALID_RESOURCE_ID",
"debug_id": "ade89339d6e00"
}
Additional debug ids include: d07f86c738cea,5c6da3bb0b6a.
There are allready several posts about this. All you can do is to wait until this issues is fixed by paypal. Fixing the url by yourself wont fix the problem.

Facebook Connect error code 191

I've looked and tried so many things but unfortunately I have been unsuccessful in fixing the Facebook Connect on my forum (IP.Board 3.4). It worked before but for some unknown reason stopped working. Now I get an error (code 191)... I'm pretty sure I've got everything set up properly. I was hoping the Stack Overflow community could help me out. Here is the full error message being displayed when someone tries to register using FB:
{
"error": {
"message": "Can't Load URL: The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.",
"type": "OAuthException",
"code": 191,
"fbtrace_id": "G9FSrFXlu0Y"
}
}
Screen 1
Screen 2
Thank you for your time and help!
For login via the website platform, you need to add an according Valid OAuth Redirect URI. (Because in that case, the address will not be apps.facebook.com/something)
The Valid OAuth Redirect URIs field must contain the exact value of the redirect_uri parameter in your login dialog call.

getting error 400 in device oauth flow

When making an http post:
https://graph.facebook.com/oauth/device?type=device_code&client_id=myclientid
I'm getting an http 400 error. Am I doing something wrong here? Is device_code supposed be something other than device_code? It doesn't look that way here:
https://developers.facebook.com/docs/authentication/devices/
I'm just starting to experment with browserless facebook auth.
Well, clicking https://graph.facebook.com/oauth/device?type=device_code&client_id=myclientid gets you a pretty clear error message:
{
"error": {
"message": "Unsupported type: 'device_code'. Supported types: web_server, user_agent, client_cred, username",
"type": "OAuthException",
"code": 1
}
}
The linked specification though says:
type
REQUIRED. The parameter value MUST be set to "device_code".
As Facebook is stating:
Both the specification and our implementation are constantly being refined, however, so some subtle differences should be expected.
that could be some temporary glitch between implementation and documentation.
Anyway, are you sure you already would have access to device authentication?
Please note that we are currently testing Device Authentication with a limited number of partners. It is not currently available for general use, and we are not accepting additional applications for access.
If you use the following URL(only the appId is changed) you will get result. It will return a code, id, verification URI etc. The fact is that the device flow api will work only for the above appId and which is provided by facebook. No other AppIds wont work. Everything will return an error like this
{
"error": {
"message": "Unsupported type: 'device_code'. Supported types: web_server, user_agent, client_cred, username",
"type": "OAuthException",
"code": 1
}
}