Add permissions to an organization team role (single or batch)

POST /v2/organizations/{orgId}/teams/{teamId}/roles/{roleId}/permissions

Add permissions to an organization team role (single or batch)

cURL

curl --request POST \
  --url https://api.cal.com/v2/organizations/{orgId}/teams/{teamId}/roles/{roleId}/permissions \
  --header 'Content-Type: application/json' \
  --data '
{
  "permissions": [
    "eventType.read",
    "booking.read"
  ]
}
'

200

{
  "status": "success",
  "data": [
    "<string>"
  ]
}

Headers

Authorization · string

For non-platform customers - value must be Bearer <token> where <token> is api key prefixed with cal_

x-cal-secret-key · string

For platform customers - OAuth client secret key

x-cal-client-id · string

For platform customers - OAuth client ID

Path Parameters

orgId · number · required

teamId · number · required

roleId · string · required

Body

application/json

permissions · enum<string>[] · required

Permissions to add (format: resource.action)

Available options: role.create, role.read, role.update, role.delete, eventType.create, eventType.read, eventType.update, eventType.delete, team.read, team.update, team.delete, team.invite, team.remove, team.listMembers, team.listMembersPrivate, team.changeMemberRole, team.impersonate, booking.read, booking.readTeamBookings, booking.readRecordings, booking.update, booking.readTeamAuditLogs, insights.read, workflow.create, workflow.read, workflow.update, workflow.delete, routingForm.create, routingForm.read, routingForm.update, routingForm.delete, webhook.create, webhook.read, webhook.update, webhook.delete, featureOptIn.read, featureOptIn.update

Example:

["eventType.read", "booking.read"]

Response

200 - application/json

status · string · required

Example:

"success"

data · string[] · required