Key and workspace

One call that tells an integration which workspace a key belongs to and whether writes will work. Zapier and Make use it to test a connection.

Updated September 26, 2026

Key and workspace

GET/api/v1/me

Which workspace (brand) a key belongs to. Integrations use it to test a connection.

can_act is false when actions would answer 403, because the person who created the key left or can no longer moderate. created_by is null when they left.

Who can call it: Any API key.

Example

Request

curl https://commentgate.com/api/v1/me \
  -H "Authorization: Bearer $COMMENTGATE_API_KEY"

200 OK. The key and its workspace.

200 OK response

{
  "data": {
    "workspace": {
      "id": "a5bf2b64-1c0e-4f8a-9d3b-2e7c6f5a4b19",
      "name": "Wildermere"
    },
    "key": {
      "id": "3ac0fccd-7e21-4b9d-8f6a-1d2c3b4a5e6f",
      "name": "Zapier",
      "prefix": "cg_live_qwn7"
    },
    "created_by": {
      "name": "Jordan Hayes"
    },
    "can_act": true
  }
}

Errors

HTTP	Code	When
401	`unauthorized`	Missing, unknown or revoked key

Also as whoami (MCP), commentgate whoami.