---
title: "List Account Authorizations For Function"
method: GET
path: "/v2/nvcf/authorizations/functions/{functionId}"
tags: ["Authorized Accounts"]
---

# List Account Authorizations For Function

`GET /v2/nvcf/authorizations/functions/{functionId}`

Lists NVIDIA Cloud Account IDs that are authorized to invoke any version of the  specified function. The response includes an array showing authorized accounts  for each version. Individual versions of a function can have their own  authorized accounts. So, each object in the array can have different  authorized accounts listed. Access to this functionality mandates the inclusion of a bearer token with the  'authorize_clients' scope in the HTTP Authorization header

## Path parameters

- `functionId` string, uuid, required

## Response `200`

OK

- ListAuthorizedPartiesResponse — Parties authorized to invoke function
  - `functions` AuthorizedPartiesByFunctionDto[], required — Functions with authorized parties and other details
    - `id` string, uuid, required — Function id
    - `ncaId` string, required — NVIDIA Cloud Account Id
    - `versionId` string, uuid — Function version id
    - `authorizedParties` AuthorizedPartyDto[] — Authorized parties allowed to invoke the function
      - `clientId` string — Client Id -- 'sub' claim in the JWT. This field should not be specified anymore.
      - `ncaId` string, required — NVIDIA Cloud Account authorized to invoke the function

---

[API](https://skmtc.dev/brevdev/apis/cloud-functions.md) · [All operations](https://skmtc.dev/brevdev/apis/cloud-functions/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/brevdev/cloud-functions/revisions/add37b001ffc/schema)