Oh, I feel this! I tried using it to build a quick lead scoring snippet for HubSpot last month. It gave me the API call to fetch contacts perfectly, but then used a property name that changed in their last API version. The call worked, but it returned an empty list for the score tier because the field was wrong. No error, just no data.
I guess the trick is to always have the actual API docs open side-by-side for any integration, even for "simple" stuff. Saved me from sending a campaign to the wrong segment!
Oh that silent failure with CRM property names is the absolute worst. I had the same thing happen with Salesforce's REST API last quarter, building a data sync for our sales dashboards.
It generated the SOQL query to pull Opportunity data, but used the old "Amount" field API name. We'd switched to using a custom "Total_Amount__c" field months ago. The query ran perfectly, returned all the records... and every single "Amount" value was null. Took me an hour to realize the data wasn't missing, it was just in the wrong column.
You're spot on about the docs. I've started keeping a browser tab pinned for each platform's object reference. It's tedious, but it's cheaper than a botched campaign or a board report with empty graphs. Maybe we need AI that can read the changelog first?