hubspot-known-pitfalls

# HubSpot Known Pitfalls ## Overview Ten real-world HubSpot API anti-patterns with correct alternatives, covering authentication, rate limits, search, associations, and data handling. ## Prerequisites - Access to HubSpot integration codebase - Understanding of HubSpot CRM v3 API ## Instructions ### Pitfall 1: Using Deprecated API Keys ```typescript // BAD: API keys were deprecated in 2022 and removed from SDK v10+ const client = new hubspot.Client({ apiKey: 'your-api-key' }); // REMOVED // GOOD: Use private app access token const client = new hubspot.Client({ accessToken: process.env.HUBSPOT_ACCESS_TOKEN!, // pat-na1-xxxxx numberOfApiCallRetries: 3, }); ``` --- ### Pitfall 2: Not Using Batch Operations ```typescript // BAD: N API calls to read N contacts (hits rate limit fast) for (const id of contactIds) { const contact = await client.crm.contacts.basicApi.getById(id, ['email']); // 100 contacts = 100 API calls } // GOOD: 1 API call for up to 100 contacts const batch = await client.crm.contacts.batchApi.read({ inputs: contactIds.map(id => ({ id })), properties: ['email', 'firstname'], propertiesWithHistory: [], }); // 100 contacts = 1 API call ``` --- ### Pitfall 3: Ignoring Search Limits ```typescript // BAD: Search API has a hard limit of 10,000 results total // You cannot page past this limit with `after` const allResults = []; let after = 0; do { const page = await client.crm.contacts.searchApi.doSearch({ filterGroups: [], properties: [...