PLEXICHATNarrative Docs

API Reference

Guides, route-group overviews, and live schema entry points for the Plexichat backend.

REST http://api.plexichat.com/api/v1Gateway ws://api.plexichat.com/gatewayVersion a.1.0-49

REST API Reference

This section organizes the backend REST API by route group. For exact request and response schemas, use the generated OpenAPI docs at /docs.

Base URL

All routes in this section are relative to https://api.plexichat.com.

Public Utility Endpoints

EndpointPurpose
GET /healthreadiness and health signal
GET /versioncurrent backend version
POST /version/negotiateclient compatibility negotiation
GET /statusoperational or maintenance status
GET /capabilitiespublic runtime constants and feature hints
GET /qrlocal QR code generation

Authenticated Product Areas

Route groupPurpose
Authenticationregistration, login, sessions, 2FA, recovery
Usersprofiles, notes, presence, self-service user actions
Settingssynced user preference storage
Relationshipsfriends, blocks, and relationship state
Serversservers, members, roles, invites, structure
Channelschannel management and channel-scoped actions
Messagesmessage CRUD, pins, acks, and attachments
Reactionsmessage reactions and reaction user lists
Presencepresence retrieval and updates
Webhookswebhook management and execution
Avatarsuser and server avatar endpoints
Emojiscustom emoji management
Featurespublic feature visibility plus admin-controlled tiers/badges

Additional Route Groups

Route groupRoutes covered
Search/search/messages, /search/users, /search/servers
Notificationscurrent-user notification reads and read markers
Pollspoll creation, voting, results, close, delete
VoiceICE server discovery and voice channel info
Mediahash reporting, resumable upload sessions, compression status
Reportsuser and message reporting
Feedbackfeedback submission and status checks
Telemetryresponse-time and CSP telemetry ingestion
Systemcapabilities, help pages, QR, health, status, version
Adminoperator-only admin authentication, review, security, telemetry, and UI routes

Notes

  • Some endpoints require normal authentication plus an API access token depending on server policy.
  • The public narrative docs intentionally avoid private infrastructure and operator-only procedures.
  • Administrative routes are mounted at a configurable root path and are documented separately in Admin.