Skip to content

Warn that data connector header values are logged unmasked - #770

Merged
yasser-aboelgheit-intercom merged 1 commit into
mainfrom
docs/data-connector-headers-unmasked
Oct 26, 2026
Merged

yasser-aboelgheit-intercom merged 1 commit into
mainfrom
docs/data-connector-headers-unmasked

Conversation

@yasser-aboelgheit-intercom

Copy link
Copy Markdown
Contributor

Why?

Data connector execution logs record request headers, and only Authorization is always masked, so other headers you set yourself, such as a static x-api-key, appear unmasked in the logs. The headers description didn't say this, so nothing pointed developers to token_ids for credentials.

How?

The headers description on the create and update data connector requests in 2.16, 2.17 and Preview now carries that warning, with a link to Create an auth token in Preview only, since Auth Tokens is Preview-only. The same change is being made to the developer docs.

Generated with Claude Code

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) <noreply@anthropic.com>
@yasser-aboelgheit-intercom
yasser-aboelgheit-intercom merged commit 00d3079 into main Oct 26, 2026
4 checks passed
@yasser-aboelgheit-intercom
yasser-aboelgheit-intercom deleted the docs/data-connector-headers-unmasked branch October 26, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants