About Courtney_E

Hello LBobA54,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API. I apologize for the delay in our reply.   You can can modify your V3 API key’s Refresh Token settings with the following steps:   Login to the “My Applications” page of the Developer Portal at https://app.constantcontact.com/pages/dma/portal/ Click on the title of the key you wish to modify the settings for Click the “OAuth2” tab of the key’s settings Under the “Application OAuth2 Settings” section, you’ll see an option for Rotating or Long Lived Refresh Tokens.    Please have a look and let us know if you have any other questions!   Regards, ... View more

Thank you Courtney for checking on this 👍  Very relieved to hear this account will not expire. ... View more

Hello emcins,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   You should be able to fully automate your integration with the exception of the initial Authorization Request screen and redirect, which can only be accessed/authorized via a browser window and cannot be bypassed, but you should only need to authorize the connected Constant Contact account once.   The Authorization Request screen is only for connecting a Constant Contact account to the integration, so for example if you are making a sign-up form or integration that only connects to one Constant Contact account, only you would access the Authorization Request screen one initial time to connect your account, it wouldn't be visible to people using the form/integration.  When your users or program are accessing the integration, it will use the token set generated when you initially granted permission to access the connection. The only time other people would access the Authorization Request screen is if you are designing an integration that needs to connect to other Constant Contact accounts, as each account needs to physically grant permission to the integration via a browser window.   Constant Contact provides developers with free access to our V3 API endpoints for developers building their own application for integration. You can get started using our API by visiting our documentation here: https://v3.developer.constantcontact.com/api_guide/getting_started.html   Additionally, you can utilize our API Reference Page to find body schemas & values, as well as test the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   While Constant Contact doesn’t offer any services as far as assistance with building custom integrations, and our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Hello LauraG70,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Our current V3 API uses OAuth2.0, which is the current industry-standard for authorization. It’s more secure than previous versions and does a much better job of keeping your Constant Contact account data safe. When you give their integration permission to access your account, it will show you exactly which permissions the integration is requesting to be granted (rather than just granting all permissions). V3 also uses tokens that are continuously refreshed to keep the connection encrypted and secure.   The request for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   In the meantime, here are the example calls that are currently available for V3:   V3 Code Samples: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.html   Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   For additional reference, here is the link to a sample that was created/shared on our Developer Forum by a 3rd party developer (NOT created or supported by Constant Contact) for V3 using PHP: https://community.constantcontact.com/t5/Developer-Support-ask-questions/PHP-V3-Library-now-updated-to-new-OAuth2-endpoints-and-PKCE/td-p/383773 ... View more

Hello Justin,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   This type of issue wouldn't be related to the version of the API, but rather the types of calls being used to manage the contacts, as there are several different ways to manage contacts via API.  Additionally, if more than one integration is connected with an account, they can sometimes work in conflicting ways for the same reason.   If you'd like us to take a look at the account for you, feel free to reach out to our team directly/securely via email at webservices@constantcontact.com and provide the Constant Contact username, integration name, and some examples of lists/contacts that are being affected so that we can better assist you.   As a side note: While no date is currently set, there will be a point in the near future where our legacy V2 API will begin deprecation. Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints, and strongly recommend upgrading to the V3 API to ensure you're ahead of the curve.   Please have a look and let us know if you have any other questions! ... View more

Hello HopeandCope,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Account credentials will always be needed at some point to connect the integration and grant access to the account.   In a case like yours, where someone else is setting up the integration, there are typically ways to bypass giving credentials to the 3rd party by just having you connect and grant access instead of them.   The process will depend on whether they are building/coding the form themselves, using a 3rd party integration/plugin, and also what version of the API is being used.   If you are able to gather a few more details (such as the name of the integration/plugin if it is 3rd party, who your website host is, whether they are building the form themselves, etc), we'd be happy to see if we can provide more insight.   You can reach our team directly/securely via email at webservices@constantcontact.com to follow up.   Please have a look and let us know if you have any other questions!   ... View more

