Skip to content

docs(integration): document masked secrets in integration responses - #1067

Merged
ysyneu merged 2 commits into
mainfrom
feat/integration-secrets-masked
Oct 16, 2026
Merged

ysyneu merged 2 commits into
mainfrom
feat/integration-secrets-masked

Conversation

@ysyneu

@ysyneu ysyneu commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

What

  • API reference (openapi.{en,zh}.json, on-call.openapi.{en,zh}.json) and the API catalog: integration list, detail and update responses return each saved secret in settings as ******. The integration key is returned as is.
  • DingTalk guide (zh/en): the event subscription aes_key and token are shown only once, when they are generated. If they were not kept, generate them again from the integration edit page. After saving, the old values stop working and the new ones must be entered in DingTalk and in the group bot.

Includes #1066.

Integration list, detail and update responses return each saved secret
in settings as ******. Updates keep a stored secret only while its
destination is unchanged. The DingTalk event subscription aes_key and
token are shown once when generated and can be generated again from the
edit page.
…asked

docs(integration): document masked secrets in integration responses
@ysyneu
ysyneu merged commit 40aed14 into main Oct 16, 2026
2 checks passed
@ysyneu
ysyneu deleted the feat/integration-secrets-masked branch October 16, 2026 20:06
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.

1 participant