API Reference

Groups

List group join requests

Lists pending join requests for a group with join approval enabled. Pass group_id as a query parameter. Upstream push events are not guaranteed, so poll this endpoint as the reliable source.

GEThttps://api.unifyport.ai/v1/accounts/{account_id}/groups/join-requests

Before you call

Use a server-side X-Api-Key for the workspace that owns the resource. Replace every placeholder before running a sample.

Prepare your parameters
account_id
Use data.id from account creation or an account query. Account identifiers belong to the workspace selected by X-Api-Key. Get account
group_id
Group to act on — the id returned by List groups. Kept in the query string because provider ids may contain @ or :.

Request parameters

Headers

X-Api-Key
stringrequired

Workspace API key. The workspace is resolved from this header.

Path parameters

account_id
stringrequired

Identifier used in the groups route.

Query parameters

group_id
stringrequired

Group to act on — the id returned by List groups. Kept in the query string because provider ids may contain @ or :.

Request body

This endpoint does not require a JSON request body.

Understand the result

Use the documented response fields and HTTP status. Successful 204 responses have no body; use X-Request-Id for diagnosis. Follow the related operations for the next step.

Response 200 OK

{
  "request_id": "<REQUEST_ID>",
  "data": {
    "group_id": "group_example",
    "items": [
      {
        "id": "member_example",
        "phone": "8613912345678",
        "requested_at": "2026-06-08T12:34:56Z"
      }
    ]
  }
}

Response body

id
string

Join request identifier; pass it as member_ids when approving or rejecting.

phone
string

Phone number of the requester, when the provider exposes it.

lid
string

Provider LID for the requester, when available.

requested_at
string

RFC3339 timestamp of when the join was requested.

format: date-time

group_id
string

Group the join requests belong to.

Responses

200

200 OK

Request succeeded. See the example response body.

400

Bad Request

The request body, path, or parameters are invalid.

401

Unauthorized

The X-Api-Key header is missing or invalid.

404

Not Found

The requested provider resource could not be found.

409

Conflict

The requested operation conflicts with an existing provider account or resource.

500

Internal Server Error

The service encountered an unexpected error.

501

Not Implemented

The selected provider does not implement this operation.

502

Bad Gateway

The provider adapter or upstream provider could not complete the operation.

If the request fails

Inspect HTTP status and error.code/numeric_code, and keep request_id for diagnosis. Correct invalid parameters, complete required authorization or check runtime state as appropriate. Confirm the outcome before retrying a send or another write. Error reference

invalid_request · 10000 · 400
Check required fields, formats and channel conditions, then correct the request.
invalid_api_key · 11001 · 401
Check X-Api-Key and whether the workspace is active.