Social and Integrations

Read The Route Group

Use this guide when a route, request, response, permission model, integration, or deployment behavior needs to be understood before people rely on it. In this guide, Social and Integrations narrows that work to discord, Telegram, social account linking, state tokens, member tags, roles, and ZEP access. Includes generated capability references from the platform inventory. Because this is a capability reference page, read it as part of the Platform adoption learning path rather than as an isolated checklist.

An API is a contract between systems. Even technical changes can affect attendee records, dashboard behavior, notifications, payments, files, or staff tools. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What These Routes Control

This page is for adoption teams and reviewers who need to understand a group of endpoints. Read each route as a promise between a caller and the records it can read or change. The intended readers are partner administrators, event leads, adoption leads, and integration owners. If the guide names a dashboard screen, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: partners-api.
• Records or contracts involved: API service expectations, Auth state, and Platform records.
• Main care point: Watch for using a service route with the wrong actor, changing a response another app depends on, leaking a secret, or triggering the same side effect twice.
• Proof worth keeping: route inventory, method and path, auth model, request and response shape, platform owner confirmation, test result, consumer note, and deployment evidence.

Trace Caller, Permission, And Result

1. Identify the caller and product area: Begin by naming the Platform adoption situation, the owner, and the exact item involved in Social and Integrations.
2. Check the method, path, auth, and inputs together: Use partners-api to connect the words on the page to the screen, file, route, or service trail that people actually use.
3. Look for records and side effects: Keep API service expectations, Auth state, and Platform records in view so the work stays tied to the records or contracts it can affect.
4. Verify tests and consumers before changing behavior: Before handing off, save proof such as route inventory, method and path, auth model, request and response shape, platform owner confirmation, test result, consumer note, and deployment evidence so an adoption lead and a non-specialist reviewer can understand what the route does and how it was verified.

Before Depending On The Route

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on callers, records, permissions, secrets, side effects, and downstream apps.
3. Proof is findable: The handoff points to evidence that an adoption lead and a non-specialist reviewer can understand what the route does and how it was verified.

End-to-end adoption runbook

1. Step 1 - Name the API workflow and owner: Identify the product area, organization owner, service path, and relying team before adopting a workflow or integration.
2. Step 2 - Read the contract in human terms: Check who can use it, what information is exchanged, what can fail, what records change, and what proof the adopting team must keep.
3. Step 3 - Prepare auth and input deliberately: Confirm the right role, account, partner, event, and approved data before depending on the workflow.
4. Step 4 - Use or request the route in the right environment: Use the approved dashboard, rego, LAN, or integration environment and keep credentials out of notes, screenshots, and exports.
5. Step 5 - Check returned data and real side effects: Confirm the visible result, affected records, external action, and review evidence in plain language.
6. Step 6 - Record tests, docs, and handoff notes: Record the owner, expected behavior, adoption evidence, and escalation path before relying on it in production.

Family summary

Discord, Telegram, social account linking, state tokens, member tags, roles, and ZEP access.

Modules audited

• social.ts: 11 generated capability entries.
• socialLinking.ts: 30 generated capability entries.
• zep.ts: 9 generated capability entries.

Capability table

Method	Path	Service area	Access note	Internal trace
GET	/api/events/:id/social/bot-settings	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1642
PATCH	/api/events/:id/social/bot-settings	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1683
GET	/api/events/:id/social/discord/guilds	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1524
GET	/api/events/:id/social/discord/guilds/:guildId/roles	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1545
GET	/api/events/:id/social/discord/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1449
GET	/api/events/:id/social/telegram/chats	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1581
POST	/api/events/:id/social/telegram/link/complete	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1709
GET	/api/events/:id/social/telegram/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1479
GET	/api/events/:id/zep/app-bundle	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:486
GET	/api/events/:id/zep/config	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:424
PUT	/api/events/:id/zep/config	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:503
POST	/api/internal/social-entitlements/reconcile	socialLinking.ts	Internal cron secret required.	partners-api/src/routes/socialLinking.ts:2066
GET	/api/manage/:id/social/bot-settings	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1642
PATCH	/api/manage/:id/social/bot-settings	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1683
GET	/api/manage/:id/social/discord/guilds	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1524
GET	/api/manage/:id/social/discord/guilds/:guildId/roles	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1545
GET	/api/manage/:id/social/discord/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1449
GET	/api/manage/:id/social/telegram/chats	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1581
POST	/api/manage/:id/social/telegram/link/complete	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1709
GET	/api/manage/:id/social/telegram/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1479
GET	/api/manage/:id/zep/app-bundle	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:486
GET	/api/manage/:id/zep/config	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:424
PUT	/api/manage/:id/zep/config	zep.ts	Partner dashboard session required.	partners-api/src/routes/zep.ts:503
DELETE	/api/org/social/discord/guilds/:guildId	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1602
GET	/api/org/social/discord/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1278
POST	/api/org/social/discord/unlink	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1308
GET	/api/org/social/settings	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1238
POST	/api/org/social/telegram/chat/link/complete	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1423
GET	/api/org/social/telegram/chat/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1382
DELETE	/api/org/social/telegram/chats/:chatId	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1622
GET	/api/org/social/telegram/link/start	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1328
POST	/api/org/social/telegram/unlink	socialLinking.ts	Partner dashboard session required.	partners-api/src/routes/socialLinking.ts:1362
GET	/api/rego/friends	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:183
DELETE	/api/rego/friends/:id	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:559
PATCH	/api/rego/friends/:id/accept	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:418
PATCH	/api/rego/friends/:id/decline	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:488
GET	/api/rego/friends/events	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:673
POST	/api/rego/friends/request	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:301
GET	/api/rego/friends/requests	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:241
GET	/api/rego/friends/sent	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:271
GET	/api/rego/social/discord/link/start	socialLinking.ts	Rego attendee session required.	partners-api/src/routes/socialLinking.ts:1132
POST	/api/rego/social/discord/unlink	socialLinking.ts	Rego attendee session required.	partners-api/src/routes/socialLinking.ts:1188
GET	/api/rego/social/settings	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:58
PATCH	/api/rego/social/settings	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:81
GET	/api/rego/social/telegram/link/start	socialLinking.ts	Rego attendee session required.	partners-api/src/routes/socialLinking.ts:1158
POST	/api/rego/social/telegram/unlink	socialLinking.ts	Rego attendee session required.	partners-api/src/routes/socialLinking.ts:1213
GET	/api/rego/users/search	social.ts	Rego attendee session required.	partners-api/src/routes/social.ts:129
POST	/api/rego/zep/launch	zep.ts	Rego attendee session required.	partners-api/src/routes/zep.ts:697
GET	/api/rego/zep/status	zep.ts	Rego attendee session required.	partners-api/src/routes/zep.ts:682
POST	/api/zep/validate	zep.ts	Unknown from inventory scan; ask the platform owner to confirm access behavior before use.	partners-api/src/routes/zep.ts:730

Endpoint contract notes

1. Action 1 - Verify unknowns: The table is inventory-generated, but fields marked unknown need platform-owner review.
2. Action 2 - Check internal trace: Use the internal trace as an escalation pointer when exact request, response, or side-effect behavior must be confirmed.
3. Action 3 - Review consumers: Search dashboard, rego, EMS LAN, and webhook callers before changing a path or response.
4. Action 4 - Update inventory: Ask the platform owner to refresh the inventory after any platform route change.