Welcome Developers


SigniFlow JSON

The SignIFlow JSON API is intended to manage the initiation, cancellation and removal of document workflows created within the SigniFlow system.

The API will also manage the security control within the SigniFlow system and generation of workflow steps.

The API is hosted within the following location:

  • Development environment: http:\\dev.signflow.co.za

The following protocol can be used to communicate with the exposed web service:

  • JSON POST
REST Description

The SigniFlow web service is located at:

  • Development WSDL: http://dev.signflow.co.za/api/Signflowapiservicerest.svc

SAMPLE FLOW DIAGRAM
Image

LOGIN METHOD SAMPLE

Url: https://flow.signflow.co.za/API/SignFlowAPIServiceRest.svc/Login

HTTP Method: POST

REQUEST: JSON
RESPONSE: JSON

GO TO EXAMPLE METHODSFull help file with example payloads
JSON REQUEST SAMPLE:
{
	"PasswordField":"String content",
	"UserNameField":"String content"
}

JSON RESPONSE SAMPLE:
{
	"ResultField":"String content",
	"TokenField":{
		"TokenExpiryField":"\/Date(928142400000+0200)\/",
		"TokenField":"String content"
	}
}

Code by Coders…


SigniFlow DLLs

SigniFlow supports the following Microsoft .Net framework:

  • .Net 4.0
  • .Net 4.5

With support and code snippets for the following languages:

  • VB.NET
  • C#
  • PHP
  • PHYTHON
  • Ruby
  • BOO
  • JAVA
Visit the DLL Help SiteDownload latest DLLs and Code snippets
Image

SigniFlow Signature API

Turn your online application into its own cryptographic signature engine and have your customers sign online in your App.

The fastest cryptographic signature API on the market. The ‘Signature API’ is a high-speed, convenient, purpose-built API that can be integrated with any web service where it is required for the signatory to digitally sign a document, using a third-party application.

Unlike standard SigniFlow APIs and DLLs, the ‘Signature API’ does not utilise standard SigniFlow functions, workflow engine functions or the standard SigniFlow user-authentication process. Instead, it relies on the third-party application to perform certain - or all of these - functions, and pass the information (trust) to the ‘Signature API’, which will use the trust data received from the application to cryptographically sign the document and embed said information in the digital signature.

Trust in the form of authentication is transferred to the third-party application by reference, and only the signature operation is performed by the Signature API. It is therefore expected that the application performs multi-factor authentication of the user, before calling the API.

Visit the Signature API Help PageDownload latest Docs and Code snippets
SOME OF OUR INTEGRATION PARTNERS