CRED-2148: Add PAT auth support to TypeScript API client#3588
Closed
CRED-2148: Add PAT auth support to TypeScript API client#3588
Conversation
This was referenced Mar 4, 2026
tausman
force-pushed
the
tausman/cred-2148-typescript-pat-auth
branch
from
d96f349 to
e98992e
Compare
tausman
changed the title
tausman
force-pushed
the
tausman/cred-2148-typescript-pat-auth
branch
3 times, most recently
from
ea09b2b to
d14ed67
Compare
tausman
force-pushed
the
tausman/cred-2148-typescript-pat-auth
branch
from
2d798e4 to
ed16242
Compare
Author
|
Closing: PATs work via the existing OAuth (AuthZ) code path -- no new changes needed. See test_program.ts. |
5 tasks
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.
PR Stack
API Client Libraries (closed)
All client libraries except Rust already support PATs via the existing OAuth/AuthZ code path. No new changes were needed.
Go: CRED-2147: Add PAT auth support to Go API client datadog-api-client-go#3764 — CRED-2147— PATs work via existing OAuth code pathPython: CRED-2146: Add PAT auth support to Python API client datadog-api-client-python#3243 — CRED-2146— PATs work via existing OAuth code pathTypeScript: CRED-2148: Add PAT auth support to TypeScript API client #3588 — CRED-2148— PATs work via existing OAuth code pathTypeScript v2: CRED-2148: Add PAT auth support to TypeScript v2 API client #3610 — CRED-2148— PATs work via existing OAuth code pathJava: CRED-2149: Add PAT auth support to Java API client datadog-api-client-java#3555 — CRED-2149— PATs work via existing OAuth code pathRuby: CRED-2151: Add PAT auth support to Ruby API client datadog-api-client-ruby#3058 — CRED-2151— PATs work via existing OAuth code pathRust: The Rust client generator does not support OAuth/AuthZ, so PATs cannot be used through the client library today. When OAuth/AuthZ support is added to the Rust generator in the future (#1438 has the approach), PATs will work automatically.
OpenAPI Spec Changes
Closing Note
This PR is being closed. PATs can be passed in using the existing OAuth (AuthZ) code path -- no new client library changes are needed. See the test program demonstrating this: