docs: document X (Twitter) + LinkedIn connectors (chat#1793)

Merged
SW
4mo ago
+4-4

What

Adds X (Twitter) and LinkedIn to the connectors contract in api-reference/openapi/social.json, so the connectors endpoints document both new platforms.

Additive description edits only (4 spots) — no schema or structure changes:

  • GET /api/connectors description — supported-integrations list
  • AuthorizeConnectorRequest.connector slug examples
  • ConnectorInfo.slug examples
  • connector-actions slug examples

Why

This is PR #1 (the contract) in the docs→api merge order for recoupable/chat#1793 (Add X + LinkedIn connectors via the existing Composio whitelist pattern). Documentation-driven development: the docs contract lands first, then api implements against it.

Merge order

  1. docs (this PR) — contract
  2. api — whitelist constants (SUPPORTED_TOOLKITS, ENABLED_TOOLKITS, CONNECTOR_DISPLAY_NAMES, buildAuthConfigs())
  3. api + chat — artist-vs-label availability

Verification

  • social.json parses as valid JSON.
  • Diff is 4 insertions / 4 deletions, additive only (verified git diff).

Tracking issue: recoupable/chat#1793

🤖 Generated with Claude Code

Summary by cubic

Documented X (Twitter) and LinkedIn connectors in the OpenAPI contract, updating api-reference/openapi/social.json so connectors endpoints list and examples include these platforms. No schema or structure changes; this lands the contract ahead of API enablement for recoupable/chat#1793.