https://encromerrdev.epacdxnode.net/shared-cromerr-rest/
Service | Description | WSDL |
---|---|---|
IdentityProofingService2 | Provides an interface to an asynchronous third-party electronic identity proofing service. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/IdentityProofingService2?wsdl |
MessagingService | Defines a way to send out messages to users via SMS or email. Also facilitates sending/validation of PINs for various purposes. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/MessagingService?wsdl |
SecondFactorAuthenticationService | Allows a user to re-authenticate and answer a knowledge-based question during the signature process. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SecondFactorAuthenticationService?wsdl |
SignatureAndCorService2 | Allows a user to sign a document and subsequently validate the copy of record (COR) against the generated signature. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureAndCorService2?wsdl |
SignatureService2 | Allows a user to sign a document and subsequently validate the copy of record (COR) against the generated signature. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureService?wsdl |
UserManagementService | Allows client applications to create, update, and manage user accounts for use within the client application, including establishing knowledge-based questions and answers for use during the signature process. | https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/UserManagementService?wsdl |
Provides an interface to an asynchronous third-party electronic identity proofing service.
Defines a way to send out messages to users via SMS or email. Also facilitates sending/validation of PINs for various purposes.
Allows a user to re-authenticate and answer a knowledge-based question during the signature process.
Allows a user to sign a document and subsequently validate the copy of record (COR) against the generated signature.
Allows a user to sign a document and subsequently validate the copy of record (COR) against the generated signature.
Allows client applications to create, update, and manage user accounts for use within the client application, including establishing knowledge-based questions and answers for use during the signature process.
Notes: User ID requirements: must a) consist of at least 8 alphanumeric characters, b) must not be all numeric, and c) allowed special characters: period (.), hyphen (-), underscore (_), at (@). Password requirements: a) consist of at least 8 alphanumeric characters, b) not contain the User ID, c) must not contain the word "password", d) contain only letters and numbers, e) contain at least one lowercase and one uppercase letter, f) contain at least one number, g) begin with a letter, h) cannot use any of the user's previous 10 passwords.
Definitions for data types that are used in service calls.
Encapsulates the QuestionId and the text of the answer that the user provides in response.
Describes a CROMERR event.
CROMERR event group.
Valid values are:
CROMERR event status.
Valid values are:
CROMERR event type.
Valid values are:
Encapsulates all required user information in order to process LexisNexis.
Describes a message to be sent.
Describes result of a sent message.
Valid message destinations.
Valid values are:
Encapsulates a collection of key-value pairs.
Encapsulates a single key-value pair.
Defines user profile elements.
User account status.
Valid values are:
Defines base user profile elements.
(v2) Defines document search criteria.
(v2) Encapsulates the detached signature object
(v2) Describes document metadata and the content of the document.
(v2) Document format
Valid values are:
(v2) Describes a CROMERR event.
(v2) CROMERR event group.
Valid values are:
(v2) CROMERR event status.
Valid values are:
(v2) CROMERR event type.
Valid values are:
(v2) Describes the type of notification to be sent.
(v2) Notification category
Valid values are:
(v2) Encapsulates one or more notifications.
(v2) Encapsulates a collection of key-value pairs.
(v2) Encapsulates a single key-value pair.
(v2) Information used to repudiate a document.
(v2) Retention status. New documents will use the Default status.
Valid values are:
(v2) Encapsulates the three elements that define the user's signature.
(v2) Defines base user profile elements.
(v2) Defines organization information.
(v2) Defines role information.