---
title: "Check Access"
method: GET
path: "/api/v2/authz/access/{action}"
tags: ["Authorization"]
---

# Check Access

`GET /api/v2/authz/access/{action}`

Allows the requesting user to check whether an access check will fail or succeed.
Useful to conditionally disable parts of the UI that are known to be inaccessible.

## Path parameters

- `action` 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | 315 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415, required — The integer values for the authorization actions are stored directly in the DB. This means you can change the name of the actions, but not their integer values. The values for the actions are spaced on purpose, to make it easier to extend. This has no technical benefit, but it makes it easier to read for developers.

## Query parameters

- `resource` string, uuid
- `domain` string, uuid

## Response `200`

Access check result

- AccessResponse
  - `allowed` boolean, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/conveyordata/apis/data-product-portal.md) · [All operations](https://skmtc.net/conveyordata/apis/data-product-portal/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/conveyordata/data-product-portal/revisions/0fe6374dedc9/schema)