Join OpenAPI Specifications

Merge multiple OpenAPI specifications into a single document.

Specification Files (2-5 specs)

Select 2-5 JSON or YAML files (max 1MB each)

Collision Strategy How to handle conflicting schema/path names

Advanced Options

Path Collision Strategy

Schema Collision Strategy "Deduplicate or Rename" merges schemas that are equivalent and falls back to renaming the ones that are not, instead of failing

Equivalence Mode Depth of schema comparison. Applies only to the "Deduplicate" strategy — "Deduplicate or Rename" and semantic deduplication always compare deeply.

Documentation in Comparison Whether title, description, and examples count when comparing schemas

Semantic deduplication

Enable semantic deduplication Merge structurally identical schemas across documents. The three settings below apply only when this is enabled — they do not affect the Schema Collision Strategy above.

Deduplication Scope Which schema names semantic deduplication may fold into another

Deduplication Mode What becomes of a name once it is folded into an equivalent one

Report what deduplication consolidated List each surviving schema name and the names folded into it

Pre-join Overlay (optional) Apply to all specs before joining

Post-join Overlay (optional) Apply to result after joining

How it's done

Full documentation · pkg.go.dev