postman-cs/Postman Onboarding: Workspace Bootstrap

Provision a Postman workspace from an OpenAPI spec with generated collections. Part of the Postman API Onboarding suite.

View on GitHub

Trust Signals

Scorecard Score
Scorecard 4–6scored Jun 12, 2026
Maintenance Recency
Activelast commit Jul 10, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: postman-cs/postman-bootstrap-action@6dfc5f3e3a1e0839a694564cd44fab17a25d6dee # v2.9.0

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
workspace-idExisting Postman workspace IDno
spec-idExisting Postman spec IDno
baseline-collection-idExisting baseline collection IDno
smoke-collection-idExisting smoke collection IDno
contract-collection-idExisting contract collection IDno
additional-collections-dirWorkspace-relative directory containing curated Postman v2.1 JSON/YAML files or canonical HTTP collection v3 Local View directories to create or update.no
sync-examplesWhether linked spec/collection relations should enable example syncingnotrue
collection-sync-modeCollection lifecycle policy (refresh or version)norefresh
spec-sync-modeSpec lifecycle policy (update or version)noupdate
release-labelOptional release label used for versioned specs and collectionsno
project-nameService project nameyes
domainBusiness domain for the serviceno
domain-codeWorkspace naming prefixno
governance-groupPostman governance workspace group name. Overrides the postman-governance-group repository custom property and domain mapping.no
requester-emailRequester email for audit contextno
workspace-admin-user-idsComma-separated workspace admin user idsno
workspace-team-idNumeric sub-team ID for org-mode workspace creation. Required when your Postman team is an org with multiple sub-teams. Run the action without this input to see available sub-teams listed in the error output.no
spec-urlHTTPS URL to the OpenAPI document to bootstrap. Provide either spec-url or spec-path.no
spec-pathLocal filesystem path to the OpenAPI document (relative to the workspace). Provide either spec-url or spec-path.no
spec-files-jsonOptional content-free JSON inventory of multi-file definition members from discovery (schemaVersion 1). Empty by default. When set, inventory root must equal spec-path. Cannot be combined with spec-url. Not a directory mode — companions are listed explicitly; file content is never embedded.no""
protocolAPI spec protocol. auto (default) detects from content/extension. openapi flows through Spec Hub; graphql (SDL/introspection), grpc (.proto), and soap (WSDL) build and instrument a Postman collection directly.noauto
protocol-endpoint-urlEndpoint URL/authority used by generated non-OpenAPI requests (e.g. {{baseUrl}}/graphql, grpc://host:port). Supports Postman variable interpolation. Ignored for openapi.no""
openapi-versionOpenAPI specification version override (3.0 or 3.1). When not set, the version is auto-detected from the spec content.no""
preserve-oas30-type-nullOpt-in compatibility mode for OpenAPI 3.0 oneOf schemas that pair one normal schema with a null-only member. The action uploads the original source bytes unchanged and uses an internal nullable true view for validation and generated artifacts. All unrelated validation and lint errors remain enforced.nofalse
breaking-change-modeOpenAPI breaking-change comparison mode (off, pr-native, baseline-only, or previous-spec)nooff
breaking-baseline-spec-pathWorkspace-relative baseline OpenAPI spec path used by baseline-only mode and pr-native fallbackno
breaking-rules-pathWorkspace-relative openapi-changes rules file. Missing files are ignored.nochanges-rules.yaml
breaking-target-refOptional target branch or git ref override for pr-native breaking-change comparisonsno
breaking-summary-pathOptional markdown report output path. Defaults to a runner-temp file.no""
breaking-log-pathOptional raw command log output path. Defaults to a runner-temp file.no""
governance-mapping-jsonLegacy JSON map of business domain to governance group name. Prefer governance-group or the postman-governance-group repository custom property.no{}
github-tokenGitHub token used to read the postman-governance-group repository custom propertyno
gh-fallback-tokenFallback GitHub token used to read repository custom properties when github-token cannotno
postman-api-keyPostman service-account API key used only to preflight the mint credential with GET /me and mint or re-mint the short-lived postman-access-token. It is never used for asset or Postman CLI operations. Optional when postman-access-token is supplied.no
postman-access-tokenPostman service-account access token (x-access-token). Every identity and asset operation runs through the access-token gateway. Optional when postman-api-key is supplied for token minting. CLI/binary usage may instead set POSTMAN_ACCESS_TOKEN.no
credential-preflightAccess-token session preflight policy. warn (default) continues with reactive diagnostics when session identity is unavailable; enforce fails before any workspace is created.nowarn
branch-strategyBranch-aware sync strategy. legacy (default) keeps branch-blind behavior; publish-gate restricts canonical writes to the canonical branch and runs credential-free static validation on other branches; preview additionally maintains suffixed per-branch preview asset sets.nolegacy
canonical-branchExplicit canonical branch (the sole writer of canonical assets). Defaults to the provider-resolved default branch; required on providers without a default-branch variable (Bitbucket, Azure DevOps) when branch-strategy is not legacy.no
channelsComma-separated channel map for long-lived promotion branches, e.g. "develop=DEV, staging=STAGE, release/*=RC". Channel branches maintain prefix-named parallel asset sets and never mutate canonical assets.no
integration-backendAdvanced/internal. Integration backend for managed workspace connectivity; leave unset to use the default.no
folder-strategyFolder organization strategy for generated collections (Paths or Tags)noPaths
nested-folder-hierarchyWhen folder-strategy is Tags, enables nested folder hierarchynofalse
request-name-sourceDetermines how requests are named in generated collections (Fallback or URL)noFallback
postman-regionPostman data residency region for access-token minting and gateway calls.nous
postman-stackPostman stack profile. Leave at the default unless Postman support directs otherwise.noprod
namedescription
workspace-idPostman workspace ID
workspace-urlPostman workspace URL
workspace-namePostman workspace name
spec-idUploaded Postman spec ID
baseline-collection-idBaseline collection ID
smoke-collection-idSmoke collection ID
contract-collection-idContract collection ID
collections-jsonJSON summary of generated collections
lint-summary-jsonJSON summary of validation findings. Bootstrap does not invoke an API-key-authenticated Postman CLI lint.
breaking-change-statusOpenAPI breaking-change check status
breaking-change-summary-jsonJSON summary of the OpenAPI breaking-change check
sync-statusBranch-aware sync status: synced, skipped-branch-gate, or empty under branch-strategy legacy.
branch-decisionSerialized BranchDecision JSON for downstream actions (also exported as POSTMAN_BRANCH_DECISION).
spec-version-tagNative Spec Hub version tag applied on this canonical publish (tag-per-publish), empty when tagging was skipped (no-op sync, non-canonical run, or legacy client).
spec-version-urlReserved for the repo-sync finalizer; bootstrap does not tag before complete onboarding.
spec-content-changedWhether bootstrap changed canonical spec content; repo-sync uses this to skip native version tags on no-op syncs.