Keycloak integration example docs

[Ubong]

Hi @z11373,

Thank you for your patience.

It appears that loading OAS APIs directly from a directory is not yet supported—this functionality is still in the backlog (ref: TT-6635).
Please use the /tyk/apis/oas endpoint to create the API.

You can also refer to the posts below for additional context.

OAS API Import generates two json files

Hi I have a question regarding the import of an OpenAPI definition. If I import an OpenAPI definition with the following request: POST somehost/tyk/apis/oas/import?allowList=true&listenPath=/api/ X-Tyk-Authorisation: foo < ./api-openapi-schema-v3.json Then two files are created in the apps folder, e.g. 383dc712e64a4717bc9524e8602e28b0.json 383dc712e64a4717bc9524e8602e28b0-oas.json The file 383dc712e64a4717bc9524e8602e28b0-oas.json contains the Tyk OAS API definition. The file 383dc712e…

Import/Create API using OAS in YAML Format

Hi, Is it possible to import/create an API using the YAML format instead of the Json format via API Call (path = /tyk/apis/oas) ? Thank you!