Hello,   There doesn't need to actually be any Postman token in your calls. For details on our server flow, see: https://v3.developer.constantcontact.com/api_guide/server_flow.html   The short description is that to connect an app, you first will direct them to an authorization URL. This will take the user to a Constant Contact login page. After they log in, they are asked to allow your app access. After clicking allow, they are then redirected to your Redirect URI, with a code appended in a query parameter. Then you need to make a POST call passing along that code in order to get an Access Token and a Refresh Token.   Access Tokens have a limited timeframe they can be used, but when they expire you can use the Refresh token to get a new access token and refresh token to keep making calls.   The other thing I'll mention is that our API is looking for a JSON string of the body content. You may need to use something like JSON.stringify() on your data before submitting the request.   Please let us know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   You can use a wildcard in your redirect URL but can place it at a slightly different spot to accommodate your use case. Please try registering the following as your redirect URI and let me know if you see the same issue: http://joomla.development/main/administrator/index.php*   Regards,   David B. Tier II API Support Engineer ... View more

Hello everyone,   Thank you for your patience as we work through this. We are currently experiencing intermittent gateway timeout errors with our V3 API. I have asked that our status page to be updated to reflect this current system issue. We are still investigating the root cause. While I can't provide an ETA on a fix, I can say that we are taking this issue seriously and that this is currently our top priority.   Sincerely,   David B. Tier II API Support Engineer ... View more

Hello everyone,   Thank you for your patience as we work through this. I have asked that our status page to be updated to continue to reflect this current system issue. We are still investigating the root cause. While I can't provide an ETA on a fix, I can say that we are taking this issue seriously and that this is currently our top priority.   Sincerely,   David B. Tier II API Support Engineer ... View more

Hello everyone,   Thank you for your patience as we work through this. I have asked that our status page to be updated to continue to reflect this current system issue. We are still investigating the root cause. While I can't provide an ETA on a fix, I can say that we are taking this issue seriously and that this is currently our top priority.   Sincerely,   David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Your developer can reach out to us by email at webservices(at)constantcontact.com with any questions they have about our API. Our main support team can assist with any questions regarding setting up our automated email campaigns, or creating segments based on contact details.   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support. I'm sorry for the trouble.   We are currently experiencing a temporary system issue that is causing frequent timeout responses. Our engineering team are working to correct this as quickly as possible.   Regards,   David B. Tier II API Support Engineer   ... View more

Hello,   Please email us at webservices(at)constantcontact.com with your authorization URL and the API Key you are using and we'll be happy to look into this for you.   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   It looks like you're looking for information about self authentication with Constant Contact. I would recommend reaching out to our Account Review team as they can help you with updating your DKIM key and answer any questions you have about self authentication. You can reach them at:  866-433-8499   Regards,   David B. Tier II API Support Engineer   ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   I'd like to look into the configuration of your API Key. Please send us an email at webservices@constantcontact.com with your API Key and the redirect URI you are passing through with your OAuth call.   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   Where are you being prompted to do this? Are you working in an app you are building, or are you using a 3rd party integration?   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Can you clarify what you're looking to do? Are you using our V2 or V3 api?   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Can you clarify what you're looking to accomplish? Our Authorization headers should be Bearer rather than Basic, and your access token is obtained during the OAuth flow.   Are you using our V2 or V3 API?   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   I wasn't able to find anything inherently incorrect with the body of your email. Assuming that you have verified the email address being used as the from/reply, that should also be okay.   So taking a look at your sample, your payload is starting with an object called 'json', whereas the body should just contain the details. For example this: {'json': {'name': 'My new message-1571836258463'....   should instead look like this: {'name': 'My new message-1571836258463'.... with the closing bracket removed as well at the end.   Please give that a try and let me know if you're still having trouble.   Regards, David B. Tier II API Support Engineer   ... View more

Hello,   That error in this case typically means that there isn't a contact with that ID in the account you are working with. Would you be willing to send an email to us at webservices(at)constantcontact.com with the Constant Contact username you are working in? I can do some digging and verify exactly why you're getting that error.   Please let us know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   The contact ID actually goes in your request URL and not as a header item. So for your example, you would make a call to: https://api.constantcontact.com/v2/contacts/1206033418/tracking?api_key=somekey   And include your Authorization header (with the bearer token) along with it. This will return all of the tracking associated with this specific contact.   Please let us know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello Sveta,   If you are seeing this data not going into the custom field and instead going into the street address, I would say that may be a possible bug. I'd like to research this a bit further in detail. Would you be willing to email us at webservices(at)constantcontact.com with an example of the body of your request, as well as the Constant Contact username that you are making the call to?   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   A 409 conflict usually comes up when you are trying to use something that is unique and already in use, such as an email address. Though I can't say for certain why you are seeing this on an individual update when making no changes at all.   Since it seems to only be this one contact, I'd like to get more detail about them. Please email us at webservices(at)constantcontact.com with your Constant Contact username, and the email address for this contact and we'll be happy to take a closer look.   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   We use current OAuth standards for security purposes. Access tokens are good for up to 24 hours. Refresh tokens don't expire, but will become invalid if they are used or if the initial authorization flow is completed again. If you could use the same refresh token over and over, that kind of defeats the purpose of having a rotating access token.   When you use your refresh token, you get a new access token and a new refresh token as well. You then use the new access token until it expires, and refresh using the refresh token that was given at the same time as the access token you were just using.   Typically in a situation such as yours where you have multiple users making calls for the same Constant Contact account, you would have your server control all of your calls, storing the access and refresh token, and refreshing it when needed. Please let me know if you have any other questions.   Sincerely, David B. Tier II API Support Engineer     ... View more

Hello,   What scope are you using in your OAuth authorization flow? Regards, David B. Tier II API Support Engineer ... View more

Hello,   Our inline form that is available within your account is not able to have a placeholder and instead has a label above the field. You may find using our Constant Contact Forms for Wordpress plugin more to your liking as this does let you set placeholder text. For more details about it see: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/Using-Constant-Contact-Forms-for-WordPress-Video?lang=en_US   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for that information. It looks like you are building your authorization header to have braces { } around your access token. These are not needed, so you should build your header like this: curl_setopt($ch, CURLOPT_HTTPHEADER, array('authorization'=>'Bearer '.$access_token)); Please give that a try and let us know how that works.   Regards, David B. Tier II API Support Engineer     ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Unfortunately our API can only be called from the back end of a website. There are no current plans to add support for cross-origin resource sharing, so you would need to use a server-side process to make the actual calls to our API.   Solutions that others have used is to have a separate server and pass data via AJAX to that separate server, which then makes the API calls on your server behind the scenes.   Please let me know if you have any questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello,   The back slashes are only needed when breaking up the request into multiple lines. Since you are doing this all on one line, they can be omitted. For example:   curl -X POST https://api.cc.email/v3/activities/contact_exports -H 'Accept: text/csv' -H 'Content-Type: application/json' -H 'Authorization: Bearer {access_token}' -H 'Cache-Control: no-cache' -d '{ "list_ids": [ "f5cb02a0-88c7-11e5-9497-d4ae5275b546" ], "fields": ["email_address"], "status": "active" }' Please give this a try and let me know if that works for you.   Sincerely, David B. Tier II API Support Engineer     ... View more