Sertifi API Web Service
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

NameDescriptionData Type
pstr_APICodeThe API code of the site.  This can be found through your Sertifi web interface under Administration -> Account Settings.xml:string
pstr_FileIDThe id of the relevant file.xml:string
pstr_EmailThe Email address of the signer being added.xml:string
pstr_Email Element pstr_FileID Element pstr_APICode Element Sequence AddSecondSignerToRequest Element
Response (AddSecondSignerToRequestSoapOut)

The response body is of type AddSecondSignerToRequestResponse.

Response Body Parameters

NameDescriptionData Type
AddSecondSignerToRequestResult"SUCCESS" or error message.xml:string
AddSecondSignerToRequestResult Element Sequence AddSecondSignerToRequestResponse Element
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."
See Also
All Operations Resource GroupSertifi API Web Service



© Sertifi, Inc., 2019 All Rights Reserved.

Send comments on this topic.