Skip to main content
GET
/
user
/
connections
List the API key owner's connections
curl --request GET \
  --url https://teambattles.gg/api/v1/user/connections \
  --header 'Authorization: Bearer <token>'
{
  "connections": [
    {
      "id": "<string>",
      "platform": "<string>",
      "isSelfReported": true,
      "showOnProfile": true,
      "username": "<string>",
      "url": "<string>",
      "isPrimary": true,
      "isVerified": true,
      "connectedAt": "<string>",
      "region": "<string>",
      "gamingPlatform": "<string>"
    }
  ],
  "count": 4503599627370495,
  "timestamp": "<string>"
}

​
Permission Required

This endpoint requires users.profile with read access on your API key. The user is always the API key owner, derived from the key itself - it is never accepted as a parameter, so a key can only read its own connections.

​
Access / Membership Rules

This is a self-read route. The owner is always derived from principal.user._id, so there is no membership or participant gating - the key reads exactly the owner’s own data. Unlike the public /users/{id}/connections endpoint, no showOnProfile filter is applied: the full set is returned, including the owner-only isSelfReported and showOnProfile fields.

​
What’s Returned

Returns a list envelope with a connections array. Each entry is the API-safe owner-connection projection, which includes the owner-only isSelfReported and showOnProfile flags alongside the public connection fields. Mintlify renders the full schema from the spec below.

Authorizations

​
Authorization
string
header
required

Send your API key as: Authorization: Bearer tb_

Response

The API key owner's connections.

Envelope containing connections, count, and a response timestamp.

​
connections
object[]
required
​
count
integer
required
Required range: 0 <= x <= 9007199254740991
​
timestamp
string
required

ISO 8601 timestamp.