About Courtney_E

Thank you for reaching out to Constant Contact API Developer Support, and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Based on the code provided, as well as your comment on this post, it looks like you were able to resolve the grant_type error you had been running into. Also, you shouldn't need to be logged into the developer portal for the account to stay authorized if you have completed the OAuth2.0 flow to grant access to the Constant Contact account you'll be working with.   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 SDKs or 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 sample calls that are currently available for V3: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.html   If you still need assistance with this, please let us know! ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   You can generate a new Access Token via the V2 API Tester in Mashery using the "Get Access Token" option near the top of the page. V2 API Tester https://constantcontact.mashery.com/io-docs ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Your feedback regarding the use of OAuth2.0, has been submitted for review and consideration by our team. Your experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter. ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like we'll some additional information in order to assist with troubleshooting. If you could please provide us with your full URL request, the API key you are using, as well as any timestamps you have available, we'll be able to better assist in pinpointing the cause of the null response. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, and reference case number 28009990. We look forward to assisting you! ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   If you're building your own integration/form, here are some of the endpoints that you can call in regards to contacts:   Bulk Activity Endpoint for Importing Contacts: https://v3.developer.constantcontact.com/api_guide/import_contacts.html   Endpoint for Creating or Updating a Contact https://v3.developer.constantcontact.com/api_guide/contacts_create_or_update.html   If needed, you may be able to find a front-end form in the OpenCart Extension Store: https://www.opencart.com/index.php?route=marketplace/extension ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   When, for example, adding contacts to a list from a custom sign-up form app, the "user" referred to in the OAuth Server Flow would be the owner of the website who is setting up the form, as opposed to the contacts filling out the form. The owner of the website (and Constant Contact account) would grant the app access to their account during the initial setup of the form, after which the app would use step 5 of the Server Flow to exchange it's Refresh Token for a new pair of tokens whenever the Access Token expires, without the owner needing to log in again.   The Client Secret is used in step 4 of the V3 API OAuth2.0 Server Flow and is used to acquire the initial Access Token and Refresh Token.   V3 API OAuth2.0 Server Flow https://developer.constantcontact.com/api_guide/server_flow.html   V3 API Token Overview https://developer.constantcontact.com/api_guide/auth_overview.html#tokens ... View more

