ItemSearch Deal Endpoint no Longer Accepting Colons

Hey Folks,

I’ve run into an issue with the itemSearch endpoint, looking for a Deal. Specifically, the term property does not accept any values with a : despite being properly encoded.

The use case here is that if a custom field contains a URL, itemSearch is not able to look up that deal. Removing the colon (e.g. http//google.com/api/) does work, though. From our logs, this appears to have popped up in the last day or two.

Is anyone else experiencing the same issue? Was there a backend change that may have broken this endpoint?

Thanks,

J

Hi! Thanks for reporting. This was a regression introduced by a faulty code change and has been rolled back now.