Community - am I going crazy, or did the Associations Schema end points all just change their definitions?
I don’t seem to see the definitions of the API’s I’m currenty using successfully…
Steve
Community - am I going crazy, or did the Associations Schema end points all just change their definitions?
I don’t seem to see the definitions of the API’s I’m currenty using successfully…
Steve
@Jaycee_Lewis - There seems to be no impact on the APIs I’m actually actively using- although they seem now to be undocumented. but I’m kind of shocked that such an significant API definition update would be made without formal annoucement. Thats why I’m doubting myself (and noboby else has commented).
Steve
@Jaycee_Lewis - I can now be pretty sure that these new API definitions do not in fact work correctly.
Example:
https://api.hubapi.com/crm/v4/associations/definitions/configurations/contact/company
returns:
HTTP 200
{
"results": []
}
Which is clearly nonsense.
The prior defined call to get the schema was/is:
https://api.hubapi.com/crm/v4/associations/{FromObjectType}/{ToObjctType}/labels
And this still works fine to return the pre-defined association - plus any custme definitions.
Who do we appeal to on this??
Steve