-
- Sign Up Free
- Log In
-
Turn on suggestionsAuto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About SegmintD
SegmintD
Frequent Participant
since
12-09-2021
03-25-2022
10
Posts
1
Kudos
0
Solutions
Badges
03-23-2022
05:29 PM
1 Kudo
So far in our Constant Contact integration, we have been successful with the older 'idfed' Oauth2 endpoint for retrieving access tokens with a POST. However, during the maintenance outage yesterday learned that we had to switch to use a new 'authz' endpoint by March 31st, very surprising to hear of this. So far, in trying to adapt to using the new 'auth' endpoint, we get 400 errors in testing. I have this POST: https://authz.constantcontact.com/oauth2/default/v1/token?code=AUTHCODE&redirect_uri=URI&state=STATE_ENCODED_VALUE&nonce=NONCE_ENCODED_VALUE&grant_type=authorization_code (the UPPERCASE values hide the actual values) to which the response is a 400 error. data: { errorCode: 'E0000021', errorSummary: 'Bad request. Accept and/or Content-Type headers likely do not match supported values.', errorLink: 'E0000021', errorId: 'oaeEf5o-pigQ0Cqtj6gey4rCA', errorCauses: [] } Looking at the message about the Accept or Content-Type headers, I checked what was being sent: 'Accept: application/json, text/plain, */*\r\n' + 'Content-Type: application/json;charset=utf-8\r\n' + Note that these values for Accept and Content-Type headers are unchanged from what was being sent to the old 'idfed' endpoint. The only changes to the new endpoint were copying the API Key and getting a new client secret per the instructions on migrating to the new endpoints, encoding these in the Authorization header, changing the URL and adding the state and nonce query parameters. Any thoughts on what might be the issue? I've been following these instructions:
... View more
03-02-2022
02:41 PM
The is the exactly what we have run into with building out our integration w/ CC V3 API. We have two developers in different time zones, and I get a text message on my cell phone periodically when the other developer is trying to login to CC...I then have to text them the MFA code. And sometimes, when I login, I trigger the MFA and get the text and have to enter the code myself..it's all very random.
... View more
02-03-2022
09:54 AM
Thank you for the continued help! We finally got the format to the standard, and that seems to work. Why do some of our calls work with the bodies you see (e.g. using phoneNumbers and not phone_numbers), but these calls to remove a value do not? We have definitely used calls with phoneNumbers to update the value of a phone number without an issue. We only encountered this problem when we tried to remove values which seems strange and inconsistent. Thank you again!
... View more
02-01-2022
10:22 PM
I believe I have updated our code to use the snake_case values you indicated (though I still do not think this is the problem since our normal update calls work with our existing generated API code), and I do not think that it solved the problem. Our existing code (and the current code) are capable of updating the value of a custom field or phone number. However we still cannot update the value to a blank value to remove the data from the contact in Constant Contact. Even though we are sending a blank value and receive a 200 response, nothing changes with the contact in ConstantContact.
... View more
01-28-2022
08:25 PM
I think that is just a discrepancy between how the body of the call logs in our program and how it reaches the actual API? We use this exact same call to update values in the contacts (for instance, updating a phone number), and it works fine. The only thing that doesn't seem to work is updating the value to be blank. Is there anything else that could be causing the issue? Thank you!
... View more
01-28-2022
02:56 PM
Thank you for the response. I have tried sending the subresources using a blank value. The API call succeeds, but no change occurs within the contact. An example of the body generated by our code: class ContactPutRequest { emailAddress: class EmailAddressPut { address: {{{aykeLohJnTdTIh1AZSPW1gGNzgrYcbh71yXmNM1iBm2nvLn5Z5x9si}}} permissionToSend: implicit } firstName: {{{NrxKAayoOX}}} lastName: {{{yoEytn64h8BClz}}} updateSource: Account customFields: [class ContactCustomField { customFieldId: 397abae4-7481-11ec-b411-fa163eaf1c42 value: {{{kUyYfv9TeomTatKrO431Mk03v1fxS1H3solfxLbfI6W3I40hMQzLFv4QR4qUDHJW}}} }] phoneNumbers: [class PhoneNumberPut { phoneNumber: kind: other }] listMemberships: [4df2e336-71b9-11ec-b411-fa163eaf1c42, 55953f04-73bb-11ec-b55c-fa163e470cab, 93ac28d6-7f8f-11ec-a993-fa163eaf1c42, bd3ef544-77b4-11ec-abf0-fa163ed2816c] }
... View more
01-27-2022
08:39 PM
How do I remove a contact's phone number (& custom field value) using the API? I have previously added a contact using the API. The contact contains a first name, last name, email, phone number ('other') and a custom field. If the contact's information changes, I would like to be able to remove these values. I can successfully remove the first name and last name using a putContact call; however, I have been unable to remove the phone number or custom field in this manner. Thank you!
... View more
01-07-2022
03:11 PM
Thanks for the followup. I looked closely at my Client API code (which was generated Java code done using the CC V3 schema and swagger) and it was sending all 3 of mutually exclusive attributes in the source. I had to change some properties to not be used when null and it is working now. Regards, Robert at Segmint, Inc
... View more
01-06-2022
06:12 PM
I noticed that the C3 postContact and putContact services both take an array of phone numbers with types (mobile, home, etc) yet the createOrUpdateContact service has only a single phone number field with no type. How does that single phone number correlate to the multiple that can be sent with postContact and putContact? Why not have an array of phone numbers w/ type in createOrUpdateContact also?
... View more
01-05-2022
05:24 PM
I'm trying to remove one contact from one list via the Bulk Activity API. I get this error: 400 Bad Request: [[{“error_key”:“contacts.api.bad_request”,“error_message”:“source[list_ids] is empty, list_ids, contact_ids are mutually exclusive”}]] My JSON payload only sends the one contact id that I want to remove from the list: (note that the quotes around the attribute names and values don't show up--they aren't there in the objects but apparently get added by the Spring Rest Tempate--I've had success calling other CC V3 API endpoints with this Java client). { source: { contact_ids: [e19f3996-6e48-11ec-ac92-fa163e963dae] }, list_ids: [24337c6e-6da8-11ec-b55c-fa163e470cab] }
... View more
Latest Tags
No tags yet