I found this post that helped me to generate refresh token. https://community.constantcontact.com/t5/API-Developer-Support/Device-Flow-Refresh-Token/m-p/404332#M14074 ... View more

Hello DanielleF2369,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The error "Error getting campaign activity by activityId __: undefined" being received within the website UI is not related to Constant Contact's API.   I apologize for any inconvenience that this error has caused, and  have opened up a case with one of Constant Contact's Tier 2 customer support specialists so that they can follow up with you directly to verify whether you are still experiencing issues related to this error.   One of our Tier 2 support specialists should be in touch within 4 business days. Otherwise, for immediate assistance, or if you’d like a callback/email from them at a certain day/time you can call our support line at 866-289-2101 and reference case # 32012755.   Please have a look and let us know if you have any other questions! ... View more

Hello KCSC,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   There are multiple ways to retrieve the URLs for sent campaigns. You can do this both via the V3 API as well as via the website UI.   To retrieve this data via the API:   After completing authorization, you'd first want to make a GET call to retrieve a list of email campaigns: GET a Collection of Email Campaigns https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignsUsingGET   In the results, emails that are marked with the "current_status" of "Done" will be emails that have been sent. You will want to save the "campaign_id" for those sent emails. The "updated_at" time should reflect when the email was last sent.   You will then make a GET call for each "campaign_id" to retrieve the details for each of those sent campaigns.   GET Details About a Single Email Campaign https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignUsingGET   From the responses of these calls, you will see a "campaign_activity_id" that corresponds with a "role". You will want to save the "campaign_activity_id" for "role": "permalink".    Next you can use the  "campaign_activity_id" to get the "permalink_url" for that campaign.   GET a Single Email Campaign Activity https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignActivityUsingGET Alternately, to get the URLs via the website UI, here are the instructions:   The permanent URL for a campaign https://knowledgebase.constantcontact.com/articles/KnowledgeBase/6128-email-campaign-url   You can then link to these campaign URLs as desired. A third option would be to use Constant Contact's Email Archive widget, a pre-built tool that is available on certain plan types which displays selected sent email urls on your site: Embed the email archive widget on your website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/8759-add-the-email-archive-widget-to-a-website   Add emails to the email archive widget to display them on your website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/8788-add-or-remove-an-email-from-email-archive   Apply styles and formatting to the email archive widget on your website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/35223-Apply-Styles-and-Formatting-to-the-Embeddable-Newsletter-Archive-Widget   Switching to our new Lite, Standard, and Premium plans https://knowledgebase.constantcontact.com/articles/KnowledgeBase/48672-Switching-to-our-new-Lite-Standard-and-Premium-plans   Please have a look and let us know if you have any other questions!   For questions about the V3 API, you can reach our team directly/securely via email at webservices@constantcontact.com   For questions about the Website UI and/or the Email Archive widget, please please reach out to Constant Contact's Support Team at 866-289-2101. ... View more

Hello MatthewV573, Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API. When making the request for the Authorization Code, after granting access, you will be redirected to a blank page and the code can be found within the blank page's URL, and/or can be retrieved if you have chosen to customize your redirect URL. If you continue to run into issue with this, please reach out to our team directly/securely via email at webservices@constantcontact.com with the API key that you are using, and the URL returned for the blank screen (if available in the program you are using) so that we can take a look at our logs and assist further. Please have a look and let us know if you have any other questions! ... View more

