Constant Contact php api v2 and OAuth 2.0 - oauth

I would like to implement Constant Contact to my Magento extension. If extension is installed in store it should automatically send e-mail to Constant Contact in live (no cron jobs but instantly) when somebody subscribes newsletter.
I never built OAuth 2.0 application. From what I understand OAuth 2.0 requires to redirect user to api url to retrieve token and then redirect back, correct? Does it mean that when in frontend any user subscribes newsletter it will send him to api url and then back? So there is no way to subscribes him without redirect? Or does it mean that the server where website is installed need to retrieve token in background?
Is there any very simple php wrapper for contant contact api v2 that doesn't require autoload and bunch of files? Something like it was for api v1 where there was only 4 files you needed to include.
thank you!

Is there any very simple php wrapper for contant contact api v2
Yes.
that doesn't require autoload and bunch of files
No.
I don't know why you need a small library. You can use official library from constantcontact without a problems https://github.com/constantcontact/php-sdk

Related

generate SLACK_APP_TOKEN for slack application

let's say I've created slack app and I have client id and secret.
What is the easiest way to get SLACK_APP_TOKEN in my hands that will be able to create channel?
If you want a proper access token that is related to your Slack App the only way to get it is to install your Slack app with the OAuth process as described here in the Slack documentation. You will need a mini website with a script (e.g. PHP) to perform the installation.
The so called test token will also allow you use the Slack API (e.g. to create a channel), provided that the user that created the test token has that right on your Slack. It is the easiest to obtain, but it will always be linked to a user account, not a Slack app. And you can not request specific scopes for it. So for most applications its better to use a Slack App and get a proper access token by installing it.
If you are looking for an example for an installer script, here is a complete script in PHP. It will run on any webserver that supports PHP. Its very basic, but it will work just fine.

Stripe Create User Function in Swift

I was just wondering if there was a simple function to create a customer in the Stripe API from my app in Swift? Instead of having to create a manual HTTP post request to my server, "createCustomer.php", and then retrieve the results (This is what I do right now).
I tried to search this up on Google, but I can't seem to find anything. I simply want the user to save their card details for later user, that's why I am in need of creating a customer.
Thanks in advance!
Except for payment information tokenization (which is done via Stripe's iOS or Android SDKs in mobile apps, and Checkout or Stripe.js in web apps), all API requests must be sent from a backend server.
The reason is that aside from token creation, all other API requests must be sent using your secret API key. You cannot embed or share the secret API key with your mobile app in any way, as it would then be possible for an attacker to retrieve it and use it to issue API requests on your behalf.
This is why there is no Swift function to create a customer -- the customer creation must be done from your backend, using the server-side language of your choice.

Retrieve my adsense report as server application

All I need is like so,
I want to use Ruby and Google API to retrieve MY adsense report (like page views, CTR ...) and save it into my database. (I want it to be automatic)
When an user requests to my page, I will show my saved report to him.
I think it was simple but it's not actually because OAuth 2.0 needs users to authenticate with google. I dont know how I can do it because I dont have any browsers on my server. Is it possible to do so? Can anyone show me how to do it?
The AdSense Management API can be used with the "Installed application" OAuth2 scenario. You just need to generate the refresh token once (you don't need browsers on your server and no human interaction is needed after this).
Here's the generic guide:
https://developers.google.com/adsense/management/getting_started#auth
And the Ruby client library, with the adsense sample:
https://github.com/google/google-api-ruby-client-samples/tree/master/adsense
The client library handles auth for you.

Twitter Application using php?

I need to develope a Twitter application in php,
Requirements are that that my application should get access token from user and then using that access token, my application should be able to get backup of the twitter user tweets, followers list, timeline, messages etc.
I created an application on twitter and got the consumer key and secret.
Please tell me how i start now, and what is the best php library that will be enough for my requirements.
Thanks
The best place to start is http://dev.twitter.com
If you want to really jump into things, check out the listing of PHP libraries that you can use: http://dev.twitter.com/pages/libraries#php
Edit: I also suggest you read everything under Guidelines and Terms, Authentication, and REST API & General on this page: http://dev.twitter.com/doc

Customising Tweets

I have some PHP creating automatic Twitter updates, which in the small print at the bottom reads "[date/n minutes ago] via API".
Is it possible to somehow change the "via API" part to something more useful and descriptive?
It looks like you have to utilize OAuth authentication. As per the Twitter API Wiki:
How do I get “from [MyApp]” appended to updates sent from my API application?
We now recommend developers use OAuth to perform authentication with the API. When applications use OAuth, Twitter automatically knows the source of status updates. We are therefore able to append source attribution (from "[MyApp]") to tweets. If you would like tweets from your application to recieve a source parameter, please register an application and implement OAuth authentication. We will automatically include your application as the source for any tweets sent from your application.
We originally allowed applications to create a source paramter for non-OAuth use but that has been discontinued. Applications pre-OAuth source parameters will remain active, but new registrations are no longer accepted.

Resources