@ThomasGoossens support for lenient URL path processing for OAuth 2.0 requests has being removed. This includes requests with trailing slashes, as your topic title suggests that you are using.
You would be receiving an HTTP response on the following form:
HTTP/2 401
X-Failure-Category: FAILURE_CLIENT_SCOPE_CHECK
{
"code": 401,
"message": "Unauthorized; scope does not match"
}
@ThomasGoossens ah. If you are not able to access the Get config statustype {id} endpoint using OAuth 2.0, it is simply because it is has no scopes assigned and is therefore not available using OAuth 2.0.
I would suggest raising a support request for this, so that a feature request can be funnelled to the appropriate team.