Hello JasonBusch,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The Constant Contact V3 API employs a REST-based resource structure with JSON support for all payloads and HTTP methods for calling endpoints.    Introduction to the V3 API https://developer.constantcontact.com/api_guide/v3_technical_overview.html   Additionally, applications that integrate with Constant Contact using the V3 API, must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user’s data.   You must complete the authorization process and obtain a valid access token i order to make endpoint calls via the API.   OAuth2 Overview https://developer.constantcontact.com/api_guide/auth_overview.html   Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application:  https://v3.developer.constantcontact.com/api_reference/index.html    The request for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   In the meantime, here are the example calls that are currently available for V3:   V3 Code Samples: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.html    Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html    For additional reference, here is the link to a sample that was created/shared on our Developer Forum by a 3rd party developer (NOT created or supported by Constant Contact) for V3 using PHP: https://community.constantcontact.com/t5/Developer-Support-ask-questions/PHP-V3-Library-now-updated-to-new-OAuth2-endpoints-and-PKCE/td-p/383773    Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Thanks it worked for me ... View more

Hello AmandaA4528,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 31783532.   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions! ... View more

Hello Nikunj,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   When accessing the Authorization Request URL, you have to be logged into a Constant Contact account to grant access, because you are granting access for that account.   If you are not already logged in when accessing the Authorization Request URL, and get redirected to the login page, once you log into your Constant Contact account it should direct you back to the page where you grant access to the application Please have a look and let us know if you have any other questions! ... View more

Hello TaraM507,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 31699378 .   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AdamP66,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The Constant Contact API v2 requires the use of SSL with TLS v1.2 and AES encryption or better for all API calls. The leading URI for all API endpoints is https://api.constantcontact.com/v2/. You are not required to have an SSL certificate to make calls into the API.    API Data Formats & more https://v2.developer.constantcontact.com/docs/developer-guides/supported-methods.html   Also, as a side note: While no date is currently set, there will be a point in the near future where our legacy V2 API will begin deprecation (potentially as soon as some point this year), as the deprecation process for our retired V1 API is nearly complete. Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints, and strongly recommend upgrading to the V3 API to ensure you're ahead of the curve. Currently, we've already retired the V2 endpoint for Custom Code email creation, as it used an outdated version of our Custom Code editor that has been retired. If you have any questions about getting started using the V3 API, please let us know.   Please feel free to reach our team directly/securely via email at webservices@constantcontact.com with any follow-up questions.   If you would like us to look into this further with you, please include the following in your email: TLS/SSL version in use by your application,  the API key that you are using to make the request, the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue. ... View more

To make it work did as you suggested.  1) Try to get  the contact using email address.  If no match, add new contact.  If match, capture the current values I need, append them to the values passed in, then Put the data back to just append the new list data as needed to the contact instead of changing the lists. ... View more

Hello HelpingHandsAct,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Based on what you are experiencing, it looks like the refresh token is most likely not being stored correctly as a variable within the application.   If you continue to run into issues, could you please contact us directly/securely via email  at webservices@constantcontact.com (do not post sensitive info in the community) and provide us with the API key that you are using to make the request, the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue?   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions! ... View more

Hello ErinR842,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The process listed above is just for those who are building an integration with Constant Contact and prefer to do it programmatically.   To download your campaigns as a PDF within the website interface, you can follow the steps in the following article:   Download or print an email https://knowledgebase.constantcontact.com/articles/KnowledgeBase/6130-download-an-email-campaign   Alternately, once each email is sent, we host a permanent URL for each sent email as a web page which you can link to if you'd prefer:   The permanent URL for a campaign https://knowledgebase.constantcontact.com/articles/KnowledgeBase/6128-email-campaign-url   If you would like assistance with this process, please reach out to Constant Contact's  Support Team at 866-289-2101.   Please have a look and let us know if you have any other questions!   ... View more

