Postman SDK language options

Set the scope for the npm package name.

Set the name for the npm package.

Set the HTTP client for the SDK. Choose between Axios, Fetch, or the Node HTTPS module, depending on your preference or requirements.

Set to true configures the TypeScript SDK so that it can be bundled using tsup. This is required if you want to use the SDK in a browser environment, and it can also be used in Node.js environments. When set to true, the generated SDK will include a bundle script in the package.json file that uses tsup to create a bundled version of the SDK.

Determine whether to export the main SDK class as the default export. By default, the main SDK class is exported as a named export. Setting exportClassDefault to true changes this behavior so that the main SDK class is exported as the default export, which can simplify imports in some cases.

Set the group ID for the Java package. This is set as the groupId in the pom.xml file, as well as being used to define the namespace for the SDK classes.

Set the artifact ID for the Java package. This is set as the artifactId in the pom.xml file, as well as being used to define the name of the main SDK class.

Set the developers for the Java package. This is set as the developers in the pom.xml file, as well as being used to define the developers of the SDK. The options for each developer are name, email, organization, and organizationUrl. The organizationUrl can be used to link to the developer’s organization, such as a GitHub profile or company website.

Set the name of the PyPI package to publish to. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI.

Set the version of the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI.

Set the description of the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI.

Set the path to the README file for the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. This should be a path to a file that contains the long description of the package, which is typically the README file. The content of this file is used as the long description on the PyPI package page.

Set the Python version requirement for the package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. This should be a string that specifies the minimum Python version required, such as >=3.8.

Set the license for the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. This should be a string that specifies the license for the package, such as license = {text = "MIT"}, license = {text = "Apache-2.0"}, or license = {text = "GPL-3.0"}. This information is important for users of the SDK to understand the terms under which they can use and distribute the package.

Set the authors for the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. Each author should have a name and email, which are used to define the authors of the package on PyPI.

Set the keywords for the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. Keywords are used to help users find the package on PyPI when searching for related topics.

Set the classifiers for the Python package. This is set in the pyproject.toml file, and is used when publishing the SDK to PyPI. Classifiers are used to provide metadata about the package, such as the intended audience, license, programming language, and more. This information helps users understand the compatibility and purpose of the package.

Set the NuGet package ID and root C# namespace for the SDK. This value is used as the root namespace for all generated classes (Config, Models, Services, and so on) and as the <PackageId> in the .csproj file. Defaults to the PascalCase form of the SDK name.

Set the authors for the SDK package. Each entry supports a name (required) and an optional email. The author names are written to the <Authors> field in the .csproj file.

Set the homepage URL for the SDK package. Written to the <PackageProjectUrl> field in the .csproj file.

Set the Go module path for the SDK. This value is written to go.mod as the module declaration and is used in all internal package import paths throughout the generated code (for example, github.com/your-org/your-sdk). If you intend to publish the module publicly, the path must match the repository URL so that go get can resolve it correctly.

Set the homepage URL for the SDK. Written into the generated README.md.

Set the Composer package name for the SDK (for example, your-org/your-sdk). This value is written to composer.json as the name field and is used when publishing the package to Packagist.

Set the authors for the SDK package. Each entry supports a name (required) and an optional email. Author information is serialized into the authors array in composer.json.

Set the homepage URL for the SDK package. Written to the homepage field in composer.json.

OTLP endpoint URL for trace data.

The 'otlp-http' or 'console' exporter type.

Custom HTTP headers for authentication.

Maximum spans per batch.

Delay between batch exports (milliseconds).

Timeout for export operations (milliseconds).