Exchanging documents with third-party systems

Remote saving makes it possible to send a loaded document directly to another system via HTTP. The URL can be set via PATCH /viewer/configuration with the parameter saveUrl and will then change the saving function in the Viewer. Information about the status of the signature fields is attached with the following URL parameter when a request is made.

• sf: Number of signed fields

• usf: Number of non-signed fields

• smf: Number of signed mandatory fields

• usmf: Number of non-signed mandatory fields

• index (optional): Optional index of the Viewer that can be set beforehand via the call PUT /viewer/meta/index.

The following points must be taken into account by the receiving side:

• It must be able to accept a multipart upload (content type: multipart/form-data)

• The PDF is transferred in the field saveFile.

• The external system must send a response containing the following content upon successful completion:

  JSON

  {
      "remoteSavingResponse" : "REMOTE_SAVING_SUCCESSFUL"
  } 

  and a response containing the following content in the event of an error:

  JSON

  {
      "remoteSavingResponse" : "REMOTE_SAVING_FAILED"
  } 

  or alternatively

  JSON

  {
      "remoteSavingResponse" : "REMOTE_SAVING_FAILED",
      "customizedSavingErrorMessage" : "my custom error message"
  } 

• it must be able to give authorisation through cookies (if authorisation is required)

Setting cookies to communicate with third-party systems is described here.