Add Contact code that has been working for 11 months started getting back ‘400 Bad Request’ with message “Unrecognized property: email_opted_in”. This began happening at about 8:12 PM PDT last night (April 2, 2018) I’m using the library from GitHub - infusionsoft/infusionsoft-php: PHP client librar…

I should also note that the Contact actually is created, even though an Exception/400 Bad Request is returned.

I am curious what the answer to this is as the same thing happened to us last night. I can tell you that we had to remove the email_opt_in property and instead use “opt_in_reason” and supply a reason. ex: “opt_in_reason:Contact gave explicit permission”. After making this change, our new contacts…

We never make it to the opt-in reason portion. In our code, we call: $infusionsoft_contact = $this->infusionsoft_obj->contacts()->create($contact); which works properly, then we call $contact_save_result = $infusionsoft_contact->save(); at which point the Exception is thrown. Without looking at…

Our order of operations is normally Create, Save, Update Opt-In Reason. I was hopeful that adding the opt-in reason to the Contact on initial creation would get around this issue, but the “Unrecognized property: email_opted_in” Exception is still thrown. Using this method (setting the opt-in reaso…

So if I’m understanding, you’re saying that it’s “working” functionally but is still throwing the error message?

It is “working”, yes, in the sense that the Contact is created, but once the Infusionsoft API library returns an Exception upon the attempted Contact creation, our code bails out, and does not run the Action Set that is supposed to be run for the newly created Contact, so for us, it is definitely br…

[image] "Unrecognized property" updating contacts API Q&A With yesterday’s release, the API Team made an improvement to the REST API documentation for the Contact resource. The Contact resource body samples now accurately indicate which properties are available for each re…

Thanks for letting us know, Mike. This generally sounds like what is happening to me, however, as far as I can tell, neither I nor the Infusionsoft PHP API Library is sending email_opted_in during Contact creation, yet I’m seeing an error as if it were sent (according to your explanation). I’m hope…

I take this back, after my call to the Infusionsoft PHP API Library, $infusionsoft_contact = $this->infusionsoft_obj->contacts()->create($contact); , [email_opted_in] => 1 is set in the returned object. Looking into how this happens.

I understand what is happening now. My code looks like this: $infusionsoft_contact = $this->infusionsoft_obj->contacts()->create($contact); $contact_save_result = $infusionsoft_contact->save(); The call to ->save() is redundant; $this->save() is called within ->create(). ->create() returns what t…

Adding Contact, returns 400 Bad Request, "Unrecognized property: email_opted_in"

API Q&A

mike.christianson (Mike Christianson) April 3, 2018, 6:17pm 8

Topic		Replies	Views
Problem Opting in New Contact through API API Q&A opt-in	5	1045	October 12, 2018
V2 Rest API Add Contact 400 Bad Request API Q&A	8	1019	June 2, 2022
Cannot Create A New Contact API Q&A	17	2347	May 17, 2018
Enable the option I have permission to send marketing to this address API Q&A	4	1713	July 10, 2017
Error when create contact with PHP SDK Max Classic api , php-sdk	0	456	January 8, 2021

Adding Contact, returns 400 Bad Request, "Unrecognized property: email_opted_in"

Related topics