Mock endpoint conflict between static and path parameter routes

Steps to Reproduce:

Create two endpoints in Apidog:

GET /dashboard/{id}

GET /dashboard/lookups

Assign different response examples for each.

Start mock server.

Hit endpoints directly in the browser:

https://mock.apidog.com/.../dashboard/1 → returns correct mock for {id}.

https://mock.apidog.com/.../dashboard/lookups → incorrectly returns the {id} mock response.

Expected Behavior:
/dashboard/lookups should match the static route and return its assigned mock response.

Actual Behavior:
/dashboard/lookups is interpreted as {id} = “lookups” and returns the wrong mock response.

Mock setting: Response Example First

Tested in browser (Chrome) Version 139.0.7258.139

I can’t seem to reproduce the same issue. Please verify my steps. If there are any screenshots or data you can’t share here, feel free to email us.

endpointA

endpointB




this was the exact example of my issue




Screenshot_2.jpg

Thank you for your feedback. We’re currently trying to reproduce this issue.

I might have reproduced your issue. Please compare:

endpointA

endpointB

When I run endpointB with query parameters, it shows the correct response.

When I run endpointB without query parameters, it shows the wrong response.






yes exactly query paramters does change the response from the mock

when I removed the query param from the endpoint B the expected response was returned correctly




Based on your description, this is the expected behavior of the mock server. When query parameters are included in the endpoint, the mock response will only match if those same query parameters are provided. Without the query parameters, the mock server will default to matching the /dashboard/{id} route, which is the correct logic.