Add X-Pplx-Integration attribution header - #92
Closed
qirh wants to merge 1 commit into
Closed
Conversation
qirh
marked this pull request as ready for review
August 24, 2026 21:28
Contributor
Author
|
Superseded by #93. |
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
1 participant
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.
Summary
Perplexity logs this opt-in header at API ingress for integration attribution. This adds the following default SDK header:
X-Pplx-Integration: perplexity-node/<version>The value is well below the server-side 512-character cap. Caller-supplied headers retain precedence, and this introduces no behavior change beyond attribution metadata.
Verification
bazel test //:test //:package_checks //e2e:sdk_parity(5 of 6 targets passed;//:attwcould not runnpm packin the local Bazel sandbox)bazel build //:pkgpnpm lefthook run pre-commit --all-files --force --fail-on-changes