/testsite/Services/Gateway.asmx/AddSecondSignerToRequest (Method)

Description

Has the exact same effect as AddSignerToRequest call with a Sequence of 2.

Request (AddSecondSignerToRequestSoapIn)

The request body is of type AddSecondSignerToRequest.

Request Body Parameters

Name	Description	Data Type
pstr_APICode	The API code of the site. This can be found through your Sertifi web interface under Administration -> Account Settings.	xml:string
pstr_FileID	The id of the relevant file.	xml:string
pstr_Email	The Email address of the signer being added.	xml:string

Response (AddSecondSignerToRequestSoapOut)

The response body is of type AddSecondSignerToRequestResponse.

Response Body Parameters

Name	Description	Data Type
AddSecondSignerToRequestResult	"SUCCESS" or error message.	xml:string

Remarks

Common Errors include:
"ERROR: Invalid API Code"
"ERROR: File could not be accessed"
"ERROR: Invalid Email address"
"ERROR: Room Expired"
"ERROR: Invalid Email address: ..."
"ERROR: The email you specified is already a participant at that level."
"ERROR: No. of total signers in the room can not be more than 24."
"ERROR: Unable to add as a signer."
"ERROR: Unable to add the email address."