Edge API Route discrepancy when creating a custom role

[kpg-apigee]

I was working on creating a custom role that was scoped to proxy related tasks. I posted to "/organizations/{org}/userroles{role}/resourcepermissions" with a number of permissions based on the API documentation described here (https://apidocs.apigee.com/docs/api-proxies/1/overview). For example, this:

    {
      "path": "/apis",
      "permissions": [
        "delete",
        "get",
        "put"
      ]      
    }

I kept getting 403's against this role so I took a look at some of the other built in roles and saw that proxies seemed to be defined with routes using the word "applications" instead of "apis".

I changed my permission to:

    {
      "path": "/applications",
      "permissions": [
        "delete",
        "get",
        "put"
      ]      
    }

and it appears to work.

Given this works, I can only assume I guessed correctly. If so, is this intentional? Can I assume this applies to any use of the word "apis" in routes, such as proxy-scoped key value maps ("/apis/*/keyvaluemaps" for example)? Can I safely continue to use "applications" instead of "apis"?