Update group settings (announce / locked / ephemeral timer)
PUT/api/sessions/:sessionId/groups/:groupId/settings
Update group settings (announce / locked / ephemeral timer)
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 501
- 503
Group settings updated
No setting provided, or a value is not a boolean
The API key is missing, unknown, revoked, or expired
The engine refused the change (the account is not a group admin). 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.
The active engine does not support a requested setting
WhatsApp did not answer within the request budget. The change may or may not have been applied — the gateway stopped waiting for a confirmation that never came. On Baileys, also answered when WhatsApp rate-limits or times out the request (code 429 or 408); retry after a pause.