Optional credential workflow
Integrators can pass credentials directly within a request. Credentials and the
appropriate Package ID* can be included as a base64-encoded JSON string in a custom http
header (
X-SmartSignPlus-Configuration) within the following fields of
the request.- Login ID
- API Key
- Client ID
- Client Secret
- Organization ID
- Package ID (used only for redraws)
Sample JSON string:
{
"loginId": "xxxxxxxxxxx",
"apiKey": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"clientId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"clientSecret": "xxxxx-xxxxxxxxxxx-xxxxx",
"organizationId": "123456789",
"lenderName": "xxxxxxxxxx",
"packageId": ""
}Note: Consider the following:
- *a
"packageId"parameter is not used within a custom header forSmartSignPlusPackageStatus,SmartSignPlusFinalize, andSmartSignPlusModifyPackagecalls, and is used only in the custom header for redraws. - The JSON string is encoded in an "http" header, separate from the
<Header/>element within theSOAP:envelope.