Request to path `/` returns 2 different mock types, depending on query param inclusion

Get Support
1

I imported an OpenAPI Schema, that has a path / with optional query params, page.size, page.number and filter.

The response is setup to be an array of objects.

In APIDog, using Cloud Mock, if i make a request (inside API Dog) the query params are included in the request, but with no values e.g. https://mock.apidog.com/m1/xxx-xxx-default/?page.number&page.size&filter and the correct response is given. But if I were to use this mock API URL in my own code, I would want to just call https://mock.apidog.com/m1/xxx-xxx-default/ as the query params are fully optional. But by doing so, the response given is wrong. It is just a singular object response, not an array.

API Dog even tells me that the response is wrong and should be an array. What I can;t figure out is why this is happening. The path in question literally only has one response schem setup, for a 200 response, and it is defined as an array of objects.

2

Could you please provide a screenshot of the issue? This will help us better understand and investigate the problem.

3

Looks like it may have been a conflict with having an OPTIONS method path. After I removed every path except one, /, the response was constant, regardless of including the query params or not.

What is annoying is that the request always includes the optional query params, even if they have no value, and without the = sign. Why would you ALWAYS include the params by default?!

4

Could you please share a screenshot of the error? I’m unable to reproduce the issue you described.