Use this endpoint to migrate users of your application from OAuth 1.0a authentication to OAuth 2.0 authentication to access the v1 and v2 Constant Contact API.
Click a method to view its documentation
This API allows you to, transparent to the end user, migrate your users with OAuth 1.0a authentication to the OAuth 2.0 authentication flow.
This is the work flow you need to follow in planning your migration to OAuth 2.0.
You need to include the following when making a call to the migration endpoint to receive a new OAuth 2.0 access token:
If you are not using an application framework such as Spring and it's related library functions, you will need to generate the following OAuth 1.0a Authentication parameters required to make a POST call to the migration endpoint:
You can migrate users who meet the following criteria:
You need to create a Mashery account if you don't have one, and register your client/application. Go here for details.
No, if your client has a Mashery API key and has only been used with OAuth 1.0a authentication, you do not need to a new API key for OAuth 2.0 authentication.
Yes, you should migrate because OAuth 2.0 authentication is an industry-standard method that is more secure than OAuth 1.0a.
The request payload must be url encoded; set Content-Type to application/x-www-form-urlencoded, and Accept to application/json.
If successfully migrated, we will redirect to the 'Redirect URI' in the DB and append the access_token,token_type and the expiration:
According to the standard Oauth 2.0 flow, you'll find the access_token required for API access in the Location header of the 302 redirect response returned from the POST request to the Migration API.
ResponseHTTP/1.1 302 Moved Temporarily
Date: Thu, 31 Oct 2013 15:37:17 GMT
Set-Cookie: p2_sso_cid=l1-sso2; Path=/; domain=.l1.constantcontact.com; Secure; HttpOnly
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate, no-cache="Set-Cookie"
Keep-Alive: timeout=10, max=100
Set-Cookie: BIGipServerL1_OAUTH2=2556957706.20480.0000; path=/
Any error messages are returned in a JSON formatted array: