Document the Preview auth_tokens read endpoints - #667
Merged
robertlangner-fin merged 4 commits intoSep 16, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Token ids are serialised as strings in the response, and the sibling connector endpoints already declare their path id as a string. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
App package and integration credentials are included, not excluded. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
The previous wording said app package and integration credentials are included. The adapter reverted to with_app_package_tokens: false, so they are not. The wording before that was also wrong in the other direction: it said no integration credentials are listed, but the allowlist covers Calendly, HubSpot Meetings and Marketo. Describes what the filter actually does instead of enumerating a set that changes. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
anubhav-intercom
approved these changes
Sep 16, 2026
anubhav-intercom
left a comment
Contributor
There was a problem hiding this comment.
Approve. The `auth_token` schema exposes exactly the adapter's 8 metadata fields plus `type` — no secret, token_prefix, refresh, or OAuth field — and both endpoint descriptions accurately state the read-only `read_auth_tokens` scope, the list filter (teammate + some listed integrations; app-package/most-integrations/MCP-minted excluded), and 404-for-unlisted. Lands in `descriptions/0` (the working source, not a frozen version). per_page default 20 / min 1 / max 50 matches the controller's clamp. Direct review.
robertlangner-fin
deleted the
robert.langner/559165-auth-tokens-preview
branch
September 16, 2026 10:03
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?
Setting up a data connector through the API needs the id of a stored credential, and there is no documented way to find one. That leaves integrators stuck partway through the setup.
How?
Documents two read-only endpoints — one listing credential metadata, one retrieving a single record — in the Preview version only.
Notes for reviewers
fern checkwas not run locally — fern is not installed on this machine, so CI is the first validation. The file parses as YAML and the new$refs resolve.Generated with Claude Code