GoliathDevelopersGet an API key
Reference/Teamgenerated from the gateway manifest

getTeamMemberCapabilities

A teammate's permissions, as Manage permissions on their row shows them.

POST/api/v1/callADMINreadruns as the key's owner
View as Markdown

A teammate's permissions, as Manage permissions on their row shows them: every capability they HOLD (one missing is one they do not have). userId comes from listTeamMembers. An Admin holds all of them. Read it before grantTeamMemberCapability or revokeTeamMemberCapability to say what changes. Organization admins only; your own permissions are getMyCapabilities.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "getTeamMemberCapabilities",
    "variables": {
      "userId": "<userId>"
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.team.getTeamMemberCapabilities({
  userId: '<userId>'
})
const res = await fetch('https://server.goliathdata.com/api/v1/call', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    operationId: 'getTeamMemberCapabilities',
    variables: {
      userId: '<userId>'
    }
  }),
})
const { data, errors } = await res.json()

Variables

The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.

userIdID!required

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "teamQuery": {
      "getTeamMemberCapabilities": [
        "VIEW_ALL_CONTACTS"
      ]
    }
  }
}

Errors

Behaviour

A read. It rejects an Idempotency-Key header with 400 bad_request.