Get group settings (announce / locked / ephemeral timer)
GET/api/sessions/:sessionId/groups/:groupId/settings
Get group settings (announce / locked / ephemeral timer)
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 503
Group settings
The session is not started: no engine is running for it (never started, stopped, or logged out). Start the session and retry.
The API key is missing, unknown, revoked, or expired
The API key is restricted to selected chats and this group is outside its allowlist. Also returned when the API key's role, session or chat scope, or IP allow-list does not allow this operation.
Group not found
The session is not connected: an engine exists for it but is not ready, meaning disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A session that was never started answers 400 instead, and the session lifecycle routes answer 409 for a conflicting state rather than this. One window answers this while the session still reads ready: WhatsApp Web periodically reloads its own page and the engine re-injects into it, and for those few seconds the answer is a 409 naming the reload; retry shortly.
WhatsApp did not answer within the request budget — nothing could be read. On Baileys, also answered when WhatsApp rate-limits or times out the request (code 429 or 408); retry after a pause.