/api/v1) and evolves additively only:
fields are added, never renamed, retyped, or removed. Optional request
parameters (like view) never change the
schema of a response — they fill or null optional fields.
Treat open vocabularies as open: deal statuses, for example, include the
system set plus any custom statuses your org defines.
Every change ships with a changelog entry, and the
generated API Reference always reflects the deployed service.