CRM Extensions API - Response deserialization error

SOLVE
Highlighted
Occasional Contributor

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!

 

 

{
    "results": [
        {
            "objectId": 7070707,
            "title": "Service",
            "properties": [
                {
                    "label": "Price",
                    "value": 98.00,
                    "dataType": "CURRENCY",
                    "currencyCode": "USD"
                },
                {
                    "label": "Auto Renewal",
                    "value": "True",
                    "dataType": "STRING"
                },
                {
                    "label": "Refund Status",
                    "value": "Past MBG",
                    "dataType": "STRING"
                },
                {
                    "label": "Start Date",
                    "value": "2019-02-18",
                    "dataType": "DATE"
                },
                {
                    "label": "End Date",
                    "value": "2021-02-18",
                    "dataType": "DATE"
                }
            ]
        }
    ],
    "totalCount": 1
}

 

 

Reply
0 Upvotes
1 Accepted solution

Accepted Solutions
Highlighted
HubSpot Moderator

Hey @mfwmtech,

 

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?

Reply
0 Upvotes
6 Replies 6
Highlighted
HubSpot Moderator

Hey @mfwmtech,

 

I was able to see that the following:

 

{
"results" : [
{
"objectId" : 1,
"title" : "TEST TITLE",
"properties" : [
{
"label" : "Price",
"value" : 98,
"dataType" : "CURRENCY",
"currencyCode" : "USD"
},
{
"label" : "Auto Renewal",
"value" : "True",
"dataType" : "STRING"
},
{
"label" : "Refund Status",
"value" : "Past MBG",
"dataType" : "STRING"
},
{
"label" : "Start Date",
"value" : "2019-02-18",
"dataType" : "DATE"
},
{
"label" : "End Date",
"value" : "2021-02-18",
"dataType" : "DATE"
}
]
}
],
"totalCount" : 1
}

works fine for me. In order for me to further troubleshoot this, do you mind sharing the following with me:

 

1. The app ID

2. The portal ID that has the app installed

Reply
0 Upvotes
Highlighted
Occasional Contributor

Hi Wendy! 

 

Thanks for your quick response. Below is the information you requested. Thanks!

 

1. The app ID : 216037

2. The portal ID that has the app installed  6069836

 

Also our developer portal id is: 7050004

Reply
0 Upvotes
Highlighted
HubSpot Moderator

Hey @mfwmtech,

 

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?

Reply
0 Upvotes
Highlighted
Occasional Contributor

Hi @WendyGoh 

 

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?

 

Thanks!

Reply
0 Upvotes
Highlighted
HubSpot Moderator

Hey @mfwmtech,

 

Currently, while there isn't a way to whitelist the data fetch url, you can however whitelist your action URLs under the 'Custom actions' tab:

customActions.png

Reply
0 Upvotes
Highlighted
Occasional Contributor

No problem! We were able to use the `X-Hubspot-Signature` instead! Thanks for your help!