- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
According to https://v3.developer.constantcontact.com/api_guide/contacts_delete.html it should be possible to restore deleted contact by making a PUT request to https://api.cc.email/v3/contacts/{contact_id}, but unfortunately it returns error for me. See:
→ curl -H "Authorization: Bearer $TOKEN" 'https://api.cc.email/v3/contacts/802a35c0-0e19-11e6-b051-d4ae52712b64' -X PUT -H "Content-Type: application/json" -d '{"email_address":{"address":"contact@example.com"},"update_source":"Contact"}' | jq
[
{
"error_key": "contacts.api.bad_request",
"error_message": "Validation failed: State is invalid"
}
]
Error says that "State is invalid". What state? Am I doing something wrong? Or this is some kind of API bug?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @DonaldD14,
We have looked in this internally and there are two things going on with your scenario.
First of all the update_source should be listed as Account. Since this is restoring a deleted contact this needs to be done by the account owner and not the contact themselves. The update_source would be Contact if you were restoring an unsubscribed contact.
The second issue is that there was a problem with the data for that specific contact. This has been updated in our database.
Please let us know if you continue having issues after this.
Regards,
Jimmy D.
Tier II API Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @DonaldD14,
We have looked in this internally and there are two things going on with your scenario.
First of all the update_source should be listed as Account. Since this is restoring a deleted contact this needs to be done by the account owner and not the contact themselves. The update_source would be Contact if you were restoring an unsubscribed contact.
The second issue is that there was a problem with the data for that specific contact. This has been updated in our database.
Please let us know if you continue having issues after this.
Regards,
Jimmy D.
Tier II API Support Engineer
