--- title: "Get policy-assigned resource" slug: "management-subaccount-getpolicyresources" updated: 2026-09-17T10:05:32Z published: 2026-09-17T10:05:32Z canonical: "api.ncloud-docs.com/management-subaccount-getpolicyresources" --- > ## Documentation Index > Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Get policy-assigned resource Available in Classic and VPC Get resources (sub accounts, groups, roles) to which a policy is assigned. ## Request This section describes the request format. The method and URI are as follows: | Method | URI | | --- | --- | | GET | /api/v1/policies/{policyId}/resources | ### Request headers For information about the headers common to all Sub Account APIs, see [Sub Account request headers](/docs/en/management-subaccount#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94). ### Request path parameters You can use the following path parameters with your request: | Field | Type | Required | Description | | --- | --- | --- | --- | | `policyId` | Array | Required | Policy ID list - See [Get policy list](/docs/en/management-subaccount-getpolicies) | ### Request example The request example is as follows: ``` curl --location --request GET 'https://subaccount.apigw.ntruss.com/api/v1/policies/7938a9f0-****-****-****-005056a7ecf2/resources' \ --header 'x-ncp-apigw-timestamp: {Timestamp}' \ --header 'x-ncp-iam-access-key: {Access Key}' \ --header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \ --header 'Accept: application/json' ``` ## Response This section describes the response format. ### Response body The response body includes the following data: | Field | Type | Required | Description | | --- | --- | --- | --- | | `resourceType` | String | - | Resource type - `SubAccount` \| `Group` \| `Role` | | `resourceId` | String | - | Resource ID | | `resourceName` | String | - | Resource name | | `nrn` | String | - | NAVER Cloud Platform resource identification value | ### Response status codes For information about the HTTP status codes common to all Sub Account APIs, see [Sub Account status codes](/docs/en/management-subaccount#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C). ### Response example The response example is as follows: ``` [ { "resourceType": "SubAccount", "resourceId": "dd578a70-****-****-****-246e96591a38", "resourceName": "role001", "nrn": "nrn:PUB:IAM::*******:SubAccount/dd578a70-****-****-****-246e96591a38" }, { "resourceType": "Group", "resourceId": "c046b960-****-****-****-246e96591594", "resourceName": "group", "nrn": "nrn:PUB:IAM::*******:Group/c046b960-****-****-****-246e96591594" }, { "resourceType": "Role", "resourceId": "5d0d4d80-****-****-****-246e96591a38", "resourceName": "role002", "nrn": "nrn:PUB:IAM::*******:Role/5d0d4d80-****-****-****-246e96591a38" } ] ```