Hello MaianneP,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Once you find a developer to assist with your project, the below info may be of use when updating from V2 to V3:   Our current V3 API uses OAuth2.0, which is the current industry-standard for authorization. It’s more secure and does a much better job of keeping your Constant Contact account data safe. When you give their integration permission to access your account, it will show you exactly which permissions the integration is requesting to be granted (rather than just granting all permissions). V3 also uses tokens that are continuously refreshed to keep the connection encrypted and secure, rather than just accessing the account via your username and password.   There are several significant differences between our V2 and V3 APIs, including the use of different endpoints, OAuth 2.0 rather than basic authentication, JSON payloads instead of XML, and a different format for resource identifiers.   A quick start guide for the V3 API can be found here: https://developer.constantcontact.com/api_guide/getting_started.html    While the rest of our documentation is linked from the quick start guide, the following pages in particular may be useful: https://developer.constantcontact.com/api_guide/v3_technical_overview.html  https://developer.constantcontact.com/api_guide/developer_portal.html  https://developer.constantcontact.com/api_guide/migration_overview.html    Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application:  https://v3.developer.constantcontact.com/api_reference/index.html    While Constant Contact doesn’t offer any services as far as assistance with building custom integrations, and our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you or your developer have any other questions! You can also reach our team directly at webservices@constantcontact.com ... View more

Hello user914495,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   If you continue to see issues with this, please feel free to contact our team directly via email at webservices@constantcontact.com , referencing case number 31498278.   Within your email, please provide us with the API key that you are using to make the request, the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue.   Please have a look and let us know if you have any other questions! ... View more

Hello CaitlinO7,   Thank you for reaching out to Constant Contact API Developer Support.    Adding or updating custom field values for a contact should be reflected in the response body when making a call to GET /contacts with the query parameter updated_after.   However, there are two  "updated_at" values that are returned in the response body, and only one of them will update with that type of change.   Example endpoint call: GET https://api.cc.email/v3/contacts?updated_after=2023-08-28T20%3A07%3A10Z   Example response body: {       "contact_id": "1618ae62-4752-11e9-9c8a-fa163e6b01c1",       "email_address": {         "address": "dlang@example.com",         "permission_to_send": "implicit",         "created_at": "2016-03-03T15:53:04.000+00:00",         "updated_at": "2016-03-03T15:56:29.000+00:00",         <this value will not update         "opt_in_source": "Contact",         "opt_in_date": "2016-01-23T13:48:44.108Z",         "confirm_status": "confirmed"       },       "first_name": "Debora",       "last_name": "Lang",       "job_title": "Musician",       "company_name": "Acme Corp.",       "birthday_month": 11,       "birthday_day": 24,       "anniversary": "2006-11-15",       "update_source": "Contact",       "create_source": "Account",       "created_at": "2016-01-23T13:48:44.108Z",       "updated_at": "2016-01-23T13:48:44.108Z",                      < this value should update   If you continue to see issues with this, please feel free to contact our team directly via email at webservices@constantcontact.com , referencing case number 31463852.   Within your email, please provide us with the API key that you are using to make the request, the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue.   Please have a look and let us know if you have any other questions! ... View more

Still I am facing the same issue while generating the access token. ... View more

Hello DannyT37,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Constant Contact provides developers with free access to our V3 API endpoints for developers building their own application for integration. You can get started using our API by visiting our documentation here: https://v3.developer.constantcontact.com/api_guide/getting_started.html   Additionally, you can utilize our API Reference Page to find body schemas & values, as well as test the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   When developing your own application for integration, you’ll need to set it up so that the application calls/retrieves the data of your choosing using the your software's API or other data export method (You will need to check their API documentation or contact their support team for help with how to configure this part), then you will program your application to sort out which variables you need and parse them into the correct format for Constant Contact’s API, at which point you can send that data through to the Constant Contact account via an authenticated connection (or vice versa).   While Constant Contact doesn’t offer any services as far as assistance with building custom integrations, and our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions! ... View more

Excellent! Thanks, Courtney!   Hopefully, your team will decide that change makes sense and some other individuals or companies will benefit from that information.   Thanks for all your help!   Osman Erzinclioglu | Senior Technical Analyst, Business Technology, AGF Investments Inc. T 647 253-6838 E osman.erzinclioglu@AGF.com ... View more

