I have an approved Instagram client (i.e. my app was reviewed an is live) and I wanted to add a new feature to the application. I've heard some applications were getting their clients revoked and I want to know, can I proactively submit my new features for approval before pushing them into production? Does anyone have any experience with this?
I just want to avoid the plug being pulled because my customers pay for my application and use it daily. I'd like to avoid any service interruption. My thought was to email someone on the Instagram API team but, I can't find an email.
What I'm going to do is create a new client and submit a new video with the new features demoed in sandbox, I think this is the best thing to do but I wanted to post here first to find out if anyone has some experience to share that might help me out. Thanks!
Related
Does anybody know, if there is a way to access the transactions made from (Google/Apple)Pay on the device?
I think of a way where the user first needs to grant the access to a specific card on his wallet to the app, before the sync is then started.
I am looking for a way to somehow verificate billings, which are initiated by our app, without handling the payment process itself. So I just want to "observe" it.
Thanks alot for any advice in the correct direction
I've been researching several different API gateway solutions to process payments, or to access bank account records, but that's all not really what the users will feel comfortable with.
I've tried to reach paypal suport so many times, with no success, so maybe you guys can help with this.
The problem: I'm working on a project that have a paypal account setted up, with 5 apps registered there. The paypal account is an old account that receives many recurring payments and we don't have a way to know in witch app the payments are comming, so I was asked to solve the problem trying to create just one paypal app but withou losing any subscription.
The question: How can I delete the apps on paypal dashboard and create a new one without lose any payments?
Thank you so much.
Deleting an app will either cancel the subscriptions, or it won't, but either way you won't be accomplishing your goal of "to know in which app the payments are coming", since nothing you do will move existing subscriptions to a new app, other than having the user cancel and subscribe again.
So, for your stated goal of "to know in which app the payments are coming", the best you can do is settle on which single app to use going forward, and always use that app for new subscriptions. There exists no way to keep old subscriptions active and have them take place in a different app.
And anyway, assuming you leave your apps active, each app can have its own webhook event listeners.
So here is what i am trying to do :
I built a bot with api.ai for my business that is hosted on my webpage and my Facebook page right now. Bot works well.
I want to push it to the next step by allowing my customers to make querys on my calendar, ask to book a specific time, see if available, if not offer other time similar, then make a booking.
I have been reading this thread and the great answer attached to it but i think my case is a bit different.
I was wondering if the bot could always have a token so every guests won't have to Auth to query the calendar ?
Obviously i am new to this, i have been reading the guide of google calendar api and api.ai but i don't really see how to do that yet. I guess there is a way to store a token somewhere and then just trigger the query with some specific intents but not to sure how.
I have also done the node.js quickstart guide of the G-calendar api, and it works fine if that helps.
Thanks for your help !
You will probably want to use a Service Account that is permitted to the calendar in question. Service Accounts are similar to regular accounts, but they are expected to do server-to-server communication only, so the method to create an auth token is a little different to keep it secure.
See https://developers.google.com/identity/protocols/OAuth2ServiceAccount for more information about using Service Accounts.
In general, you'll be using a shared secret to create and sign a JSON Web Token (JWT) you send to Google's servers. You'll get back an access token which you'll then use to call the Calendar API. The access token expires in about an hour, at which point you'll need to repeat the process.
There are libraries available to do much of this for you. For example, if you're using the node.js library https://github.com/google/google-api-nodejs-client, then it will take care of this for you (although you need to modify the key file - see the documentation for details).
I just noticed that new Instagram API's sandbox has too many restrictions and I would need to submit review to build my app. I googled to see if there's a way around but looks like using their API would be better than anything.
The app I was going to build requires all the API endpoints that Instagram doesn't allow Sandbox users to access (such as hashtag search and get recent tags). Do I just build one assuming I can get responses from the endpoints? I am pretty confused. Anything would help. Thanks!
You think you have two options:
Since, instagram allows you get the contents from the user's in the sandbox mode.
Create an App using link and submit for review to get experience with public data available in instagram.
I have created mobile app and used Instagram api for searching users and feeds of users.but They have declined the public_content permission. How can I solve this issue.
You should follow the documentation.
My submission was rejected but it was a valid use case. What should I do?
A common reason for rejecting a submission is that we do not have
enough information to make an assessment of your app. This can happen
if your submission was too short, if it missed important information,
if you did not provide a good screencast, your website is not working,
etc. Before you submit for review again, make sure to provide a long
and clear explanation of what your app does and how you use every
permission. Make sure also to provide a video screencast and to follow
all our Platform Policies.
What should I write in the submission?
The submission should be long enough for us to understand exactly what
your app does and why you need the permissions you are asking for. If
your submission is too short or does not explain all parts of your
integration, then we may not be able to understand and approve your
app. For example, your submission should explain what does your app or
company do, which of the approved use cases your integration falls
into, who will be using your app, how do your user authenticate with
your app, how you use the API to power your integration, how does your
product use the data acquired from Instagram, etc.
What should I show in the video screencast?
The video screencast is a very important part of a submission and
cannot be omitted. Please make sure that the video clearly shows how
your application works, including any Instagram login experience and
the usage of every permission you are requesting. Since your app may
still be in sandbox mode, you can use data from sandbox users to
showcase the integration.