Bind data source with OpenAPI spec has body/response only as object

Get Support
1

When I setup a Data Source that pulls in our OpenAPI specification files, the body and responses end up disconnected from the schema that they should be. The schema is imported, but not linked correctly for the endpoints. However, if I manually do the import data with the same settings, it correctly imports and links the schemas.

This is a problem as we publish up our specifications and want to ensure ApiDog is updated regularly with the specification.

Bind_Data_Source_-_object_schema.png
Bind_Data_Source_-_object_schema.png633×549 37.9 KB

Import_Data_-_correct_schema.png
Import_Data_-_correct_schema.png782×500 44.3 KB

2

To help troubleshoot the issue, could you please provide:

  1. Your Apidog version and OpenAPI specification version
  2. Data source import method: Are you using Runner? If so, what’s the Runner version?
  3. Confirmation: Are the data models imported but just not linked to request/response bodies?
  4. A minimal reproducible OpenAPI file example
3
4
  1. Apidog 2.8.4. I’m using the Web version. OpenAPI Spec 3.1.0
  2. I am using a runner, it’s version is 1.9.2
  3. Yes, as far as I can tell, the data models are created in the schema section but not linked to request/response bodies.
  4. This publicly available sample demonstrates it for me - https://beeceptor.com/docs/storefront-sample.yaml
5

Thank you for your feedback. We are aware of this issue with Runner imports and will optimize it in future updates.