Urgent: Domain change needed for Cicero (address verification provider for NPSP)

[rebeccawomack]

The Cicero API, which is one of three address verification options for NPSP users, has a new domain. All references to cicero.azavea.com should be changed to app.cicerodata.com. Until then, we won't be able to complete our transition to a new domain.

Here's a search that shows all the occurrences.

Thanks for your attention.

[rebeccawomack]

@jstvz or @ceiroa Could you give a sense of how long it might take to get to this? It's really urgent for us. Thanks for your help.

[force2b]

Thank you for the heads up on this @rebeccawomack.

Looking at Cicero's API documentation, it defines their endpoint as "https://cicero.azavea.com/v3.1".

If you are from Cicero and have other documentation with a different endpoint, can you provide links so that we're sure NPSP implements the correct endpoint?

[rebeccawomack]

@force2b Could you try checking again? All links should show the new domain, as does the API documentation.

[force2b]

Honestly, the two docs are identical with the exception of the endpoint. Based on that, it's hard to know if the current URL is valid or not. If we're going to change the URL in our product, it's important that we have clear documentation and support from that vendor stating the correct API Endpoint so we don't break customers (understanding that maybe it's broken now).

Right now, their docs are ambiguous enough to indicate what we have should still work. However, I see your point. We just need to have something definitive from them with the right endpoint. If they've have deprecated the old endpoint, it's odd that it's still the endpoint that comes up in a google search.

• https://app.cicerodata.com/docs/#root-url
• https://cicero.azavea.com/docs/

[rebeccawomack]

Hi Mike. I just emailed you from my @cicerodata.com email with this same message:

I'm emailing you from my cicerodata.com email since I realize from my GitHub profile that it's not clear I'm the Cicero Product Manager and therefore able to serve as an authoritative source on what the "real" Cicero API endpoint should be.

Until the NPSP code is updated to reflect the new domain, NPSP/Cicero integration users will be getting error messages and not be able to access the API. We thought we could avoid this in the shorterm with a redirect, but the Salesforce integration doesn't follow redirects.

Our home page has been cicerodata.com and the azavea.com app domain has been an anachronism for a long time, so we're transitioning to a more unified setup without a lot of fanfare.

Thanks for your help.

[force2b]

Thank you for the additional confirmations @rebeccawomack. We'll look into this to determine when an update can be delivered.

[rebeccawomack]

Hello @force2b, @jstvz and @ceiroa. I'm writing to check in on the status of this issue since it has been nearly 2 months without an update. Could you let me know what's going on and what, if anything, you need from the Cicero team? Thank you.