500 Internal Server Error when updating contact using REST

API Q&A
#1

Hi there,

I’m trying to make a PATCH request to update a contact and I get {“message”:“General error”} with http response-code 500. See this (removed as it contained an access token).

https://api.infusionsoft.com/crm/rest/v1/contacts/206653?access_token=XXX
{“given_name”:“akiko”,“family_name”:“tanaka”,“owner_id”:1,“email_addresses”:[{“email”:“ari_akiko@hotmail.com”,“field”:“EMAIL1”}],“addresses”:[{“zip_code”:“3107”,“country_code”:“AUS”,“field”:“BILLING”}]}

Could you please let me know what is the wrong here?
Many thanks.

#2

Hi guys, I found another way to update the contact, using PUT instead of PATCH and it works. Hope this will help.

https://developer.infusionsoft.com/docs/rest/#!/Contact/createOrUpdateContactUsingPUT

#3

Hi @Dev3_SIMB1, this appears to have been caused by a recent code change on our end and we are looking into a fix. Thanks for bringing it to our attention!

#4

Hi @Nicholas_Trecina Is there any update on this issue ?
I had the same problem and do you have any estimation of the patch release date ?

#5

Hi @Nicholas_Trecina, can you please provide an update on this?

#6

Hi @Nicholas_Trecina, can you update us on when this issue will be solved?

My client is losing leads because of this bug.

Thanks!

#7

@Nicholas_Trecina, can you please let us know what time estimate to expect for the problem to be solved? We are a lot of people waiting, and our businesses are put on a hold because of this.

#8

The fix will be deployed to all customers over the course of today and tomorrow and by Wednesday it will deployed to everyone.

#9

Hi @Nicholas_Trecina

To prevent this kind of incident, do you have any automated continuous integration testing system for each API endpoints before launching the system ? For example like Jenkins or Bamboo to perform CI unit testing and functional testing ?

If you don’t, I’m happy to assist and write something like that to test your API system prior your production launch. :grinning:

#10

Hi @Nicholas_Trecina. Can you tell us from which date you did this code change?

#11

The bug was introduced into production between February 20th and 21st, depending on what release group your app is part of.

#12

Hi @Nicholas_Trecina. What’s the status, -has it been fixed yet?

#13

Yes the fix has been deployed to all customers.

#14

@Nicholas_Trecina. thank you.