---
search:
  tags:
    - Roles and permissions
    - POST
seo:
  description: >-
    Answers each check for the caller, for example to show… Reference for the
    POST /organizations/{organizationId}/permission-checks endpoint in the Auth
    API.
sidebar:
  label: Check the caller's Permissions
  badge: POST
title: Check the caller's Permissions
type: openapi-operation
---
Answers each check for the caller, for example to show only the actions they may take. Requires being a member. Organization Permissions (organization, member, invitation, team, ac, audit) take no context. Permissions on Platform API resources are checked on the resource named by its own context ID, on the project for an environment check with only `project_id`, or else on the organization; a read without context is allowed when the caller can read any resource of that type in the organization. Resources outside the organization answer false.

`POST /organizations/{organizationId}/permission-checks`

**Request body** (`application/json`, required)

- `checks` (permission_check[], required)

Request body example:

```json
{
  "checks": [
    {
      "permission": "string",
      "project_id": "405d8375-3514-403b-8c43-83ae74cfe0e9",
      "environment_id": "40ef0e48-a11f-4963-a229-e396c9f7e7c4",
      "cluster_id": "d3d1bfdf-67c4-41fa-b065-858242731616",
      "integration_id": "55d7337e-1d0a-49fc-9826-925ba40df035"
    }
  ]
}
```

**Responses**

- `200` — One answer per check, in order.
- `default` — The request failed.

Response example, 200:

```json
{
  "allowed": [
    true
  ]
}
```
