OAS API Import generates two json files

[forxina]

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 383dc712e64a4717bc9524e8602e28b0.json contains the Tyk Classic API definition.

The file 383dc712e64a4717bc9524e8602e28b0.json has a property: “is_oas”: true

Why are two files created here? I can’t find anything about this in the documentation.
I would be pleased if someone could provide me with an explanation.
Thank you very much!

[Olu]

@forxina Hello and welcome to the community

Sorry for the late reply.

@forxina

Why are two files created here? I can’t find anything about this in the documentation.
I would be pleased if someone could provide me with an explanation.

Yes, we don’t have it documented since It’s more of an internal implementation detail due to a current limitation that is awaiting a fix. Once that is resolved, it should then be possible to simply load Tyk OAS and Tyk Native API definitions side by side without the need to link them together.