Hello MaggieS418,   Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   When adding contacts to a list from a custom sign-up form app, the "user" referred to in the OAuth Server Flow would be the owner of the website who is setting up the form, as opposed to the contacts filling out the form. The owner of the website (and Constant Contact account) would grant the app access to their account during the initial setup of the form, after which the app would use step 5 of the Server Flow to exchange it's Refresh Token for a new pair of tokens whenever the Access Token expires, without the owner needing to log in again.   V3 API OAuth2.0 Server Flow https://developer.constantcontact.com/api_guide/server_flow.html   V3 API Token Overview https://developer.constantcontact.com/api_guide/auth_overview.html#tokens ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like we’ve connected with you via email regarding this issue, as we required additional information in order to better assist. If you still need assistance with this, or if you haven't received our reply, please let us know via email at webservices@constantcontact.com ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like you may have already switched to one of our Inline Sign-Up Forms as a resolution. That said, our standard V2 API rate limit is 10,000 calls per day, and 4 calls per second. Your key was occasionally exceeding the calls per second limit. Ideally, the integration you're using should re-try any requests which fail due to this limit. If you've noticed that these requests are not being re-tried, or are concerned that they may not be, you should reach out to the integration's developer. ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We're still in the process of rolling out new endpoints for Tags support in the V3 API.   It looks like a bulk activity endpoint to remove Tags has been published, but as of just yet, there is no bulk endpoint for adding Tags: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/postTagRemoveContact   There are also Tag capabilities in the body schema for creating or updating an individual contact, but none for the sign_up_form endpoint currently: https://developer.constantcontact.com/api_guide/tags_overview.html   We look forward to making new endpoints available for Tags. You can keep up to date on the latest available V3 endpoints here: https://developer.constantcontact.com/api_guide/release_notes.html ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   It looks like you are using the V3 API documentation and endpoints with a V2 API key and access token, which is likely the reason you are receiving an error. The app that you have registered in the Dev Portal should have your V3 API key, and the API endpoint tester at v3.developer.constantcontact.com also accesses the V3 API key that was created. To resolve this, you’d want to use the V3 API OAuth2.0 Server Flow to authenticate the connection and generate an access token and refresh token. Those instructions below:   V3 OAuth2.0 Server Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   For your privacy and security, we’ve removed the image of your V2 API Key and Client Secret that was included with your post, and have also revoked the token (the Client Secret was no longer secret). If you do need to use the V2 API, I’d recommend generating a new key. The V2 API keys generated through Mashery have a different authentication flow and endpoints than the V3 API.   V2 API Documentation https://v2.developer.constantcontact.com/docs/developer-guides/overview-of-api-endpoints.html ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   Here are the available instructions we have for installing Constant Contact’s Inline Sign-Up Form on various website hosting platforms: http://knowledgebase.constantcontact.com/articles/KnowledgeBase/18053-activating-and-installing-your-sign-up-form   If your hosting platform is not listed, or you are having trouble installing it where you want, we’d need to refer you back to your website hosting platform’s support for assistance with where to install the Universal and Inline Code.  ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. 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 27920040. ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The V3 API uses both an Access Token and a Refresh Token, rather than a long lasting token like the V2 API uses. Using access tokens with a limited lifespan decreases the risk and impact of compromised credentials. V3 still makes use of Authorization Bearer for the Access Token, but you will also need to use the Refresh Token to obtain a new Access Token when the existing one expires.   When going through the OAuth2.0 Server Flow for the V3 API, you should only need to use the Authorization Request URL once, and then after that you can exchange the Authorization Code for an Access Token and a Refresh Token which can be used to authenticate from that point forward.   OAuth2.0 Server Flow for the V3 API https://v3.developer.constantcontact.com/api_guide/server_flow.html   More about V3 Tokens https://developer.constantcontact.com/api_guide/auth_overview.html#tokens ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. 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 here is the information provided for visibility on the forum:   We don't have a developer account per say but you are able to create a free trial account through our developer portal which will allow you to have a trial account with limited sending capabilities. From there you can use the trial account for your testing purposes. Below is a link to our developer portal where you can sign up for a trial account, you'll just need to click on "Get Started" and then "Sign up".   Constant Contact Developer Portal https://developer.constantcontact.com/ ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. 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 27879122. ... View more

Hello Marci,   Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   If you still need assistance, please let us know! Constant Contact API Developer Support can be reached directly by email at webservices@constantcontact.com ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. My team is here to assist outside software developers with questions about building into Constant Contact's API.   To the question at the end of the post, it isn't necessary to refresh the token every time it's used, only if it's expired. The two most common reasons for expired refresh token errors are:   1) When you refresh, you get both a new access token and a new refresh token. If you are able to refresh once, but subsequent refreshes fail, you may not be storing the new refresh token, and the code may be continuing to use the old one.   2) If you are starting the authentication flow over from the beginning, any previously generated tokens are immediately expired; you have to use the most recent set of tokens.   If this doesn't resolve your issue, please feel free to send us an email at webservices@constantcontact.com with your API key and the username of the account you’re connecting to so we can look into it further for you. ... View more

