Hi! I have a question about which to rely on in the API v2.9 Models documentation: the example JSON object, or the documented fields / field datatypes. In some cases the inconsistencies can be significant. For example, in looking at https://developers.intercom.com/intercom-api-reference/reference/the-contact-model I can see the following differences:
- Documentation does not include the external_id field from the example JSON.
- Documentation lists avatar as having type object but in the example object it has type string.
- Documentation does not include the opted_out_subscription_types field from the example JSON.
- Documentation does not include the opted_in_subscription_types field from the example JSON.
- Documentation does not include the utm_campaign field from the example JSON.
- Documentation does not include the utm_content field from the example JSON.
- Documentation does not include the utm_medium field from the example JSON.
- Documentation does not include the utm_source field from the example JSON.
- Documentation does not include the utm_term field from the example JSON.
- Documentation does not include the referrer field from the example JSON.
- Example JSON does not include the formatted_phone field from the documentation.
At the very least it would be good for the site / documentation team to fix these inconsistencies; but in the meantime, I’d love to know which is accurate - JSON or documentation table - and whether that’s true not just for the Contact model but other models as well. (The Contact model doc is the most egregious case of this, but there are a few difference on other pages too.)
Thank you very much in advance for the help!