Export

Export an existing collection for another tool. Review literal request values and local file paths before sharing the result.

Export in the TUI

Open the command palette with Ctrl+P and choose Export Collection. Select OpenAPI or Postman and an output folder; the overlay previews the exact target before exporting. If the default Postman target already exists, Noodle uses the next numbered directory.

OpenAPI

noodle export ./collections --format openapi --output ./specs/openapi.yml

The document includes enabled request parameters and headers, request-body examples, folders as tags, supported authentication schemes, and each enabled, nonempty environment base_url as a server. Other environment values and response timeline data are not exported.

XML bodies export as literal string examples. Explicit XML MIME types such as application/soap+xml are preserved; a Noodle extension preserves XML intent when a request uses a non-XML media type.

NTLM and AWS SigV4 export as HTTP security schemes. Validate those schemes with the OpenAPI consumer that will read the document.

OAuth 2.0 exports as standard authorization code, client credentials, implicit, or password flows when explicit endpoints cover the selected grant. Discovery-only auth exports as openIdConnect with the normalized discovery URL, scopes, and Noodle extensions for the grant and issuer URL kind. Partial endpoint overrides with discovery are rejected because OpenAPI cannot preserve both sources faithfully. Client credentials, cached tokens, generated state, and other secure runtime values are omitted. OAuth 1.0a auth is omitted because OpenAPI 3.0 has no matching security-scheme type.

Postman

noodle export ./collections --format postman --output ./exports/postman

The output directory must be new or empty. Noodle writes collection.postman_collection.json and one redacted <environment>.postman_environment.json file per environment. Request literals remain intact and can contain secrets, so review a bundle before sharing it.

Home-relative @/ file paths expand to absolute paths in Postman output. That keeps file requests runnable, but can reveal local usernames and directories.

Noodle-specific TLS settings and OS-vault credentials are not translated into OpenAPI or Postman output.

Postman output uses its matching ntlm, awsv4, oauth1, and oauth2 auth representations. OAuth configuration is preserved, but cached OAuth 2 tokens and generated OAuth 1 signatures are not exported. XML bodies use Postman’s raw XML representation. Discovery-backed OAuth 2 must supply every endpoint required by the selected grant before Postman export; Postman has no discovery field.

On import, Noodle maps XML request examples from OpenAPI and Swagger, raw XML bodies from Postman, and XML bodies from Insomnia. It also maps OAuth 2.0 flows from OpenAPI; OAuth 1.0a and OAuth 2.0 from Postman and Insomnia; NTLM from OpenAPI, Postman, and Insomnia; and AWS SigV4 from Postman. Review imported grant types, endpoints, signing methods, token placement, and credentials. Move sensitive values and private keys to secret environment declarations before sending.

For either format, use an output path outside the collection directory.