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.
Recall also enforces a trusted sent-time window (48 hours on the official recall methods). Missing / expired messages →
400; insufficient permission →403.
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.
Related
API method matrix
Core concepts / Privacy Mode in groups
User guide: how commands rank when multiple bots share a group