Crate ruma_client_api

source ·
Expand description

(De)serializable types for the Matrix Client-Server API. These types can be shared by client and server code.

Re-exports§

Modules§

  • Endpoints for account registration and management.
  • Endpoints for room aliases.
  • Endpoints part of the application service extension of the client-server API
  • Authenticated endpoints for the content repository.
  • Endpoints for server-side key backups.
  • Endpoints for client configuration.
  • Endpoints for event context.
  • Endpoints for managing dehydrated devices.
  • Endpoints for sending and interacting with delayed events.
  • Endpoints for managing devices.
  • Endpoints for the public room directory.
  • Server discovery endpoints.
  • Errors that can be sent from the homeserver.
  • Endpoints for event filters.
  • Helpers for HTTP headers with the http crate.
  • Endpoints for key management
  • Endpoints to knock on a room.
  • Endpoints and helpers for the media repository.
  • Endpoints for room membership.
  • Endpoints for sending and receiving messages
  • Endpoints for user presence.
  • Endpoints for user profiles.
  • Endpoints for push notifications.
  • Endpoints for “fully read markers”
  • Endpoints for event receipts.
  • Endpoints for event redaction.
  • Endpoints for querying relations
  • Endpoints for room management.
  • Endpoints for event searches.
  • Endpoints for server administration.
  • Endpoints for user session management.
  • Endpoints for spaces.
  • Endpoints for managing room state
  • Endpoints for getting and synchronizing events.
  • Endpoints for tagging rooms.
  • Endpoints for third party lookups
  • Endpoints for querying threads in a room.
  • Endpoints for client devices to exchange information not persisted in room DAG.
  • Endpoints for typing notifications.
  • Endpoints for the user directory.
  • Endpoints for Voice over IP.