We have also been getting these messages the last 5 days or so.  This API is heavily used by our customers and is critical to their day to day processes.   When can we expect this to be fixed?   Secondly, if v3 is in Beta, please make this more apparent on your v3 landing page I believe it was recommended that we upgrade, but a lot of our customers have migrated.  Is there a way to roll back from v3 to v2?    ... View more

I was looking though the documentation and I don't see any webhooks being offered.  It would be nice to have some webhooks especially for unsubscribes and list removals.  ... View more

We are working on implementing the new V3 version of your API.  When we push over a contact that has a special character in their name (in this case "Boglárka") we are receiving the "invalid byte sequence in utf-8" error.  I have code that converts the unicode to ISO-8859-1 but it still gives this error. Am I converting this string incorrectly?  I get the same issue when I add or update this contact.  Bulk import blows up the entire batch.  Request Body: { "contact_id": null, "email_address": { "address": "hansoncolton_137@mailinator.com", "permission_to_send": "implicit" }, "first_name": "Boglárka", "last_name": "Balassaa", "job_title": "", "company_name": "", "create_source": "Account", "update_source": "Account", "phone_numbers": [], "street_addresses": [{ "street": "", "city": "", "state": "", "postal_code": null, "country": "", "kind": "work" } ], "list_memberships": ["91ef3366-4f41-11e9-bc63-d4ae52806b34", "6bbe73a8-4f3e-11e9-8fc2-d4ae5292c973", "6bd796b2-4f3e-11e9-b034-d4ae528ed502"] } Response: [ { "error_key": "contacts.api.bad_request", "error_message": "invalid byte sequence in UTF-8" }] ... View more