Accepts a RelationshipChange with the given changeId.


  • relationshipId the Relationship’s id which should be changed by the RelationshipChange
  • changeId the RelationshipChange’s id
  • content a possible answer to the respective RelationshipChange which the peer can fetch

On Success

  • The RelationshipChange is accepted and the given content made available for the peer.
  • Returns the changed Relationship

On Failure

  • There is no such Relationship or RelationshipChange.
  • The changeId is not related to the relationshipId.

How to execute this use case with the Connector?

The Connector is our first-class citizen, thus we provide you with a detailed API description for every use case. This use case can be executed with the REST API of the Connector which you can Access the Connector.
Corresponding interactive API docs excerpt: