Signer.Digital Server provides SOAP API for signing PDF File. The SOAP API is useful in scenarios and platforms where native pdf component is unavailable or not feasible to deploy. The service supporting the API takes the complete PDFFile to be signed along with Name of SignatureSetting and returns Signed PDF File.
Since these APIs takes complete PDF file for signing, the response may be somewhat slower than native component. Also it has to be kept in mind from the Security and PDF Document protection perspective that the Server hosting service receives complete PDF file for signing and not just the HASH; but this is okay if the application generating pdf and this service, consuming pdf for signing, is on same hardware or in same internal network, fully owned by the Organization.
Alternatively, the Setup is available on request to install and host the service in your server(s) on public or private network. Use Signer.Digital Console -> Other Settings to configure the endpoint either using your (sub)domain or IP address as be below snapshot:
