From b66267d21f2447e47f06bf5e0fa271abc01fb0c1 Mon Sep 17 00:00:00 2001 From: yasser-aboelgheit-intercom Date: Mon, 26 Oct 2026 12:04:19 +0000 Subject: [PATCH] Warn that data connector header values are logged unmasked The `headers` field on the create and update data connector requests now says that header values are recorded unmasked in execution logs (except `Authorization`) and points to `token_ids` for credentials. Applies to 2.16, 2.17 and Preview. Co-Authored-By: Claude Opus 5.5 (1M context) --- descriptions/0/api.intercom.io.yaml | 6 ++++-- descriptions/2.16/api.intercom.io.yaml | 6 ++++-- descriptions/2.17/api.intercom.io.yaml | 6 ++++-- 3 files changed, 12 insertions(+), 6 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 981954af..4d125399 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -44629,7 +44629,8 @@ components: - visitors headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach a stored credential with `token_ids` instead (see [Create an auth token](/docs/references/preview/rest-api/api.intercom.io/auth-tokens/createauthtoken)). Its value is stored encrypted, masked in execution logs, and never returned. items: type: object properties: @@ -44807,7 +44808,8 @@ components: - users headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach a stored credential with `token_ids` instead (see [Create an auth token](/docs/references/preview/rest-api/api.intercom.io/auth-tokens/createauthtoken)). Its value is stored encrypted, masked in execution logs, and never returned. items: type: object properties: diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 15ee25a2..bdffed86 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -30668,7 +30668,8 @@ components: - visitors headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs. items: type: object properties: @@ -30794,7 +30795,8 @@ components: - users headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs. items: type: object properties: diff --git a/descriptions/2.17/api.intercom.io.yaml b/descriptions/2.17/api.intercom.io.yaml index 65903e1e..363f1e1e 100644 --- a/descriptions/2.17/api.intercom.io.yaml +++ b/descriptions/2.17/api.intercom.io.yaml @@ -39366,7 +39366,8 @@ components: - visitors headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs. items: type: object properties: @@ -39506,7 +39507,8 @@ components: - users headers: type: array - description: HTTP headers to include in the request. + description: | + HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs. items: type: object properties: