The 1.29.1 release introduces support for userProfileId across the Activation and Legal Documents services. This identifier is now critical for fetching user-specific legal documents and handling activation responses.
userProfileId
Activation
Legal Documents
The activate method now returns a ResultHandler<Activation> instead of ResultHandler<Void>.
ResultHandler<Activation>
ResultHandler<Void>
The success response now provides an Activation object containing userId and userProfileId.
All public methods (getLegalDocuments, getLegalDocumentContent, submitConsent) now require userProfileId: String as a parameter.
getLegalDocuments
getLegalDocumentContent
submitConsent
userProfileId: String
Last updated 1 month ago