CRM Extensions API - Response deserialization error
SOLVE
Hello! We had a CRM Card that worked until last Friday. The extension still works when pointed to a lower environment we have. On our production environment we get a "Response deserialization error". The json payloads between environments and they are identical. We believe this might be issue with how our production environment is configured. Could we get more information as to what is causing the deserailization error? Below is a copy of the json payload we return. Thanks for your help!
When I took a look at the data fetch url for the member services card, I noticed that when I attempt to access the url, it redirects me to the root domain of the page.
I believe this is likely the caused of the deserialization error. HubSpot will send a data fetch request and the request should return the card properties associated with the current CRM object.
Could you ensure that there's no redirect set up on the data fetch url and see if it works?
When I took a look at the data fetch url for the member services card, I noticed that when I attempt to access the url, it redirects me to the root domain of the page.
I believe this is likely the caused of the deserialization error. HubSpot will send a data fetch request and the request should return the card properties associated with the current CRM object.
Could you ensure that there's no redirect set up on the data fetch url and see if it works?
Good catch! Our API endpoints are behind a private firewall, which is not contained in applicaiton code but our infrastructure. Is there a way we could get a Hubspot's IP Address to whitelist?