Oasify | API Spec Transpiler as a Service

Why Oasify?

Manually crafting OpenAPI 3 specs from existing API descriptions is error-prone and time-consuming. Oasify automates that translation so you can:

Accelerate API onboarding and documentation.
Migrate legacy SOAP (WSDL) or GraphQL services into REST-friendly OpenAPI.
Ensure your AWS Marketplace offering is accompanied by a standard-compliant API specification.
Integrate seamlessly into CI/CD pipelines with programmatic access.

Core Benefits

Quick conversion: Get OAS3 output in seconds—no manual rewriting.

Format support: Postman, GraphQL (SDL/introspection/URL), WSDL → OpenAPI 3.

Marketplace-ready: Output that fits into AWS Marketplace workflows and listings.

Key Features

Postman Collections

Upload your exported Postman collection (JSON). Oasify infers endpoints, parameters, and schemas and emits a compliant OpenAPI 3 definition ready for documentation or automation.

GraphQL Schemas

Provide SDL, introspection JSON, or even a GraphQL endpoint URL. Oasify introspects or parses the schema and produces a REST-style OpenAPI 3 spec to help bridge GraphQL to traditional tooling.

WSDL Files

Modernize legacy SOAP services: upload WSDL definitions and receive OpenAPI 3 representations, making integration with RESTful ecosystems straightforward.

How It Works

Select Source

Choose your input format: Postman JSON, GraphQL schema/introspection/URL, or WSDL XML.

Upload or Provide

Send the file or endpoint to the `/transpile` endpoint with your desired output mode.

Receive OAS3

Get back a fully formed OpenAPI 3 specification as a downloadable file or base64 payload, ready for use.

Quickstart

Start converting specs with a single curl command. Replace placeholders with your actual file paths or URLs.

1. Convert a Postman Collection (JSON) to OAS3 file

curl -X POST "https://oasify.uk/transpile?output_format=file" \
  -H "Content-Type: multipart/form-data" \
  -F "file=@your_postman_collection.json" \
  -o oas_definition.json

2. Convert GraphQL SDL to base64 OpenAPI payload

curl -X POST "https://oasify.uk/transpile?output_format=base64" \
  -H "Content-Type: multipart/form-data" \
  -F "file=@schema.graphql" \
  | jq -r '.file' | base64 --decode > oas_definition.json

(Requires jq and base64 to decode.)

3. Convert a WSDL

curl -X POST "https://oasify.uk/transpile" \
  -H "Content-Type: multipart/form-data" \
  -F "file=@service.wsdl" \
  -o oas_definition.json

Example Response (base64 mode)

A JSON object like:

{
  "file": "eyJvcGVuYXBpX2RlZmluaXRpb24iOiB7fX0=", 
  "source_type": "POSTMAN_COLLECTION", 
  "filename": "oas_definition.json"
}

You can decode the file field to get the OpenAPI JSON.

Frequently Asked Questions

What input formats are supported?

Postman Collections (JSON), GraphQL (SDL, introspection JSON, or endpoint URL), and WSDL XML.

What output do I get?

OpenAPI 3 specification: either as a downloadable JSON file or as a base64-encoded payload for programmatic pipelines.

Can I integrate this into CI/CD?

Yes. Use the API endpoint with scripts to automatically generate/upkeep OpenAPI definitions during your build or deployment process.

Is this compatible with AWS Marketplace requirements?

Yes. The OAS3 outputs are meant to be embedded in your offering metadata and documentation, and our website includes clearly visible support/contact information to satisfy AWS Marketplace guidelines.:contentReference[oaicite:2]{index=2}

Support & Contact

On-Premises Deployment

Need the solution inside your network? Ask about our on-premises deployment options.

Need Help or Found a Bug?

Help us help you—if the API isn’t working as expected, tell us what happened and we’ll jump on it ASAP.

Quick Message

Need guaranteed response times or SLA? Contact us and ask about enterprise support plans.

Effortlessly Transpile Your API Specs to OpenAPI 3