Hello Kmayer21,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It's our understanding that this issue is caused due to Outlook not supporting "px" or setting these variables in the style attribute. The following workaround is suggested to bypass this display issue:  Change the code so that it does not use the 'px' for the size and also has the height and width set individually.   In case it is helpful, I have also linked the following article which contains a List of supported HTML tags for Custom Code emails within the current Custom Code editor, as the old editor was retired since this thread was originally created.   Errors in a custom code email https://knowledgebase.constantcontact.com/articles/KnowledgeBase/33242-Errors-in-a-Custom-Code-Email   If you have further questions regarding Custom Code emails, please feel free to reach out to Constant Contact's Support Team at 866-289-2101 and request to be connected with a Custom Code specialist. Your case number for reference is #31433001. ... View more

Hello ChristopherW5602,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The Source column within the Contacts tab of the Website UI is a hard-coded part of the UI that cannot be modified, and will only display pre-populated source types such as "Website sign-up form", "Inline", "Other app", and "Added by you".    The Source label "Other app" indicated that the contact was added via a 3rd party integration or signup form that was developed by a 3rd party using our free public API.   If your intent is to better categorize the sources of contacts being added by your application, you can do so by using one of our other contact management tools, such as Lists, Tags, or Custom Contact Fields, all of which can be modified using the API.   The "create_source" variable in contacts indicates who the contact was added by, and indicates the type of permission given, which ensures that we remain compliant with any applicable laws and regulations in the areas that we offer service.    For example, if you upload a list of contacts, or sync a list of contacts from another platform, you'd want to use "Account" because those contacts were added by you, and you have implied that you have permission to email them. If the contact is being added via a sign-up form, or some alternate method where the contact is the one confirming that they want to be added to a list, you would use "Contact", as the contact has given firsthand permission.    Understanding implied and express permission for CASL and GDPR: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5924-implied-and-express-permission-in-casl-regulations    Please have a look and let us know if you have any other questions!   ... View more

Hello user371954,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Based on our logs, it looks like you may have already resolved your issue, but if not, here is some more information:   There is currently no way to bypass the initial Authorization Request screen, which can only be accessed/authorized via a browser window, but you should only need to authorize an account once.    You'll want to paste the Authorization Request URL into the browser, grant access, and then you will be redirected to a URL containing the Authorization Code.   After the Authorization Code is returned in the browser, you should be able to take that value and perform the rest of the authorization process within your program.   OAuth2 Authorization Code Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Hello JohnS76814,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   For privacy purposes regarding your account, we’ve followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 31395698.   Please have a look and let us know if you have any other questions! ... View more

Hello user8916157,   Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   While the wildcard option has been removed from the redirect URI at the domain root level in our V3 API's new authorization management service in order to improve security, there are still other options available as far as passing additional information via your authorization request.   Within the redirect URI itself,  the lowest level subdomain will still support wildcards.   Example Request URIs:   App Redirect URI: https://subdomain*.example.com/oidc/redirect Auth request URL Redirect URI: https://subdomainvalue.example.com/oidc/redirect   App Redirect URI: https://*.example.com/oidc/redirect Auth request URL Redirect URI: https://value.example.com/oidc/redirect   Alternately, the newly added state parameter can also be used to pass additional values through the Authorization Request URL.   Here are three ways that you might implement this, from least secure to most secure:   Option 1: Use the additional value as the state value (least secure, directly exposes the additional value in the URL, and so isn't secure).   Option 2: Base64 encode the additional values, and use that as the state value (more secure, but still not random, and can be decoded).   Option 3: Come up with some formula to encode the additional values + a random value, which your program can decode when you get the response (fairly secure).   Option 4: Use a completely random state value for each additional value, save it within your application before sending the request associated with that value, then use the state value to look up the additional value upon receiving the response (most secure).   Please have a look and let us know if you have any other questions! ... View more