> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt. # Troubleshoot SDK errors in Postman The [SDK commands](/docs/postman-cli/postman-cli-sdk-gen/) in the Postman CLI can emit errors and warnings based on their current implementations under `lib/commands/sdk/*` and related services. The following sections are organized by command and cross-functional concerns: * `postman sdk generate` * `postman sdk list` * `postman sdk get`,`postman sdk fetch`, and `postman sdk download` * `postman sdk connect` * Shared build, artifact, filesystem, configuration, language, and HTTP-status handling. All SDK subcommands share the same authentication mechanism. When no API key or access token is available, they surface a common *no authorization data* error. ## Common authentication and authorization errors These apply to all SDK subcommands that wrap `postmanUtil.addApiKeyToOptions` or `withAuthentication` and to some helper flows (`identifyIdType`, `validateCollection`, workspace lookups, and the SDK generator API). ### Missing CLI authentication The source of this message is: * `ERROR_MESSAGES.NO_AUTHORIZATION_DATA_WITH_REFERENCE` (used in `sdk/generate.ts`, `sdk/list.ts`, `sdk/get.ts`, `sdk/authenticated-action.ts`) * Ad-hoc message in `sdk/connect.ts` workspace lookup and specification/collection helpers. If the error message is: ```bash Error: No authorization data found. Please use the `postman login` command. ``` or (when surfaced through the shared error message constant): ```bash Error: No authorization data found. Please use the `postman login` command. Refer: https://learning.postman.com/docs/postman-cli/postman-cli-options/#postman-login ``` It occurs in the following cases: * When running any of the following without a valid Postman API key or access token: * `postman sdk generate ` * `postman sdk list ` * `postman sdk get|fetch|download ` * `postman sdk connect github ` (initial auth check) * When calling helpers that require auth: * `identifyIdType` / `validateCollection` * Workspace discovery in `sdk/connect.ts` * `createSDKGeneratorService` when both `accessToken` and `postmanApiKey` are missing: ```bash Error: Authentication required. Please provide accessToken or postmanApiKey. ``` The expected response is: * The command exits with status code `1` after logging the error to `stderr`. To resolve this error, do the following: * Run `postman login` to create or refresh the local access token. * Or provide `POSTMAN_API_KEY` / `--api-key` as documented in the CLI auth docs. * Ensure the same account has access to the collections/specifications you are working with. ## Generate command errors and warnings ### Collection validation errors If the error message is: ```bash Error: Collection validation failed: Collection "12345-abcde-67890" not found. Please verify the collection ID and your access permissions. ``` It occurs in the following cases: * When the collection doesn't exist. * When the user doesn't have access to the collection. To resolve this error, do the following: * Verify the collection ID is correct. * Check that you have access to the collection. * Ensure you're authenticated with the correct account. If the error message is: ```bash Error: Collection validation failed. Please check the collection ID and your access permissions. ``` It occurs in the following cases: * When collection validation fails for any reason. To resolve this error, do the following: * Verify the collection ID. * Check your access permissions. * Ensure you're authenticated. ### Collection identifier errors If the error message is: ```bash Error: Invalid ID provided. Expected a Postman Collection ID or Specification ID. ``` It occurs in the following cases: * When the ID is null, undefined, or not a string. If the error message is: ```bash Error: URLs are not currently supported. Please provide a Postman Collection ID or Specification ID (UUID). ``` It occurs in the following cases: * When the ID is a URL (starts with `http://` or `https://`). If the error message is: ```bash Error: File paths are not currently supported. Please provide a Postman Collection ID or Specification ID (UUID). ``` It occurs in the following cases: * When the ID looks like a file path (for example ends with `.json`, `.yaml`, `.yml`, or contains `/` or `\`). If the error message is: ```bash Error: Invalid ID: "invalid-id". Expected a Postman Collection ID or Specification ID (UUID format). ``` It occurs in the following cases: * When the ID format is invalid. * When it doesn't match a supported UUID format. To resolve this error, do the following: * Use a valid Postman Collection ID or specification ID in UUID format. Supported formats include: * Standard UUID (8-4-4-4-12), typically used for specifications. * Prefixed UUID (8-8-4-4-4-12), typically used for collections. ### Language selection errors If the error message is: ```bash Error: Cannot use both --all and --language flags. Please use either --all to generate all languages or --language to specify specific languages. ``` It occurs in the following cases: * When both `--all` and `--language` flags are used together. To resolve this error, do the following: * Use either `--all` to generate all languages, or `--language` to specify specific languages. If the error message is: ```bash Error: No languages selected. SDK generation cancelled. ``` It occurs in the following cases: * When the user cancels the language selection prompt. * When no languages are selected from the interactive prompt. To resolve this error, do the following: * Re-run the command and select at least one language. * Or use `--language` flag to specify languages directly. If the error message is: ```bash Error: Unsupported language(s): swift. Supported languages: typescript, python, java, kotlin, csharp, go, php, ruby, rust ``` It occurs in the following cases: * When an unsupported language is specified. To resolve this error, do the following: * Use one of the supported languages: `typescript`, `python`, `java`, `kotlin`, `csharp`, `go`, `php`, `ruby`, `rust`. If the error message is: ```bash Error: At least one language must be specified. ``` It occurs in the following cases: * When no valid languages are provided after filtering. ### Configuration file errors If the error message is: ```bash Error: Failed to load config file: Config file not found: /path/to/config.json ``` It occurs in the following cases: * When the specified config file doesn't exist. If the error message is: ```bash Error: Failed to load config file: Failed to fetch config from URL: ``` It occurs in the following cases: * When fetching a config file from a URL fails. If the error message is: ```bash Error: Failed to load config file: Failed to read config file: ``` It occurs in the following cases: * When reading a local config file fails. If the error message is: ```bash Error: Failed to load config file: Failed to parse config file: ``` It occurs in the following cases: * When the config file contains invalid JSON. If the error message is: ```bash Error: Failed to load config file: Config file validation failed: ``` It occurs in the following cases: * When the config file doesn't match the expected schema. To resolve this error, do the following: * Check the config file format against the schema. * Ensure all required fields are present. * Validate JSON syntax. ### SDK generation API errors If the error message is: ```bash Error: SDK generation failed: Rate limit exceeded. Please try again later. Rate limit resets at: 3:45:30 PM ``` It occurs in the following cases: * When the API rate limit is exceeded (HTTP 429). To resolve this error, do the following: * Wait until the rate limit resets. * Reduce the frequency of requests. If the error message is: ```bash Error: SDK generation failed: You do not have permission to generate SDKs. Please check your account permissions. ``` It occurs in the following cases: * When the user doesn't have permission to generate SDKs (HTTP 403). To resolve this error, do the following: * Check your account permissions. * Contact your administrator if needed. If the error message is: ```bash Error: Build polling failed: ``` It occurs in the following cases: * When polling for build status fails. * When build polling times out. To resolve this error, do the following: * Check your network connection. * Try again later. * Check build status manually. If the error message is: ```bash Error: Failed to initialize SDK service: ``` It occurs in the following cases: * When the SDK generator service fails to initialize. To resolve this error, do the following: * Check your authentication. * Verify network connectivity. * Try again. ### PR creation errors If the error message (specification ID with `--pr`) is: ```bash Error: PR creation is not supported for specifications. The integrations API does not currently support specifications. Please use a collection ID instead, or omit the --pr flag. Support for specifications is being worked on and may be available in a future release. ``` It occurs in the following cases: * When `postman sdk generate --pr` is used (PRs are only supported for collection IDs, not specification IDs). This warning message (generic PR failure) appears: ```bash ⚠ PR creation failed: ``` It occurs in the following cases: * When PR creation fails (non-fatal, doesn't stop SDK generation). This is a warning, not an error. SDK generation continues even if PR creation fails. ## List command errors ### Status validation errors If the error message is: ```bash Error: Invalid status: "invalid-status". Must be one of: IN_PROGRESS, SUCCESS, FAILURE (case-insensitive) ``` It occurs in the following cases: * When an invalid status filter is provided. To resolve this error, do the following: * Use one of: `in-progress`, `success`, `failure` (case-insensitive) ### API errors If the error message is: ```bash Error: Failed to list builds: Rate limit exceeded. Please try again later. ``` It occurs in the following cases: * When rate limit is exceeded (HTTP 429). If the error message is: ```bash Error: No builds found for this collection. ``` It occurs in the following cases: * When no builds exist for the collection (HTTP 404). To resolve this error, do the following: * Generate a build first using `postman sdk generate`. If the error message is: ```bash Error: Server error while fetching builds. Please try again later. ``` It occurs in the following cases: * When a server error occurs (HTTP 500+). If the error message is: ```bash Error: Failed to list builds: HTTP Status: ``` It occurs in the following cases: * When verbose mode is enabled and an error occurs. * Shows the HTTP status code for debugging. ### Download errors If the error message is: ```bash Error: Error fetching build details: ``` It occurs in the following cases: * When fetching full build details fails during download. If the error message is: ```bash Error: Error downloading SDKs: ``` It occurs in the following cases: * When downloading SDKs from a build fails. ## Get/Fetch command errors ### Build ID validation errors If the error message is: ```bash Error: Invalid build ID provided. Build ID must be a positive number. ``` It occurs in the following cases: * When the build ID isn't a valid positive number. To resolve this error, do the following: * Provide a valid numeric build ID. ### Build not found errors If the error message is: ```bash Error: Build not found: 12345 Please verify the build ID is correct. ``` It occurs in the following cases: * When the build ID doesn't exist (HTTP 404). To resolve this error, do the following: * Verify the build ID is correct. * List builds first to see available build IDs. If the error message is: ```bash Error: No SDKs found in build ``` It occurs in the following cases: * When the build has no successful SDK artifacts. To resolve this error, do the following: * Check if the build completed successfully. * Try a different build ID. If the error message is: ```bash Error: No SDK found for language: TYPESCRIPT Available: PYTHON, JAVA ``` It occurs in the following cases: * When requesting a specific language that doesn't exist in the build. To resolve this error, do the following: * Use one of the available languages. * Or omit the `--language` flag to download all available SDKs. If the error message is: ```bash Error: No SDK artifacts found in build ``` It occurs in the following cases: * When no SDK artifacts are found in the build. ### Download errors If the error message is: ```bash ✗ Failed: No artifact URL found and collection ID is missing ``` It occurs in the following cases: * When an artifact has no URL and the collection ID is missing. If the error message is: ```bash ✗ Failed: ``` It occurs in the following cases: * When downloading a specific SDK language fails. If the error message is: ```bash Error: Build fetch failed: Rate limit exceeded. Please try again later. Rate limit resets at: 3:45:30 PM ``` It occurs in the following cases: * When rate limit is exceeded (HTTP 429). If the error message is: ```bash Error: Failed to initialize SDK service: ``` It occurs in the following cases: * When SDK service initialization fails. ## Connect command errors ### Provider validation errors If the error message is: ```bash Error: Unsupported provider "gitlab". Currently only "github" is supported. ``` It occurs in the following cases: * When an unsupported provider is specified. To resolve this error, do the following: * Use `github` as the provider. ### Language validation errors If the error message is: ```bash Error: Language is required. Use --language or -l flag. Supported languages: typescript, python, java, kotlin, csharp, go, php, ruby, rust ``` It occurs in the following cases: * When language isn't provided. To resolve this error, do the following: * Use `--language` or `-l` flag to specify a language. If the error message is: ```bash Error: Invalid language: "swift". Must be one of: typescript, python, java, kotlin, csharp, go, php, ruby, rust ``` It occurs in the following cases: * When an unsupported language is specified. To resolve this error, do the following: * Use one of the supported languages. ### Workspace errors If the error message is: ```bash Error: No workspaces found for this user. ``` It occurs in the following cases: * When the user has no accessible workspaces. If the error message is: ```bash Error: Collection 12345-abcde-67890 not found in any of your workspaces. Please provide the workspace ID manually using the --workspace option. ``` It occurs in the following cases: * When the collection can't be found in any workspace. To resolve this error, do the following: * Provide the workspace ID manually using `--workspace` option. ### OAuth authentication errors If the error message is: ```bash Error: Authentication timeout. Please try again. ``` It occurs in the following cases: * When OAuth authentication takes too long (5 minutes timeout). To resolve this error, do the following: * Try the authentication process again. * Complete the browser authentication promptly. If the error message is: ```bash Error: OAuth token not available. Please try again. ``` It occurs in the following cases: * When OAuth token is missing after authentication. To resolve this error, do the following: * Re-run the connect command. * Complete the OAuth flow again. ### Repository errors If the error message is: ```bash Error: No repositories found for ``` It occurs in the following cases: * When the selected owner/organization has no repositories. To resolve this error, do the following: * Select a different owner/organization. * Ensure the owner has accessible repositories. If the error message is: ```bash Error: No branches found for / ``` It occurs in the following cases: * When the repository has no branches. To resolve this error, do the following: * Ensure the repository has at least one branch. * Check repository access permissions. ### Integration errors If the error message is: ```bash Error: Integration is missing required configuration (owner, repo, or access token) ``` It occurs in the following cases: * When an integration is missing required configuration. This warning message appears: ```bash Warning: Could not fetch GitHub user info: ``` It occurs in the following cases: * When GitHub user info can't be fetched (non-fatal). This warning message appears: ```bash Warning: Failed to delete integration : ``` It occurs in the following cases: * When deleting an existing integration fails (non-fatal). If the error message is: ```bash Error: No files were copied to the repository ``` It occurs in the following cases: * When no SDK files are found to copy to the repository. To resolve this error, do the following: * Ensure SDKs were generated successfully. * Check the output directory contains SDK files. If the error message is: ```bash ✗ Failed to create PR for integration (): ``` It occurs in the following cases: * When creating a PR for a specific integration fails. If the error message is: ```bash ✗ Failed to create pull request(s) ``` It occurs in the following cases: * When one or more PRs fail to be created. ## Build completion errors ### Build status errors If the error message is: ```bash ✗ Build failed Failed artifacts: ✗ typescript ✗ python Warnings: ⚠ ``` It occurs in the following cases: * When a build fails completely. * Shows failed artifacts and their errors. This warning message appears: ```bash ⚠ Build completed with partial success Duration: 45s Failed to generate some SDKs: ✗ typescript Warnings: ⚠ ✓ Successfully generated 2 SDK(s), 1 failed ``` It occurs in the following cases: * When a build completes with some successful and some failed artifacts. If the error message is: ```bash Error: SDK generation failed. Check the error details above for more information. ``` It occurs in the following cases: * When build completion handling fails. ### Download errors If the error message is: ```bash Error: SDK generation cancelled. Existing directories were not overwritten. ``` It occurs in the following cases: * When user declines to overwrite existing SDK directories. To resolve this error, do the following: * Use `--yes` flag to automatically overwrite. * Or manually remove existing directories. If the error message is: ```bash ✗ : ``` It occurs in the following cases: * When downloading a specific language SDK fails. ## Resource validation errors ### Collection validation errors If the error message is: ```bash Error: Collection ID is required for validation. ``` It occurs in the following cases: * When collection ID is missing. If the error message is: ```bash Error: Collection "12345-abcde-67890" not found. Please verify the collection ID and your access permissions. ``` It occurs in the following cases: * When collection doesn't exist or user lacks access. ## Configuration errors ### Config file errors If the error message is: ```bash Error: Config file not found: /path/to/config.json ``` It occurs in the following cases: * When the specified config file doesn't exist. If the error message is: ```bash Error: Failed to fetch config from URL: ``` It occurs in the following cases: * When fetching config from URL fails. If the error message is: ```bash Error: Failed to read config file: ``` It occurs in the following cases: * When reading a local config file fails. If the error message is: ```bash Error: Failed to parse config file: ``` It occurs in the following cases: * When config file contains invalid JSON. If the error message is: ```bash Error: Config file validation failed: ``` It occurs in the following cases: * When config file doesn't match the expected schema. ## Language validation errors ### Language format errors If the error message is: ```bash Error: Unsupported language(s): swift. Supported languages: typescript, python, java, kotlin, csharp, go, php, ruby, rust ``` It occurs in the following cases: * When unsupported languages are specified. To resolve this error, do the following: * Use supported languages: `typescript`, `python`, `java`, `kotlin`, `csharp`, `go`, `php`, `ruby`, or `rust`. If the error message is: ```bash Error: At least one language must be specified. ``` It occurs in the following cases: * When no valid languages are provided. If the error message is: ```bash Error: Could not extract language from bucket key: ``` It occurs in the following cases: * When language can't be extracted from artifact bucket key. ## File system errors ### Download errors If the error message is: ```bash Error: Download failed: ``` It occurs in the following cases: * When downloading an artifact fails. If the error message is: ```bash Error: HTTP : Failed to download artifact ``` It occurs in the following cases: * When artifact download returns an error status code. If the error message is: ```bash Error: Failed to write file: ``` It occurs in the following cases: * When writing downloaded file to disk fails. To resolve this error, do the following: * Check disk space. * Verify write permissions. * Check file path validity. ### Artifact errors If the error message is: ```bash Error: Artifact does not contain SDK metadata or bucket key ``` It occurs in the following cases: * When artifact is missing required metadata. If the error message is: ```bash Error: SDK Generator Service and collectionId are required to fetch download URL ``` It occurs in the following cases: * When required parameters are missing to fetch download URL. If the error message is: ```bash Error: Artifact URL is missing ``` It occurs in the following cases: * When artifact has no download URL. ## HTTP status code errors ### Rate limit (429) If the error message is: ```bash Error: failed: Rate limit exceeded. Please try again later. Rate limit resets at: