Jan concludes that the /crm/v3/properties/{objectType} endpoint must be used to fetch all available properties, as there's no comprehensive list in the docs.
Dennis Edson relays team feedback that recent cache invalidations may cause slowdowns, advises submitting specific examples.
Muhammad explains that two API calls are needed: one for the custom object and another for associated deals. Later, Joe Conery advises handling pagination using the 'after' parameter.
Muhammad mentions that notes can be exported via API, but comments cannot be retrieved. Exporting notes is possible, but comments are not supported.
Muhammad suggests formatting hs_additional_emails as a semicolon-separated string in the request body.
Muhammad advises rotating private apps and implementing exponential backoff for retries.
The crm_associations parameters were likely reversed. Correct usage requires the FROM object ID (contact) first, not the custom object ID. Association definition shows FROMOBJECTTYPEID=0-1 (contact), TOOBJECTTYPEID=2-14785969 (custom object).
Creating a custom blog template mimicking KB functionality instead of modifying restricted KB templates.
Muhammad suggests exporting, updating data, and re-importing via workflows or API if unavailable.
Muhammad and Federico Mozzo advised using human-readable module instance names instead of auto-generated IDs to avoid conflicts.
Muhammad points to the Engagements API for adding call/meeting data, though it doesn't fully address CI integration.
Muhammad confirms it’s possible using webhooks, HubSpot APIs, and Private Apps for authentication without complex permissions.
Jon McLaren advises adhering to trademark laws and avoiding names implying official affiliation unless authorized.
Muhammad confirms the API doesn't support narration audio and suggests checking if the file is publicly accessible on the blog page.
SJ Morris directs to the HubSpot Dev Forum or feedback channels, as the Slack isn't monitored by HubSpot staff.
Robert explains that the `context` parameter must be included in the Forms API submission payload. This should contain values like `hutk` (from the 'hubspotutk' cookie), `pageUri`, and `pageName` to ensure proper tracking and contact association. A link to documentation and a tutorial Gist are provided.
Tanya Scales confirmed the issue was due to Zscaler blocking CLI requests. Disabling Zscaler resolved the problem.
No solution provided in the thread. Implied need to verify eventType handling or API logic alignment with HubSpot's event tracking.
Ryan Huff suggests using the Tax object API to attach taxes similarly to line items.
Justin Givens recommends using the GraphQL API to fetch line item details efficiently.