Thank you for reaching out to Constant Contact API Developer Support and for your patience. 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 here is the information provided for visibility on the forum:   Based on what you described it sounds like you're utilizing an Automated Campaign which sends to contacts anytime they're added to a particular list. When it comes to Automated Campaigns there isn't a way to create, copy, or edit them through our API at this time but that is a feature we're looking into implementing in the future, we just don't have a time frame when that would be available.   Just to confirm, it sounds like you want to be able to utilize those Automated Campaigns and customize it based on the contacts. If that's the case, you could keep the same Automated Campaign and perhaps use dynamic contact fields to automatically generate contact's information in those emails.   If so, below is a link to documentation on Creating and Manage Custom Contact Fields https://knowledgebase.constantcontact.com/articles/KnowledgeBase/33120-Create-and-Manage-Custom-Contact-Fields   ... View more

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 the provided code, there are two areas that may need to be adjusted:   $contact->id = "12345678"; I would remove this line from the code, as we assign an ID automatically upon creating the contact.   $contact->addList('099896ba-0ce6-11eb-81d5-**********'); This line appears to be identifying the list_id. The V2 API doesn't use the list_id and needs a different value here, as V2 and V3 APIs use different formats for list IDs.   If you are unsure how to get the correct values for the account's lists, you can use this function from the PHP SDK: http://constantcontact.github.io/php-sdk/class-Ctct.Services.ListService.html#_getLists   You can also just use the V2 API tester to get those values: https://v2.developer.constantcontact.com/docs/contact-list-api/contactlist-collection.html   If fixing those two items doesn't resolve the issue, we would need to know the new response you’re receiving, preferably with the full error message so that we can look into this further for you. ... View more

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 reached out to you via email regarding this issue to request some additional information in order to assist with troubleshooting, but here is the information provided for visibility on the forum: In regards to the 400 error, that's often due to malformed data or a data validation error. Just so we can research and test the issue further, would you be able to email us the body coding you're using to add those fields into Constant Contact? If you haven't received our email reply, please let us know via email at webservices@constantcontact.com, and reference case number 27790342. ... View more

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 customers using integrations developed by 3rd parties using the Constant Contact API, we will typically refer them back to the developer of the application, as we do not have access to the application data needed for troubleshooting. If the developer of the Stripo integration believes that the issue is on Constant Contact's end, the developer will need to reach out to Constant Contact directly via the Developer Community forum or by email webservices@constantcontact.com with the details of the failed calls. ... View more

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 would recommend authenticating using the OAuth2.0 Server Flow so that you can use the access token and refresh token to re-authenticate without the login prompt reappearing each time. The Client Flow is typically used only if the application is unable to securely store the client secret. https://v3.developer.constantcontact.com/api_guide/server_flow.html   For additional help with this, please let us know what kind of application you’re building so that we can offer more detailed assistance. ... View more

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 are only getting the error with specific contacts, we’d be happy to look into this further with you.  Please feel free to email us at email us at webservices@constantcontact.com, referencing case number 27616858, and include the account's username, and any example contacts whose email addresses are being affected. If you are also able to send us the full payload, that would be best. We look forward to assisting you! ... View more

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.   Below is a link to documentation on how to obtain an API Key and Access Token along with documentation on how to implement that information into the Bloom plugin.   How to generate an API Key and Access Token: https://community.constantcontact.com/t5/Community-News/How-to-generate-an-API-Key-and-Access-Token/ba-p/293856   Constant Contact and Bloom https://www.elegantthemes.com/documentation/bloom/accounts/   Please have a look and let us know if you have any other questions! ... View more

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 via email, but here is the information provided for visibility on the forum: I'm sorry but at this time our V3 API requires OAuth 2.0 to authenticate the customer's account and there is no way to bypass it. ... View more

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 via email, but here is the information provided for visibility on the forum: In regards to there being an easy way to pull email campaign reporting information, that would all be dependent on how the CRM has their integration set up to pull in Constant Contact campaign reporting information. If you're currently in the process of determining what CRM you'll be selecting, I would recommend asking if they have an integration with Constant Contact or if they have a way to pull information into the CRM via an API. Below is a link to documentation on email campaign reporting with our API. This documentation may be useful while you're still looking into CRMs.   Email Reporting Overview https://developer.constantcontact.com/api_guide/email_reporting_overview.html ... View more

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 regarding this issue to request some additional information in order to assist with troubleshooting, 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 27625712. ... View more

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 customers using integrations developed by 3rd parties using the Constant Contact API, we will typically refer them back to the developer of the application, as we do not have access to the application data needed for troubleshooting.    If the developer of the Stripo integration believes that the issue is on Constant Contact's end, the developer will need to reach out to Constant Contact directly via the Developer Community forum or by email webservices@constantcontact.com with the details of the failed calls. ... View more

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 here is the information provided for visibility on the forum: Based on the information provided it appears that you're requesting information for our V3 API which generates the API Key and Secret but doesn't give you an Access Token right away as we use OAuth 2.0 for verification instead. When it comes to our V3 API we don't also don't utilize Mashery. If you need an API Access Token for our V3 API below are links to steps on how to obtain the Access Token along with Access Token Information.   V3 API: Retrieve the Access Token https://developer.constantcontact.com/api_guide/client_flow.html#step-3-retrieve-the-access-token Access Token Information Method https://developer.constantcontact.com/api_guide/token_info_method.html   Also, just in case this is what you needed instead, here are steps on how to obtain the Access Token for our V2 API. V2 API: How to generate an API Key and Access Token: https://community.constantcontact.com/t5/Community-News/How-to-generate-an-API-Key-and-Access-Token/ba-p/293856 ... View more