Maybe I am just not seeing the “way it should be used properly” or the explicit reason why the parameter values are explicitly skipped in sync and therefore noted in those notification messages that i circled in screenshots, but kinda trying to see what’s the point of having sync for Endpoint Spec if I will put some other values for the parameters. Without that this is making the actual test scenario run “an instance” of endpoint with its own values similar to and Example in Endpoint Spec…
Personally I think it would be cool if there is an option to allow you to set the values sync on/off for your particular test scenario…
In Apidog, an endpoint spec includes the definition of parameters as well as a set of ‘example values.’ The values displayed on the endpoint spec page are considered ‘example values’ for these parameters, each having only one example value. However, in practice, when we make a request to this endpoint, we typically use a variety of request values. This is why the ‘example values’ from the endpoint specification are not directly used to overwrite the request values in the test step during sync.
Sync operation is used when there is a change in the parameters within the endpoint spec. For example, if you add a new field to the spec, clicking manual sync will sync it to the test steps.
OK but then what’s the difference between using and Cases of Endpoint Spec and a Test Scenario associated with Endpoint Spec where you will have to put some values for the request that will continue to “live” inside that test scenario step instance only?
isn’t that like just having an undocumented Endpoint Case just in different place? (Test Scenario step instance)
I think I am just failing to see the point then for making a Test Scenario Step from option “Import from endpoint spec” instead of “import from endpoint case” because that is going to make me have to maintaing the values in test scenario step instead o having all in one place in APIs tab in Endpoint spec, which I thought was main idealogy of Apidog, not to have to maintain similar/same things on multiple places but only in one place
So it seems that I will just have to use “import from endpoint case” when making my test scenario steps since that takes into the account parameter values as well from the Endpoint specs, since I find it weird to have to update values manually in test scenario step…
Because when doing API Testing the Parameter values are actually very often the key point in finding out problems and figuring out if the API works correctly or not, so kinda strange approach apidog team took here… 
Thanks for all the information though 
, I think my mindset and organization just differs a bit from the apidog team
You are right, if you expect to change values only in the endpoint case rather than manually changing them in the test steps, it is better to use import from endpoint case and choose the reference method. That may meet your needs.
It seems so
from testing point of view (since I am backend QA) - i have test cases and I make test plan/scenario from it. I wouldn’t expect to maintain anything about the test plan/scenario since all my logic will be in the cases
In some large teams, the develop and QA teams are separate. The QA team expects to maintain more independent and stable test scenarios, so they need to fill in request values themselves in the test steps, rather than just accepting changes to the endpoint specs made by developer, which might lead to execution failures. This is the reason for our design.
I get the reasoning but that would mean that i would have to maintain the Endpoint Cases values but also the values inside the test scenarios steps for some of the same Endpoints
which doesn’t make much sense since i would have similar/same functional logic in 2 places
therefore it makes more sense to just keep my functional logic and scenarios in Endpoint Cases and then use import from endpoint cases and keep a reference not copy
the only use case that i see for the test step values modification is if i want to just check something temporarly so i edit it there, but if I find it as useful scenario I would definietelly add it to endpoint cases so it can be regression tested at any point etc.
overall I think some switch button for the values here would probably add more versatility to the app and different users might find it useful for them or not
But I wouldn’t bother you anymore, thanks for all the answers