I am writing a four square application and after reading the push API, I realized that my users will have to authenticate and add a callback URL and all that good stuff listed below:
"To turn on real-time APIs for your consumer, access your consumer's details page by clicking on its name at https://foursquare.com/oauth. Then click the “Edit this Consumer” button in the upper right of the page.
To change your consumer's real-time API settings, pick the desired state from the drop-down menu on that page titled “Push API notifications.” Then click “Save this Consumer. ” You should now see your new notification settings reflected on the details page for your consumer.
If you have not activated a real-time API in the past, you will note that the Push URL field is blank on the details page. To actually receive real-time pushes from foursquare, you will need to edit your consumer again and add a HTTPS-compliant URL in this field."
Most of my users are not tech savvy to do this. How do I as an application provider automate or pre-poulate some fields in order to make it easy for them to register for the push api for my app?
Thanks!
When you enable the Push Api, you're doing it for all users who authorize your service. You will receive push notifications from all your authorized users... they don't have to explicitly authorize you to use the Push API
Related
Problems:
I am unable to enable Business Messages API, Because "Business Messages API" is not showing API list, While i am going to enable the API through the
https://console.cloud.google.com/apis/dashboard
I want to use auth token, while hitting the API, but the document is saying use the service.json for the credentials. i am following these doc. I am using "Google\Client()" with Laravel application.
https://developers.google.com/business-communications/business-messages/guides/how-to/agents?method=api
I am following these steps:
Login with google business account in the Dashboard
App taking multiple permissions as I have attached the permissions list and taking the auth token.
Open the chat box for the Business.
So please guide me, where i am going wrong. What is correct way to implement this.
Requirement:
I want to create a custom chat box for google businesses, Where business owner will login into the web app and He can easily manage the multiple business chats in one dashboard.
As per your given information, you have to be a partner of Google. As per google documentation, you need to be a partner of google and then you can create the agent and can send and receive messages. You can integrate the business messages API by following this documentation:
https://developers.google.com/business-communications/business-messages/guides
In this process, you need to be a partner of Google. The complete process is given on the link. If you follow this link, then you can use their built-in libraries easily and can send messages easily.
So far the permission for API, it might not be found for you because you might have to take permission for the particular project that is registered on google and then you will see the business messages API and you can enable it and use it. The reason as per the basic step:
https://developers.google.com/my-business/content/basic-setup
Sometimes, you have to submit the request form to take the API access for particular APIs. Or Share how are you using that API.
If you do not find a form for business messages API then you can ask for the information from bm-support#google.com. they mostly respond on a working day.
I am developing an app on Microsoft Teams, and I would like to send a mail with an instance of a logged in user.
This means that a user logs into my Microsoft Teams app, wants to send a custom mail that the app generated, now I want to send a request to my REST API to send this mail as the user.
I could not find any relevant information regarding sending an email like this, I only found methods to send emails with supplying username/password or using the current logged user on the machine (which I can't use since I want to do that using my REST API).
Example of what I found but is irrelevant:
https://www.add-in-express.com/creating-addins-blog/2011/09/02/outlook-create-send-message/
You don't mention if your app is a Tab or a Bot app (or something else), but I'm presuming a Tab. In any case, both Bots and Tab's offer the ability to do SSO sign-in of the user, in which case you can easily get a token for the user. In your backend API, you can exchange this for an "on behalf of" (OBO) token, which lets you access the Microsoft Graph API on the user's behalf. Once that's done, you can call the "send mail" operation on Graph.
To find out more about the above, see:
here for an excellent video overview on SSO with Tabs
here for a blog post on how to exchange the tokens and make the graph call securely
here for the specific operation in Graph (sending email)
My boss is setting up a UK PayPal account for use with REST API for direct credit card payments and payouts.
During this process he's been asked to choose between signature and certificate credentials.
However as far as I understand the REST API uses OAuth 2.0 so what we need is an ID and secret associated to an App.
How should we proceed?
Setting up your credentials for REST is done on the developer site https://developer.paypal.com/. You are correct that the choice between "Signature" and "Certificate" is irrelevant in this case. Try the following:
Go to https://developer.paypal.com and log in using the email address and password of the live PayPal account that will be receiving payments.
Click on “Dashboard” up at the top of the page. You should see a list of your apps here. (If, instead, you see a sentence that says “Create your first app to view it here”, you will need to create at least 1 app)
Click the app name. You’ll see your client ID and Secret for the Sandbox. Toggle your view to “Live” in the upper right corner of the page to see the credentials for the live environment.
You can click on “Account Eligibility” to see what features are available for Live. If the feature isn’t already added there will be an “Enable” link to the right. Clicking on the link will start the request process for that feature.
I would like my server-side code to upload tracks to soundcloud in its own name, then later it will retrieve comments, favourites and listener counts. I do not want to do this on behalf of an app user - for there is no app! Previous questions here on stackoverflow§ (there is no "me too" button) and the API docs seem to suggest I cannot do this. Am I correct?
§ Can track belong to the application and not individual users?
This is called "Authenticating without the SoundCloud Connect Screen" in the API docs:
http://developers.soundcloud.com/docs/api/guide#user-credentials
An "app" in this case is a program that wants to access the Soundcloud API. You register them here:
http://soundcloud.com/you/apps/
Normally you would make a unique username, and register the app to that user. Then, the code logs in as that user to authenticate.
Hi I am working on Rails application. My application is currently in 'invitation only' mode. What I want to do is once user signed up to my application then user should be able to invite his Facebook friends to my application. So what is the best way to do it? I want to do similar like pinterest does. pinterest is also in invitation only mode. But still it allows my facebook friend to whom I have sent an invite to sign up directly. So how I can implement it in my application? Any guidance will be helpful..
Use the requests dialog:
http://developers.facebook.com/docs/reference/dialogs/requests/
Store the list of user id's you get back (which you need to do anyhow
to delete the request programmatically when the come to your app)
When a user tries to login to your app, ensure that they're on your
list of id's you stored earlier.
Delete their app request
See http://developers.facebook.com/docs/reference/dialogs
Deleting Requests When a user is directed to your application, by
clicking a Request from the application, the games dashboard, or from
a Request notification, you must delete the request after it has been
accepted. Requests are not automatically deleted once they have been
clicked, thus it is the developer’s responsibility to clear them once
they have been consumed.