Sofar logo
Sofar logo
Api
Delete a member relation DELETECollect member relations (replaced by POST /v1/role/{roleId}/member/query) GETCollect member relations POSTCreate or update a member relation PUTUpdate an existing member relation PUT
Member
DELETE
/v1/role/{roleId}/member/{memberId}

A user can only execute this action if he is a member of an authorizing role which satisfies one of the following conditions: The authorizing role has direct or indirect userManagement rights for the role to which a member is deleted The authorizing role has indirect roleManagement rights for the role to which a member is deleted The authorizing role is the role from which a member is removed, and the removed member is the user itself

Authorization

accessBearerAuth
AuthorizationBearer <token>

In the value field below, fill in the access token. It has a 10 minutes validity period. A valid token can be obtained via the /accesstoken endpoint (call), AFTER authorization with refreshBearerAuth and the refresh token.

In: header

Path Parameters

roleId*integer

Id of the role of the deleted member relation

Range0 <= value
memberId*integer

Id of the deleted member relation

Range0 <= value

Response Body

application/json

application/json

application/json

application/json

curl -X DELETE "https://api.eniris.be/v1/role/0/member/0"
{
  "deletedNodeIds": [],
  "deletedRelationIds": []
}
{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Missing or misformatted query parameter or body"
}
{
  "statusCode": 401,
  "error": "Unauthorized",
  "message": "Failed to verify token"
}
{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "User does not have sufficient rights"
}

Update an existing manages relation PUT

Update an existing manages relation. A user can only execute this action if he is a member of an autorizing role which has (direct or indirect) roleManagement rights for the parent role of the manages relation

Collect member relations (replaced by POST /v1/role/{roleId}/member/query) GET

Get all (or some of) the member relations which start from a role where the user has (either directly or indirectly) userManagement rights, and get those member relations involding the user itself. The POST /v1/role/{roleId}/member/query is a preferable alternative, which can better handle complex filters.