Sporadic server-side check for "foreign-key" consistency


When I create a new blog post via API I can specify a blog_author_id. I would expect the server to reject an id that doesn’t correspond to an id returned by the Get blog authors endpoint. I know that HubSpot enforces this type of quasi-foreign key constraint for other fields, but not for this one. Are there plans to include this kind of functionality later? What is the reasoning behind this kind of sporadic enforcement?


@Adam Thanks for pointing that out, I’ll notify the owner of that endpoint.



Hi @seb_fairchild,

I noticed similar issues with ownerId for Calendar Events, contentId in BlogComments, and generatedFromLayoutId in Templates.