Attempting to call google chat API in Postman on the developer's computer, we get the following response.
{
"error": {
"code": 403,
"message": "This API is not accessible for external HTTP caller.",
"status": "PERMISSION_DENIED"
}
}
We have authenticated using OAuth2 (apiKey/secret) with scope https://www.googleapis.com/auth/chat.messages.
We did like to use Postman to try out this API.
Is it possible to get around this error? If so, how?
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 am working on scalr and trying to access scalr api using postman client but I have getting error:
{
"meta": {
"requestId": "63b814f1-f885-48cc-85d6-762e524e0bfb"
},
"errors": [
{
"code": "BadAuthentication",
"message": "Unsigned request"
}
]
}
For scalr api they have given Access keyid:xxxxxxx and secret key: xxxxxxxx so I am using basic auth for authentication process and giving:
username:(scale key id)
password:(scalr secret_key)
Scalr apis working fine with scalr api interface but throwing error with postman client.
Please suggest me what is the problem.
If you are using the API v1 (deprecated) that is currently available in Scalr Open Source, you need to get the signature from your user profile as described in the documentation.
If you are using Scalr Enterprise which supports the current API v2, authentication is described in the API Explorer.
Our organization uses SAML for SSO into Google Apps. In order to use SSO we must manage the change password functionality through APIs. Since the Provisioning API has been deprecated in favor of the Admin SDK Directory API, I am developing against this API.
The flow I am developing is that the end user will login using Google OAuth2 into my application. Then, using the users access token I am attempting to call the https://www.googleapis.com/admin/directory/v1/users/ API to put a new password, but I get an error 403 "Not Authorized to access this resource/api".
My question is, what privilege is required for the user to be able to update their own password? When calling this API with GET I am able to retrieve my user information successfully, but trying to put a new password (or any other field for that matter) fails.
Here is an example of my request and response:
Request:
PUT https://www.googleapis.com/admin/directory/v1/users/user%40domain.org?key={YOUR_API_KEY}
Content-Type: application/json
Authorization: Bearer ya29.AHES6ZT_7onp48edpClD72X-*************************
X-JavaScript-User-Agent: Google APIs Explorer
{
"password": "wlKsf.##2af"
}
Response:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "forbidden",
"message": "Not Authorized to access this resource/api"
}
],
"code": 403,
"message": "Not Authorized to access this resource/api"
}
}
Only super admins, delegated admins and resellers can access the Admin SDK Directory API.
I suggest creating a delegated admin that only has access to update users via the API and then having your web application utilize an OAuth token created for this delegated admin.