With #141, which was part of release 1.9.0, these endpoints (and their sub-resources):
/restapi/v1/chatrooms/{roomName}/owners/restapi/v1/chatrooms/{roomName}/admins/restapi/v1/chatrooms/{roomName}/members/restapi/v1/chatrooms/{roomName}/outcasts
got replaced by one generic endpoint (and sub-resources):
/restapi/v1/chatrooms/{roomName}/{affiliation}
Sadly, this new template clashes with other, unrelated endpoints, including:
/restapi/v1/chatrooms/{roomName}/chathistory/restapi/v1/chatrooms/{roomName}/occupants/restapi/v1/chatrooms/{roomName}/participants/restapi/v1/chatrooms/{roomName}/invite
The fix for #141 makes these return an 400 response, stating that chathistory, occupants, participants or invite is not a valid affiliation value.
With #141, which was part of release 1.9.0, these endpoints (and their sub-resources):
/restapi/v1/chatrooms/{roomName}/owners/restapi/v1/chatrooms/{roomName}/admins/restapi/v1/chatrooms/{roomName}/members/restapi/v1/chatrooms/{roomName}/outcastsgot replaced by one generic endpoint (and sub-resources):
/restapi/v1/chatrooms/{roomName}/{affiliation}Sadly, this new template clashes with other, unrelated endpoints, including:
/restapi/v1/chatrooms/{roomName}/chathistory/restapi/v1/chatrooms/{roomName}/occupants/restapi/v1/chatrooms/{roomName}/participants/restapi/v1/chatrooms/{roomName}/inviteThe fix for #141 makes these return an 400 response, stating that
chathistory,occupants,participantsorinviteis not a valid affiliation value.