feat: Add API-key installation support to Pipes#1649
Merged
Conversation
dandorman
approved these changes
Jun 30, 2026
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
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
oagen).updateDataIntegrationApiKey()— upserts an API-key installation for an integration/user viaPUT /data-integrations/{slug}/api-key, rotating the stored key if one already exists.createDataIntegrationCredential()— vends credentials for a connected account viaPOST /data-integrations/{slug}/credentials, branching on the installation'sauth_method(OAuth returns a refreshed access token; API-key returns the stored secret).auth_methodon connected accounts and provider list entries, with supporting credential/error interfaces and serializers.getAccessToken()to takeGetAccessTokenOptionsdirectly (renameget-access-token.interface→get-access-token-options.interface) and document the new 422 response.pipes.spec.tsto cover the new endpoints.Test plan
npm test -- src/pipes/pipes.spec.tspassesnpm run build/ typecheck succeeds with the regenerated interfaces