Schemas and links defined in the OAS are used to compose data definitions. Furthermore, hierarchical path structures can be used to nest data via the
addSubOperation option (learn more...).
GraphQL-incompatible identifiers of your API are sanitized. For example, API parameters or data definitions with unsupported characters (e.g.,
;...) are removed.
OASGraph provides viewers to support passing API keys or basic auth credentials. OAuth 2.0 integration can be handled by the hosting application (learn more...).
We've curated resources to help you get started faster with OASGraph.