Skip to main content
POST
Block a member

Authorizations

Api-Token
string
header
required

Server-to-server authentication. Generate a token in the admin UI at Settings → Developers → API Access. Send the raw token in the Api-Token header — there is no Bearer prefix.

Tokens can be marked read-only at creation time, in which case the API rejects any non-GET request with 403 Forbidden.

Body

application/json

The new UserBlock resource

A one-way block: $blocker no longer sees content authored by $blocked.

Mirrors UserFollowDiscussion (the other Discuss-module join entity): integer identifier, no uuid, so the resource IRIs match /posts/{id} and the rest of the module.

blocker
string<iri-reference>
Example:

"/api/v1/users/1"

blocked
string<iri-reference>
Example:

"/api/v1/users/1"

tenant
string<iri-reference>
Example:

"/api/v1/tenants/1"

Response

UserBlock resource created

A one-way block: $blocker no longer sees content authored by $blocked.

Mirrors UserFollowDiscussion (the other Discuss-module join entity): integer identifier, no uuid, so the resource IRIs match /posts/{id} and the rest of the module.

id
integer
read-only
blocked
object
dateCreated
string<date-time>
read-only