/Legal/CreateContract

Allows the client to create a new smart contract, based on an existing (and approved) contract template. The request must be signed using one of the keys created by the client.

JSON

Request

{
	"templateId": Required(Str(PTemplateId)),
	"visibility": Required(Str(PVisibility)),
	"Parts":
	{
		"role": Required(Str(PRole)),
		"legalId": Required(Str(PLegalId))
	}?[],
	"Parameters":
	{
		"name": Required(Str(PParameterName)),
		"value": Required(Str(PParameterValue))
	}?[]
}

Response (if successful)

{
	"Contract": Required(PContract)
}

XML

Request

<CreateContract xmlns="https://waher.se/Schema/BrokerAgent.xsd"
                templateId=(Required(Str(PTemplateId)))
                visibility=(Required(Str(PVisibility)))>
    <Parts>
        <[
        <Part role=(Required(Str(PRole)))
              legalId=(Required(Str(PLegalId))) />?[]
        ]>
    </Parts>
    <Parameters>
        <[
        <Parameter name=(Required(Str(PParameterName)))
                   value=(Required(Str(PParameterValue))) />?[]
        ]>
    </Parameters>
</CreateContract>

Response (if successful)

<ContractResponse xmlns="https://waher.se/Schema/BrokerAgent.xsd">
	<[Required(PContract)]>
</ContractResponse>

Input Parameters

Response Parameters

Javascript Library

Use the following asynchronous method in the Javascript Library, to call this resource. It computes the signatures according to the above specification.

var Response = await AgentAPI.Legal.CreateContract(TemplateId,Visibility,Parts,Parameters);

Note The Parts argument is a vector of objects, each one specifying a role and a corresponding legal ID. The Properties argument on the other hand, is a normal JSON dictionary, and not an array. The Parameters in this dictionary are instead enumerated and converted to the format expected by the web service. The reason for this difference, is that the may be multiple parts signing a contract with the same role, while parameters are unique by name.