import-api-spec

To import an OpenAPI spec, provide the specification file to validate syntax and resolve $ref references, generating a structured api-reference bundle with introduction, authentication, errors, and rate-limiting pages ready to publish.

Yes, you can generate documentation bundles for GraphQL and AsyncAPI specifications. The tool detects the spec type and routes it to appropriate scaffolding, creating schema.graphql, queries, and mutations for GraphQL.

Yes, the API spec importer automatically resolves $ref references and extracts servers, security schemes, and error definitions during syntax validation to ensure accurate documentation generation across multiple spec versions and formats.

The best way to automate API spec ingestion is to route your OpenAPI, GraphQL, or AsyncAPI files through automatic spec detection and validation, outputting a structured, versioned api-reference bundle directly into your documentation portal.

You can validate syntax and detect the spec type of an unknown API specification file by feeding it into the importer, which automatically identifies formats like OpenAPI, Swagger, GraphQL, AsyncAPI, and Protobuf before routing.

No, you do not need to manually structure API reference docs. The importer automatically generates a ready-to-publish documentation bundle with relevant sections like introduction, authentication, and errors directly from your Swagger or AsyncAPI spec.