romainlefebvre

Why the owner of the account becomes a signer in a package using API ?

0 votes
Hi, We are noticing a surprising behavior when using the REST API to create a package, compared to a package created using the UI. When we use your quick start "Create and send a package" (https://developer.esignlive.com/guides/quick-start/creating-and-sending-a-package-java/), we should have only 2 signers. But we get a third signer which is owner of the account. The thing is we don't want the owner of the account to be part of the signing process. This behavior does not exist if we create a new package from the UI directly. Is this a bug?
DocumentPackage documentPackage = newPackageNamed("Test Package Java SDK")
			.withSigner(newSignerWithEmail( "[email protected]" )
				.withCustomId( "Signer" )
			    .withFirstName( "SignerFirstName" )
			    .withLastName( "SignerLastName" ) )
			.withSigner(newSignerWithEmail( "[email protected]" )
			    .withFirstName( "YourFirstName" )
			    .withLastName( "YourLastName" ))
			.withDocument( newDocumentWithName( "sampleAgreement" )
			    .fromFile( "C:\\Users\\dly7336\\Desktop\\esignlive_requetes.docx")
			    .withSignature( signatureFor("[email protected]")
			    	.onPage( 0 )
			     	.atPosition( 175, 165 ) )
			    .withSignature( signatureFor( "[email protected]")
			        .onPage( 0 )
			        .atPosition( 550, 165 )))
			.build();
		
		PackageId packageId = eslClient.createPackage(documentPackage);
Thanks

Reply to: Why the owner of the account becomes a signer in a package using API ?

0 votes
Try adding this when building your package:
.withSettings(DocumentPackageSettingsBuilder.newDocumentPackageSettings().hideOwnerInPersonDropDown())

Reply to: Why the owner of the account becomes a signer in a package using API ?

0 votes
Is this an issue because of in-person signing as jhullin mentions? Or a problem for another reason?

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Why the owner of the account becomes a signer in a package using API ?

0 votes
It's not an in-person signing issue. We have an eSign service account (which is not link to any employee) and that will be used for the API to create packages. I just want 2 persons to sign those documents (let's say the final customer and the sale representative). Why would I have another signer (the owner of the service account) shown in the list of signers?

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off