Document the Preview auth token write endpoints - #670
Merged
robertlangner-fin merged 3 commits intoSep 21, 2026
Merged
Conversation
Adds POST /auth_tokens and PATCH /auth_tokens/{id} to the Preview spec,
alongside the read endpoints already documented there, with request schemas
for each and the error responses they can return.
Also corrects the token_type example on the auth_token schema: the API returns
"text", not "header".
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
token_prefix is now returned by every auth token operation and accepted when updating one. Also corrects two response examples that showed a token_type of header, which is not a value these endpoints return. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
robertlangner-fin
marked this pull request as ready for review
September 21, 2026 09:59
The four operations referenced the unrestricted intercom_version schema, so generated clients offered released versions that do not expose them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
anubhav-intercom
approved these changes
Sep 21, 2026
anubhav-intercom
left a comment
anubhav-intercom
left a comment
Contributor
There was a problem hiding this comment.
Approving — the spec matches the code contract in intercom/intercom#578721 (required create fields, all-optional PATCH with no token_value, and the 400/401/403/404 set), and the token_type header→text example fix is right.
Ordering: merge after intercom/intercom#578721 ships so the spec doesn't describe endpoints that still 404.
robertlangner-fin
deleted the
robert.langner/auth-tokens-write-endpoints
branch
September 21, 2026 14:49
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?
The Preview auth tokens reference only documents reading, so a developer setting up a data connector has no documented way to store a credential over the API.
How?
Adds the create and update operations with their request bodies and error responses, widens the Auth Tokens tag description to cover writing and its limits, and fixes a wrong example value on the existing read response.
Generated with Claude Code