In short
Bots can read group metadata and member profiles via the getChat* family, and — with the right admin rights — delete or recall ordinary members’ messages. Owner/admin messages cannot be recalled by another admin bot. Prefer official field lists on core.mp.net/bots.
Overview
Treat this as an index of capabilities. Exact response fields and error codes: core.mp.net/bots.
Readable group info
Group title and avatar.
Member avatar, display name, and username (when present).
How you sort or present members is your product choice — the API returns data; it does not impose a UI order.
Method index
Method | Typical use |
| Chat title, photo, and basic chat fields. |
| List administrators for the chat. |
| One member’s status / profile fields. |
| Member count for the chat. |
Field-level paths follow the official Chat / ChatMember types — do not invent names.
Delete member chat content
With sufficient rights, a bot can remove messages from the group history. If a deleted message is still referenced elsewhere, clients show a “deleted message” placeholder.
Recall vs delete
recallMessage/recallMessagesare MPChat extensions for recall semantics.deleteMessage/deleteMessagesremain the compatible delete methods (DocOnly / compatibility boundary — keep both in mind when reading older samples).As an administrator with Recall permission, a bot may recall regular members’ messages, but not messages from the owner or other administrators.
Delete and recall enforce a 48-hour window based on the trusted sent time. Invalid or expired targets can return
400. Insufficient permission returns403.
Permission errors
Expect 403 when the bot lacks membership or admin rights, and 400 for invalid ids / expired recall targets. Always confirm against the live method page before hard-coding client copy.
Group events and join requests
Kafka-sourced group events and join-request actions are documented as pre-release. Confirm deployment before relying on them. Use the Webhook or polling guide to configure the update types you need.