Hello @michelefabbri
Unfortunately, it seems you cannot pass those parameter values in the query path, since they are collectively nested inside the issuesApproachingLimitParams object, so you must provide them in the request body.
IMHO GET requests shouldn’t pass parameters values via the body. This has been a hotly debated topic and an unwritten rule for REST APIs for decades. Google obviously agree.
This new endpoint also breaks all of Atlassian’s own rules about their API endpoint formats, as I’m fairly sure no other GET endpoint in the entire Jira REST API set passes parameters in the request body.
I don’t think the Jira API team has thought this through… IMHO
rant
ALSO… little syntax things like one parameter field being remoteIssueLinks (uppercase for each word after the first one) but another being issuelinks (all lowercase) just tick me off! Be consistent; if you’re going to use uppercase for each word, do it always, not just sometimes, at random.
/ rant