Postman SDK customization options

Custom access token authentication options.

API key authentication options.

The prefix to use for the custom access token authentication. By default, when using custom access token authentication, the Authorization header is passed as Bearer <token>.

By setting the prefix, you can replace “Bearer” with the value of your choice. For example, setting this to "Token" will result in headers like Authorization: Token YOUR_TOKEN.

The header to use for the API key authentication. This is used by the SDKs to set the header when making requests to the API.

For example, if you set this to "MY_CUSTOM_APIKEY_HEADER", the API key will be passed to your API using that header instead of the default X-API-KEY header.

Controls whether the SDK generator tracks changes to generated files between regenerations.

CLI override: --no-track-changes (sets to false)

When true, the generator detects local edits and uploads them for merge processing. When false, the generator performs a clean regeneration that overwrites all files.

Defines how the generator handles merge conflicts when both you and the generator modify the same lines in a file.

CLI override: --conflict-strategy <strategy>

• "mark" — Adds conflict markers to the file, allowing manual resolution
• "ours" — Keeps your changes and discards the generator’s changes
• "theirs" — Keeps the generator’s changes and discards your changes

Controls whether to skip the merge process entirely, even when edits are detected.

CLI override: --no-merge (sets to true)

When true, forces a clean regeneration of the SDK that overwrites all files, regardless of detected changes.