I tried to do a Google Wallet Integration , I am able to successfully use the createWalletButton API. On clicking the button , I am asked to login to Google Wallets - which is successful as well. But the call to retreive the wallet information fails. The following error is displayed:
Uh-Oh. There was a problem. Sorry, Google Wallet couldn’t complete your request. Please return to the merchant to choose a different payment method, or try again later. Error: 62 (121217125033+0530)
The same error is also seen when trying to call the requestMaskedWallet API. Please advise.
A prompt response will be helpful and much appreciated.
I am getting the error problem in Google Sample App : Instant Buy
Downloaded Sample Instant Buy App
As you are trying to use the Web/JS API for Instant Buy the access to Sandbox for that is to be first requested from Google - http://getinstantbuy.withgoogle.com/ after you are given sandbox access and Merchant ID etc (which you may have seen is required to be in the JWTs), you will be able to use it.
Related
I am trying to use Instagram Basic Display API (V2) to get username and user profile picture of user who logs into application.
I have given necessary permissions to the application for eg. instagram_user_profile & instagram_user_media, I am successfully getting username of the user but i am not getting any API end point which will return me user's profile picture.
following is the link I am referring to for Instagram Basic Display API
https://developers.facebook.com/docs/instagram-basic-display-api
I have tried to query the media node using following GET api listed in the documentation https://graph.instagram.com/{userid}/media?access_token=IGQV....
But in response i am able to get only data of Instagram POST of logged in user.
I'm having the same issue. Instagram Basic Display doesn't provide basic info like user display name and profile picture.
Even the known workarounds, like https://www.instagram.com/USERNAME/?__a=1, are not fully working anymore (think they added some IP filtering, because it works from my machine but if I deploy to an AWS Lambda it doesn't).
The only official way to get the user info that I know is the Instagram Graph API, but it's only for Instagram Business :(
Currently, now I have been working to develop an app in which we have done code for Gmail integration. We are importing all Gmail emails into our database.
Our domain is like mytest and currently, I am testing with mayank#mytest.com which is a Gmail account.
So I am able to integrate mayank#test.com successfully and able to import all 50 mails into the database also.
But when I am trying with mayankprajapati21#gmail.com which is my other id, I am getting error like below.
Authorization Error
Error 403: org_internal
This client is restricted to users within its organization.
I am searching to find a solution for a day but not able to find it.
If any have past experience with Google API, pls let me know how to solve this issue.
Thanks.
My goal is to use the Facebook webhooks to get a notification whenever an IG user mentions my IG account. For that I have followed these steps:
I have created a Facebook page and connected it with an Instagram business account.
I have created a Facebook app (which is now live) and added the product "webhooks".
I have connected my app with my page.
I have created a webhook and subscribed to the mentions event.
I have tested the webhook, using the tools provided by Facebook and it works.
The problem I'm facing is that I can't get my app to work with real data. I have tried to mention my business IG account from my IG personal account, but nothing happens. My callback url is not getting called.
My app doesn't need users to login, so I'm not sure if I need to send my app for review. Do I need a special permission?
I had the same problem. For my case, when I installed the app via graph api explorer, the page token I was using didn't have the instagram_manage_insights permission. So I granted that permission, got a new token, re did the POST request to the {page-id}/subscribed_apps again with the new token and that fixed the problem. Just for the record, I used a system user token from the business manager.
Did you verified your Facebook app via app review? If not, you won't get production data via a webhook callback for the Instagram. I had the same issue and asked the Facebook support and got following response:
However, this is not the same for instagram or pages. This is just how the product teams have decided to implement it. For app review, you can show a mock process of the flow, using either the test webhook or your own process. The app review is less about technical implementation steps, but just a way to make sure that your app is going to use the permission in a way that follows our guidelines, so mocking the procedure should be fine. The reviewers understand that you do not receive webhooks in dev mode and should take this into consideration.
For more information check out following links:
Why is the Instagram Graph API webhook not working
https://developers.facebook.com/support/bugs/495933900986533/
I just figure it out of this problem.
There is a mistake in the official Instagram webhook guide:
With Graph API version 3.2, the /{page-id}/subscribed_apps edge now requires the subscribed_fields parameter, which currently does not support Instagram webhooks fields. To get around this, use your app's dashboard to subscribe.
https://developers.facebook.com/docs/instagram-api/guides/webhooks/#install-app
However, the app's dashboard subscribe is another function. You need your page to subscribe to some field to receive webhooks
Just POST /{your-instagram-connected-page-id}/subscribed_apps?subscribed_fields=feed&access_token={your-instagram-connected-page-token}
Then you will receive webhooks in live mode.
I'm using a javascript code (instafeed.js) to connect to the Instagram API and get the last photos of my Instagram account. The problem is that the thing works for a few days and then the token I got from instagram "expires" or something and it stops working. It throws me Uncaught Error: Error from Instagram: The access_token provided is invalid.
I believe (I might be wrong) it's because I never sent my "app" for review and they are giving me a "sandbox mode" token. Or should I be able to use their API for this simple thing without approval?
Should I send my website for review or is this not an intended use of their API? And if it's not, what should I do?
You should be able to use API in sandbox mode to access your latest 20 posts. You dont need to get reviewed.
Not sure about access_token expiring, in live mode it never expires, so I expect sandbox to be same
I'm getting a 401 error when I try to create a PayPal invoice. I'm using the nodejs REST API:
https://github.com/paypal/rest-api-sdk-nodejs
I did a quick test with the create invoice sample, changing the id and secret in the configure.js to those my app in sandbox. I get the 401 when this happens as well. The app is setup to allow invoice actions (it's in the scope parameter when I request the token), is there something else I need to enable?
I contacted PayPal technical support, they said to contact PayPal MTS. When I contacted them they said to contact technical support... I'm assuming it's something account related as that's the only thing I changed in the sample.
Edit 2014-09-17
I can get a token with curl:
{"scope":"https://uri.paypal.com/services/applications/webhooks https://uri.paypal.com/services/invoicing openid https://api.paypal.com/v1/payments/.* https://api.paypal.com/v1/vault/credit-card/.* https://api.paypal.com/v1/vault/credit-card","access_token":"A015QDaSWWVrhK.FNSZVZd-vDGflSm.g1H.4PnDeXaYDFqo","token_type":"Bearer","app_id":"APP-80W284485P519543T","expires_in":28800}
I'm using the samples from github (configure.js and invoice/create.js specifically) the only thing I changed was the client and secret in configure.
The e-mail in the request was the issue. It worked with the sample because it was the e-mail associated with the app. Changing the config id and secret to mine wasn't enough, the e-mail needed to be changed to mine as well.
Just spent a couple of hours trying to solve this very issue. The answer Dave gave above led me on the right track.
The "merchant e-mail" in the request has to be the Paypal Sandbox Developer Account associated with the REST API app in question. I hope this helps someone.
Below is a screenshot highlighting the property in Visual Studios and PostMan.