WhatsApp Gateway
API referenceGroups

Approve pending join requests (not implemented in v2)

**Not implemented in v2.** Approving people waiting to join a group is not part of v2's live WhatsApp surface, so this endpoint **always responds 501 `not_implemented`** regardless of the request body. The route and `participants` body shape are reserved for a future release. **Capability:** requires `send` (checked before the 501 is returned).

POST
/api/v1/sessions/{session}/groups/{gid}/members:approve

Authorization

AuthorizationBearer <token>

Send Authorization: Bearer <token>. The router accepts two kinds of token and tries each in turn: a frontend-minted login JWT (verified against the frontend JWKS; the person's org + role are read from it), or an api-key for a script/service (carrying a fixed set of gateway permissions). The bearerFormat: JWT label describes the person-login case.

In: header

Path Parameters

session*string

The WhatsApp session id that owns the group. Note: this endpoint is not implemented in v2 and always returns 501 not_implemented regardless of input.

gid*string

The group's JID, ending in @g.us. Not implemented in v2 (always 501).

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

participants?array<string>|

User JIDs of pending join requests to approve. Not implemented in v2 (always 501); this field is accepted but never acted on.

Response Body

application/json

curl -X POST "https://example.com/api/v1/sessions/01HZ0SESSION0000000000000/groups/120363041234567890@g.us/members:approve" \  -H "Content-Type: application/json" \  -d '{}'
Empty
{  "error": {    "code": "not_found",    "details": {      "property1": null,      "property2": null    },    "message": "session not found"  }}