> ## Documentation Index
> Fetch the complete documentation index at: https://developer.vanta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add owners to resources

> Use the Vanta API to update the owner and descriptions on your resources.

## Before you begin

This guide is for Vanta admins managing data inside their own Vanta account.

You'll need:

* A Manage Vanta [API token](https://developer.vanta.com/docs/quickstart/manage-vanta.md).
* The token must have scopes `vanta-api.all:read` and `vanta-api.all:write`.
* At least one connected integration whose resources need owners or descriptions.

Inventory resources need an active owner and a text description to pass the [Inventory items have active owners](https://app.vanta.com/tests/inventory-list-owners) and [Inventory items have descriptions](https://app.vanta.com/tests/inventory-list-descriptions) tests. Owners must be `CURRENT` employees — Vanta will reject `FORMER` users.

> [!NOTE]
>
> Onboarding a new owner across many integrations? Run Step 3 once per `(integrationId, resourceKind)` pair. The bulk-update endpoint accepts up to 50 resources per call.

**1. Find the resources missing an owner**

**Your terminal** — pick the `integrationId` and `resourceKind` you want to update. If you don't already know them, list connected integrations first with [`GET /v1/integrations`](https://developer.vanta.com/reference/manage-vanta/overview), then list resources filtered to `hasOwner=false`.

```bash Terminal theme={"system"}
curl 'https://api.vanta.com/v1/integrations/snowflake/resource-kinds/SnowflakeDatabase/resources?hasOwner=false&isInScope=true&pageSize=50' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer YOUR_TOKEN'
```

Response

```json theme={"system"}
{
  "results": {
    "data": [
      {
        "responseType": "Database",
        "resourceKind": "SnowflakeDatabase",
        "resourceId": "64dc848b6491f66d23c64df6",
        "connectionId": "64dbda1a6491f66d234bfd41",
        "displayName": "SNOWFLAKE",
        "owner": null,
        "inScope": true,
        "description": "Snowflake Database"
      }
    ],
    "pageInfo": { "hasNextPage": true, "endCursor": "..." }
  }
}
```

Copy each `resourceId` you want to update — you'll send them in Step 3.

> [accordion] Got a 401?
>
> Token is expired (one-hour lifetime), missing, or lacks `vanta-api.all:read`. Mint a fresh one — see [Authentication → Token expiration](https://developer.vanta.com/docs/concepts/authentication.md#token-expiration).

> [accordion] Don't know the integrationId or resourceKind?
>
> Call [`GET /v1/integrations`](https://developer.vanta.com/reference/manage-vanta/overview) to list connected integrations, their `connectionIds`, and the `resourceKinds` they expose (e.g. `aws`, `gcp`, `snowflake`, `okta`).

> [accordion] Filtering by description too?
>
> Add `hasDescription=false` to find resources missing a description. Some resource kinds (e.g. `SnowflakeDatabase`) auto-populate a description and won't show up in that filter.

**2. Get a user to assign as owner**

**Your terminal** — call [`GET /v1/people`](https://developer.vanta.com/reference/manage-vanta/overview) and filter to `CURRENT` employees so you don't pick someone who's offboarded.

```bash Terminal theme={"system"}
curl 'https://api.vanta.com/v1/people?pageSize=100&employmentStatus=CURRENT' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer YOUR_TOKEN'
```

Response

```json theme={"system"}
{
  "results": {
    "data": [
      {
        "id": "5fc82421a228f6b6f713547d",
        "emailAddress": "developers@vanta.com",
        "name": { "display": "Alejandro Ocampo" },
        "employment": { "status": "CURRENT", "jobTitle": "Security Engineer" }
      }
    ]
  }
}
```

Copy the `id`. You'll send it as `ownerId` in the next step.

> [accordion] Can't find the user?
>
> Filter client-side by `emailAddress` (most reliable), or paginate with `pageCursor` if `hasNextPage` is `true`. You can also copy a user's ID directly from their profile URL on the [People page](https://app.vanta.com/people/people).

> [accordion] They show as `FORMER`?
>
> They've been offboarded and aren't eligible to own resources. Pick a `CURRENT` user instead.

**3. Update owner and description in bulk**

**Your terminal** — `PATCH /v1/integrations/{integrationId}/resource-kinds/{resourceKind}/resources` with an `updates` array. Each entry is keyed by the resource `id` and may set `ownerId`, `description`, and/or `inScope`.

```javascript Node.js theme={"system"}
const INTEGRATION_ID = "snowflake";
const RESOURCE_KIND = "SnowflakeDatabase";
const OWNER_ID = "5fc82421a228f6b6f713547d";

const res = await fetch(
  `https://api.vanta.com/v1/integrations/${INTEGRATION_ID}/resource-kinds/${RESOURCE_KIND}/resources`,
  {
    method: "PATCH",
    headers: {
      "Content-Type": "application/json",
      Authorization: "Bearer YOUR_TOKEN",
    },
    body: JSON.stringify({
      updates: [
        {
          id: "64dc848b6491f66d23c64df6",
          ownerId: OWNER_ID,
          description: "Primary Snowflake warehouse for analytics",
        },
        {
          id: "64dc848b6491f66d23c64e26",
          ownerId: OWNER_ID,
          description: "Sample dataset – read-only",
        },
      ],
    }),
  },
);
console.log(await res.json());
```

```python Python theme={"system"}
import requests

INTEGRATION_ID = "snowflake"
RESOURCE_KIND = "SnowflakeDatabase"
OWNER_ID = "5fc82421a228f6b6f713547d"

r = requests.patch(
    f"https://api.vanta.com/v1/integrations/{INTEGRATION_ID}/resource-kinds/{RESOURCE_KIND}/resources",
    headers={"Authorization": "Bearer YOUR_TOKEN"},
    json={
        "updates": [
            {
                "id": "64dc848b6491f66d23c64df6",
                "ownerId": OWNER_ID,
                "description": "Primary Snowflake warehouse for analytics",
            },
            {
                "id": "64dc848b6491f66d23c64e26",
                "ownerId": OWNER_ID,
                "description": "Sample dataset – read-only",
            },
        ]
    },
)
r.raise_for_status()
print(r.json())
```

```bash Terminal theme={"system"}
curl -X PATCH 'https://api.vanta.com/v1/integrations/snowflake/resource-kinds/SnowflakeDatabase/resources' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -d '{
    "updates": [
      { "id": "64dc848b6491f66d23c64df6", "ownerId": "5fc82421a228f6b6f713547d", "description": "Primary Snowflake warehouse for analytics" },
      { "id": "64dc848b6491f66d23c64e26", "ownerId": "5fc82421a228f6b6f713547d", "description": "Sample dataset – read-only" }
    ]
  }'
```

Expected response (`200`) — a per-resource result, so you can tell which updates failed:

```json theme={"system"}
{
  "results": [
    { "id": "64dc848b6491f66d23c64df6", "status": "SUCCESS" },
    { "id": "64dc848b6491f66d23c64e26", "status": "SUCCESS" }
  ]
}
```

> [!WARNING]
>
> The bulk endpoint accepts up to **50** resources per call. Page through Step 1 and call this endpoint in batches if you have more.

> [accordion] Got an `ERROR` in `results`?
>
> The `message` field tells you which update failed and why — typically because `ownerId` is `FORMER`, the `id` doesn't belong to that `(integrationId, resourceKind)`, or the resource kind doesn't support `description`. Successful entries are still applied; only fix and retry the failures.

> [accordion] Got a 404?
>
> The `integrationId` or `resourceKind` is wrong. They're case-sensitive — `snowflake` and `SnowflakeDatabase` are different fields. Re-run Step 1 to confirm the exact spellings.

> [accordion] Got a 403?
>
> Your token has `vanta-api.all:read` but not `vanta-api.all:write`. Mint a token with both scopes.

> [!NOTE]
>
> **Single-resource update?** Use `PATCH /v1/integrations/{integrationId}/resource-kinds/{resourceKind}/resources/{resourceId}` with `{ "ownerId": "...", "description": "..." }` instead. It returns `204 No Content` on success.

## Congratulations

You've assigned active owners and descriptions to your inventory resources. Those resources will now pass the **Inventory items have active owners** and **Inventory items have descriptions** tests, and the changes are captured in your audit log.

## Next steps

> [card] [Scope resources in or out](https://developer.vanta.com/docs/guides/scope-resources-at-the-integration-level.md)
>
> Mark resources `inScope: false` to exclude them from tests entirely.

> [card] [Assign a control owner](https://developer.vanta.com/docs/guides/add-an-owner-to-a-control.md)
>
> Make a specific user accountable for the controls these resources support.

> [card] [Try it in Postman](https://developer.vanta.com/docs/postman-setup.md)
>
> Import the collection and run the bulk PATCH against a sandbox in seconds.

> [card] [Manage Vanta API reference](https://developer.vanta.com/reference/manage-vanta/overview.md)
>
> Browse every Manage Vanta endpoint — controls, tests, documents, people, integrations.


## Related topics

- [Add Trust Center resource category](https://developer.vanta.com/api-reference/trust-centers/add-trust-center-resource-category.md)
- [Scope resources in or out](https://developer.vanta.com/docs/guides/scope-resources-at-the-integration-level.md)
- [Find failing tests](https://developer.vanta.com/docs/guides/query-test-results-and-filter-for-failing-resources.md)
- [Manage Vanta API](https://developer.vanta.com/reference/manage-vanta/overview.md)
- [List resources](https://developer.vanta.com/api-reference/integrations/list-resources.md)
