postman-cs/Postman Onboarding: Service Token

Recommended credential producer for Postman API Onboarding. Mints a service-account access token and team ID in CI.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
postman-api-keyRecommended credential source. Service-account Postman API key (PMAK) used to mint a fresh access token. Required when postman-access-token is not provided.no""
postman-access-tokenCompatibility input for externally rotated Postman access tokens. When provided, minting is skipped, this value is returned via outputs.token, and the action warns because fresh service-account minting is preferred.no""
postman-team-idOptional pre-known Postman team ID. When provided, the team ID lookup is skipped and this value is returned via outputs.team-id. Recommended with postman-access-token pass-through.no""
postman-regionPostman data residency region for public API calls. One of: us or eu. Use the same region as the target Postman team.nous
postman-stackPostman stack profile. Defaults to the public production stack. Marketplace workflows should leave this as prod.noprod
write-github-secretWhen 'true', writes the resolved token and team ID to repo secrets named by access-token-secret-name and team-id-secret-name. Requires github-token to be a PAT (or GitHub App installation token) with secrets write permission on the target repo. The default GITHUB_TOKEN cannot write repo secrets.nofalse
access-token-secret-nameRepo secret name to receive the resolved access token. Used only when write-github-secret is 'true'.noPOSTMAN_ACCESS_TOKEN
team-id-secret-nameRepo secret name to receive the resolved team ID. Used only when write-github-secret is 'true'.noPOSTMAN_TEAM_ID
github-tokenGitHub PAT or App installation token with secrets write permission on the target repo. Required when write-github-secret is 'true'.no""
namedescription
tokenResolved Postman access token. Either minted or passed through from the postman-access-token input.
team-idResolved Postman team ID. Either looked up via /me or passed through from the postman-team-id input.
skipped'true' when minting was skipped because postman-access-token was provided as input.