Add Identity Verification Secret rotation API - #475
Open
thibault-intercom wants to merge 1 commit into
Open
Conversation
Documents the new public V3 endpoints for self-served rotation of
Messenger Identity Verification secrets:
- GET /secure_mode_secrets — list metadata (no signing material)
- POST /secure_mode_secrets — create; secret returned ONCE
- DELETE /secure_mode_secrets/{id} — soft-delete (rotation out)
The create response includes the raw 256-bit HMAC secret; the list and
delete responses do not. This write-once pattern mirrors AWS IAM access
keys and GitHub fine-grained PATs.
Companion to:
- intercom/intercom#500245
- intercom/intercom#500247
- intercom/intercom#500250
eredi93
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Moon Active's 2025 security agreement with Intercom calls for self-served rotation of Messenger Identity Verification secrets via API. This spec documents the three new public endpoints that make that possible.
How?
Three endpoints plus supporting schemas and a new `Identity Verification Secrets` tag. The raw HMAC signing material is only returned from `POST /secure_mode_secrets` — list and delete responses contain metadata only. This write-once posture mirrors AWS IAM keys and GitHub fine-grained PATs.
Companion to:
Generated with Claude Code