Correct the Intercom-Version value advertised for the Preview version - #669
Merged
laszlobogacsi-intercom merged 1 commit intoSep 18, 2026
Merged
Conversation
The shared Preview header schema set its example, default and only enum value to `preview`, and the granted companies descriptions repeated it in prose. The version lookup matches the id exactly, so a lowercase value is rejected with a 400. The sibling `intercom_version` schema already uses the capitalised form. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
laszlobogacsi-intercom
enabled auto-merge (squash)
September 18, 2026 09:36
Apexinsideapex
approved these changes
Sep 18, 2026
laszlobogacsi-intercom
deleted the
laszlobogacsi/fix-preview-header-case-578238
branch
September 18, 2026 09:41
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 API version is only accepted as
Preview. The spec advertised it in lowercase, so anyone copying the documented header value got a 400 back instead of a response.How?
Capitalises the value in the shared Preview header schema and in the endpoint descriptions that spelled it out, matching the form the general version schema already uses.
Generated with Claude Code