- Collection
- Environment
Conversion behavior
The converter handles several differences between the Postman and Bruno data formats automatically.Non-string value coercion
Postman’s schema allows numeric and other non-string values in fields like header values, query parameters, form fields, and authentication credentials. Bruno expects all of these to be strings. During conversion, non-string values are automatically coerced:- Numbers (e.g.,
5000) become their string equivalent ("5000") - Objects are serialized as JSON strings
nullorundefinedvalues default to an empty string (or a field-specific fallback for auth fields)
- Request headers, query parameters, and path parameters
- URL-encoded and multipart form body fields
- Authentication fields across all auth types (Basic, Bearer, AWS Signature v4, API Key, Digest, OAuth 1.0, and OAuth 2.0)
- Example request and response fields
Header format normalization
Postman’s v2.1 schema permits headers in several formats. The converter normalizes all of them into Bruno’s standard array-of-objects format:| Postman header format | Example |
|---|---|
| Array of objects (most common) | [{ "key": "Content-Type", "value": "application/json" }] |
| Mixed array of strings and objects | ["Content-Type: application/json", { "key": "Accept", "value": "*/*" }] |
| Single concatenated string | "Content-Type: application/json\r\nAccept: */*" |
null | Treated as an empty header list |