You can use SwiftEnterprise REST APIs as service endpoints to interact with SwiftEnterprise Application remotely and perform various functions.
The link https://saas.digite.com/rest/v1/ takes you to the Swagger document to access different services. These web services can be used on any operating system and any web service client capable of handling REST API protocol.
For example, to view the list of operations that can be performed on an eForm, you can click EFormService. It opens the Swagger page where you can access all services related to the eForm operations.
The authentication method for the REST APIs is token-based authentication using JWT Token or using Personal SwiftEnterprise LoginID.
In case of JWT based authentication, a token is generated for a user-specified time interval. To access any of the REST web services you must first generate the Authentication Token.
To get an Authentication Token in SwiftEnterprise, perform the following steps:
You can generate an Authentication Token using your personal SwiftEnterprise LoginID.
Since this method accepts Encrypted Password, an UI page will be provided (It will be provided by Digite support on request), which will accept plain text password and create an encrypted password. It will use a 64 bit DES (Data Encryption Standard) Encryption method to encrypt the password.
Pass the Loginid and Encrypted Password as a part of the body to call the TokenService. The resulting output string is returned in the response body as the data element, which is one of the several name/value paired objects in a data collection. Make sure that the user for which you are generating a personal access token is having enough access to perform the activities. Following is the snippet of the sample call to generate the personal SwiftEnterprise ID token.
The following snippet shows the generated Authentication Token as part of the response body. The response body contains a data element, which should be passed as header to call all the SwiftEnterprise REST web services.
A REST API request/response pair can be separated into the following components:
2. HTTP request message header fields:
SwiftEnterprise REST web service exposes API to allow users to perform common card operations as listed below: