Hightouch destination, source, and model configuration capabilities. Generated from Hightouch's hash-locked official OpenAPI 3.0.0 document (ee840baa9cab…) and its separately hash-locked API-guide section. This leaf carries 12 of the suite's 38 current admitted operations at https://api.hightouch.com/api/v1; the one explicitly deprecated identity-graph trigger alias is inventoried but excluded in favor of its documented replacement. Calls use an Admin-created Hightouch API key only through the trusted bearer connection adapter. Required and optional JSON bodies retain the official distinction and use bounded body_raw payloads. Documented limit/offset collections paginate automatically at their official default page sizes; response integers remain exact strings, reads are uncached and not approval-gated, and every mutation requires approval. Provider failures receive no hidden retries. No reverse-ETL control-plane object is misrepresented as a task, note, or user-work project Source.