Read what Synq did in the org’s Discord servers and Telegram groups
Newest first: people checked for a role or a group (`user.token_gate_checked` with `at` `discord` or `telegram`), members recognized with no link because their account was linked at the brand already (`discord_role.recognized`, `telegram_member.recognized`), roles given and removed, join requests approved and declined, people muted and removed, people an admin banned, whom Synq leaves as they are (`telegram_member.banned_by_admin`), people an admin muted, whom Synq never unmutes (`telegram_member.muted_by_admin`), failures with their fix, and servers and groups connected and disconnected. Each row is an audit row, as webhooks get it, and never holds a wallet address. `kind` keeps one of the dashboard's filters. Needs `org.integrations.view`.
/v1/orgs/{org}/integrations/activityNewest first: people checked for a role or a group (user.token_gate_checked with at discord or telegram), members recognized with no link because their account was linked at the brand already (discord_role.recognized, telegram_member.recognized), roles given and removed, join requests approved and declined, people muted and removed, people an admin banned, whom Synq leaves as they are (telegram_member.banned_by_admin), people an admin muted, whom Synq never unmutes (telegram_member.muted_by_admin), failures with their fix, and servers and groups connected and disconnected. Each row is an audit row, as webhooks get it, and never holds a wallet address. kind keeps one of the dashboard's filters. Needs org.integrations.view.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$Query Parameters
At most this many items, 200 at the most.
1 <= value <= 20050The previous page's next_cursor, for the page after it.
verified (checks passed, and members recognized), refused, granted (roles given, requests approved, people unmuted), removed (removals scheduled and done, mutes, declined requests), failed or connections; every row when left out
Value in
- "verified"
- "refused"
- "granted"
- "removed"
- "failed"
- "connections"
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/integrations/activity" \ -H "Authorization: Bearer $SYNQ_API_KEY"{ "data": [ { "id": "aud_01h455vb4pex5vsknk084sn02q", "created_at": "2026-10-21T12:00:00.000Z", "action": "org.updated", "actor": { "type": "member", "id": "usr_01h455vb4pex5vsknk084sn02q" }, "act_client_id": "string", "approval_id": "string", "brand_id": "brd_01h455vb4pex5vsknk084sn02q", "resource": { "type": "org", "id": "org_01h455vb4pex5vsknk084sn02q" }, "metadata": {}, "ip": "string", "user_agent": "string" } ], "next_cursor": "string"}List who left an org GET
Everyone who left the org or was removed from it and isn't a member again, newest first: who they were, the role they had, when they joined and left, and whether they left themselves or who removed them. Read from the audit log's `member.left` and `member.removed` entries, so it reaches as far back as the org's plan keeps its log (`audit_retention_days` in `GET /v1/plans`). Their access ended when they went; filter the audit log by their `user_id` (`actor`) to see what they did. Needs `org.members.view`.
List what the caller may do in an org GET
The caller's own permissions in the org: across the org (`permissions`: a member's org role's, or an API key's own) and in its brands (`brand_permissions`: on All brands, and in each brand it holds a role in beside those). Needs no permission, only to be in the org, so a dashboard can offer only what its person may do. Every other route still checks its own.