This use case tests if an incoming LocalRequest can be accepted with the given parameters without actually accepting it.

This is great for checking if all required information of a Request was filled out in order to accept it, e.g. to update a user interface with the respective errors (and render an “Accept Button” as disabled) as long as there are errors.

Parameters

On Success

  • Returns a RequestValidationResult that indicates if the Request can be accepted with the given parameters.

On Failure

  • The decisions do not match the RequestItems.
  • The decisions and values of respective RequestItems do not match the requested or required values, e.g. an email address is wrong.
  • A RequestItem that has the mustBeAccepted field set to true was not accepted or left blank.
  • A RequestItem of a Request cannot be accepted if its acceptance would lead to the creation of a RelationshipAttribute with the same key, owner and value.@type as a RelationshipAttribute that already exists in the context of the Relationship to the peer that sent the Request. The corresponding Request can therefore not be accepted if the RequestItem in question has mustBeAccepted set to true. However, if mustBeAccepted is set to false, the Request can still be accepted by rejecting the RequestItem.

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: