Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/postmanlabs/openapi-to-postman
Plugin for converting OpenAPI 3.0 specs to the Postman Collection (v2) format
https://github.com/postmanlabs/openapi-to-postman
openapi openapi3 postman-collection
Last synced: about 1 month ago
JSON representation
Plugin for converting OpenAPI 3.0 specs to the Postman Collection (v2) format
- Host: GitHub
- URL: https://github.com/postmanlabs/openapi-to-postman
- Owner: postmanlabs
- License: apache-2.0
- Created: 2018-12-12T10:13:46.000Z (almost 6 years ago)
- Default Branch: develop
- Last Pushed: 2024-05-17T12:47:32.000Z (6 months ago)
- Last Synced: 2024-05-29T18:33:50.405Z (6 months ago)
- Topics: openapi, openapi3, postman-collection
- Language: JavaScript
- Size: 7.02 MB
- Stars: 875
- Watchers: 23
- Forks: 190
- Open Issues: 73
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
- memento - OpenAPI-to-Postman
- jimsghstars - postmanlabs/openapi-to-postman - Plugin for converting OpenAPI 3.0 specs to the Postman Collection (v2) format (JavaScript)
README
*Supercharge your API workflow.*
*Modern software is built on APIs. Postman helps you develop APIs faster.*
# OpenAPI 3.0, 3.1 and Swagger 2.0 to Postman Collection
#### Contents
1. [Getting Started](#getting-started)
2. [Command Line Interface](#command-line-interface)
1. [Options](#options)
2. [Usage](#usage)
3. [Using the converter as a NodeJS module](#using-the-converter-as-a-nodejs-module)
1. [Convert Function](#convert)
2. [Options](#options)
3. [ConversionResult](#conversionresult)
4. [Sample usage](#sample-usage)
5. [Validate function](#validate-function)
4. [Conversion Schema](#conversion-schema)
---
---
### 🚀 We now also support OpenAPI 3.1 and Swagger 2.0 along with OpenAPI 3.0.
---
---
## 💠Getting Started
To use the converter as a Node module, you need to have a copy of the NodeJS runtime. The easiest way to do this is through npm. If you have NodeJS installed you have npm installed as well.
```terminal
$ npm install openapi-to-postmanv2
```
If you want to use the converter in the CLI, install it globally with NPM:
```terminal
$ npm i -g openapi-to-postmanv2
```
## 📖 Command Line Interface
The converter can be used as a CLI tool as well. The following [command line options](#options) are available.
`openapi2postmanv2 [options]`
### Options
- `-s `, `--spec `
Used to specify the OpenAPI specification (file path) which is to be converted
- `-o `, `--output `
Used to specify the destination file in which the collection is to be written
- `-p`, `--pretty`
Used to pretty print the collection object while writing to a file
- `-i`, `--interface-version`
Specifies the interface version of the converter to be used. Value can be 'v2' or 'v1'. Default is 'v2'.
- `-O`, `--options`
Used to supply options to the converter, for complete options details see [here](/OPTIONS.md)
- `-c`, `--options-config`
Used to supply options to the converter through config file, for complete options details see [here](/OPTIONS.md)
- `-t`, `--test`
Used to test the collection with an in-built sample specification
- `-v`, `--version`
Specifies the version of the converter
- `-h`, `--help`
Specifies all the options along with a few usage examples on the terminal
### Usage
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options
```terminal
$ openapi2postmanv2 -s spec.yaml -o collection.json -p -O folderStrategy=Tags,includeAuthInfoInExample=false
```
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options via config file
```terminal
$ openapi2postmanv2 -s spec.yaml -o collection.json -p -c ./examples/cli-options-config.json
```
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options (Also avoids any `""` kind of errors present in converted collection)
```terminal
$ openapi2postmanv2 -s spec.yaml -o collection.json -p -O folderStrategy=Tags,requestParametersResolution=Example,optimizeConversion=false,stackLimit=50
```
- Testing the converter
```terminal
$ openapi2postmanv2 --test
```
## 🛠Using the converter as a NodeJS module
In order to use the convert in your node application, you need to import the package using `require`.
```javascript
var Converter = require('openapi-to-postmanv2')
```
The converter provides the following functions:
### Convert
The convert function takes in your OpenAPI 3.0, 3.1 and Swagger 2.0 specification ( YAML / JSON ) and converts it to a Postman collection.
Signature: `convert (data, options, callback);`
**data:**
```javascript
{ type: 'file', data: 'filepath' }
OR
{ type: 'string', data: '' }
OR
{ type: 'json', data: OpenAPI-JS-object }
```
**options:**
```javascript
{
schemaFaker: true,
requestNameSource: 'fallback',
indentCharacter: ' '
}
/*
All three properties are optional. Check the options section below for possible values for each option.
*/
```
Note: All possible values of options and their usage can be found over here: [OPTIONS.md](/OPTIONS.md)
**callback:**
```javascript
function (err, result) {
/*
result = {
result: true,
output: [
{
type: 'collection',
data: {..collection object..}
}
]
}
*/
}
```
### Options
Check out complete list of options and their usage at [OPTIONS.md](/OPTIONS.md)
### ConversionResult
- `result` - Flag responsible for providing a status whether the conversion was successful or not.
- `reason` - Provides the reason for an unsuccessful conversion, defined only if result if `false`.
- `output` - Contains an array of Postman objects, each one with a `type` and `data`. The only type currently supported is `collection`.
### Sample Usage
```javascript
const fs = require('fs'),
Converter = require('openapi-to-postmanv2'),
openapiData = fs.readFileSync('sample-spec.yaml', {encoding: 'UTF8'});
Converter.convert({ type: 'string', data: openapiData },
{}, (err, conversionResult) => {
if (!conversionResult.result) {
console.log('Could not convert', conversionResult.reason);
}
else {
console.log('The collection object is: ', conversionResult.output[0].data);
}
}
);
```
### Validate Function
The validate function is meant to ensure that the data that is being passed to the [convert function](#convert-function) is a valid JSON object or a valid (YAML/JSON) string.
The validate function is synchronous and returns a status object which conforms to the following schema
#### Validation object schema
```javascript
{
type: 'object',
properties: {
result: { type: 'boolean'},
reason: { type: 'string' }
},
required: ['result']
}
```
##### Validation object explanation
- `result` - true if the data looks like OpenAPI and can be passed to the convert function
- `reason` - Provides a reason for an unsuccessful validation of the specification
## 🧠Conversion Schema
| *postman* | *openapi* | *related options* |
| --- | --- | :---: |
| collectionName | info.title | - |
| description | info.description + info.contact | - |
| collectionVariables| server.variables + pathVariables | - |
| folderName | paths.path / tags.name | folderStrategy |
| requestName | operationItem(method).summary / operationItem(method).operationId / url | requestNameSource |
| request.method | path.method | - |
| request.headers | parameter (`in = header`) | - | [link](#Header/Path-param-conversion-example) |
| request.body | operationItem(method).requestBody | requestParametersResolution, exampleParametersResolution |
| request.url.raw | server.url (path level server >> openapi server) + path | - |
| request.url.variables | parameter (`in = path`) | - |
| request.url.params | parameter (`in = query`) | - |
| api_key in (query or header) | components.securitySchemes.api_key | includeAuthInfoInExample |