Home › Forums › Support - Ask questions of your peers (and the Constant Contact Team)

Another reason for a 409 on a PUT

Thu, 08/13/2009 - 15:44 — lgrening

The list of HTTP codes and possible reasons at http://developer.constantcontact.com/doc/errorCodes doesn't list a reason for a 409 on a PUT.
I just got a 409 on a PUT where the Updated date/time was earlier than the contact's Last Update date/time.  Could these date/times be the reason for the 409?  If so, could this reason be added to http://developer.constantcontact.com/doc/errorCodes?  Are there other reasons for a 409 on a PUT?
Now, my contact's Last Update date/time is today at 10pm :-).  I've been testing new code (on my personal contact) and I had the Updated date/time in the wrong timezone (fixed now).  However, *every* PUT I've executed today has received a 400 (for many good reasons).  Why would these failed PUTs have changed the contact's Last Updated date/time?
  --Lars

‹ Email Reminders API Support ›
Thu, 08/13/2009 - 16:02 — lgrening

Whoops! Bad <id>!

I'd mistyped a variable's name and the <id> value was bad.  Now *that* I can see causing a 409. :-)
  --Lars

—

Lars Greninger
Hero Arts development

Thu, 08/13/2009 - 16:19 — lgrening

Well, all is good

Having fixed the bad <id> I now get a HTTP 204 *and* the contact's Last Updated timestamp changed from 8/13/2009 10:17pm to 8/13/2009 4:14pm, the actualy date/time that the 204 response was returned.  So it looks like no checking is done against the Last Update timestamp.  Whatever the latest update gave as a date/time is the new Last Updated timestamp.
Sure feels good getting that 204 finally! :-)
  --Lars

—

Lars Greninger
Hero Arts development

Fri, 08/14/2009 - 11:34 — dberard

Hi Lars,   There is no

Hi Lars,
 
There is no checking of the Last Update Timestamp value you send us, we automatically update that for you when the update is actually processed.  There are a few 409 conflict messages you can receive such as incorrect ID field, changing email to an address associated with another contact already (we require email addresses to be unique to each contact) and other fields not matching correctly (such as state code and country code not matching).
 
We are looking into our response messaging to better assist with why you are receiving a message.  Hopefully we'll have an update soon that will make this process easier.

—

Dave B Support Engineer, Constant Contact