Hello user2865428,
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.
Thanks so much for your feedback regarding the 6MB file size limit for contact exports. It has been submitted for review and consideration by our engineering team. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.
Regarding all fields not being exported when using the Export Contacts to a File request, every contact field, including custom fields should be exported by default. When using the “fields” array, only the specified fields are exported. If you have any examples of a field not being exported when not including the “fields” array, or when including that field in the array, we would be happy to investigate if you could send an email to webservices@constantcontact.com which specifies your API key, includes a full example request, including headers, an example response, and any timestamps you may have from previous requests where this behavior occurred.
For the CSV formatting concerns that you mentioned regarding commas, one method you could use to escape the field values, which may contain commas from the commas separating the field values, is to put the field values within quotation marks.
I was able to confirm that address line 1 and address line 2 being combined in a single cell upon exporting contacts is functioning as designed, however, I would be happy to pass your feedback to the appropriate teams if you feel these fields should have their own cells.
Regarding the filtering options for the contact export request, if by GET request you’re referring to the GET Contacts Collection request, the list ID is returned in the response under the “list_memberships” property. Currently, only the list_id can be used to specify the contact list in the contact export request. I would be happy to pass your feedback regarding the ability to use the list name in place of the list_id to the appropriate team, though we can’t guarantee if or when this feature will be implemented.
GET Contacts Collection:
https://developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts
Regarding segment_id’s, you can obtain all of your account’s segment_id’s by utilizing the GET all Segments request.
GET all Segments:
https://developer.constantcontact.com/api_reference/index.html#!/Segments/getAccountSegments
Regarding the issue you encountered with physical address field values populating under random “Home”, “Work” and “Other” groupings in the website UI, we greatly appreciate you bringing this to our attention. I have documented this issue and passed it up to our engineering team to review for a resolution. For the meantime, the best method to ensure that these field values appear correctly under their corresponding physical address type is to group all “Home”, “Work” and “Other” address fields together in the request body as is shown in the Body sample of the JSON import request documentation I am linking below.
Import Contacts using a JSON Payload:
https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/bulkImportContactsJSON
When you receive an error response which states “The requested resource was not found”, this typically indicates that a list, contact or segment ID used in the request was not found on the account. We would be happy to investigate this further if you could send an email to webservices@constantcontact.com which specifies your API key, includes a full example request, including headers, an example response, and any timestamps you may have from previous requests where you received this error response.
Please have a look and let us know if you have any other questions!
Regards,
... View more
