List of permissions that the short-lived token can have. These can only be permissions that are already given to the calling user.
JWT token
{"permissions": ["string"]}
{"token": "string"}
The unique company identifier.
A valid domain associated with a company
User type.
The username to authenticated. This can be a username or an email, depending on the configuration.
The password to authenticate with.
{"username": "string","password": "pa$$word"}
Logged out
Success no content
Success
{"status": 200,"message": "success","data": {"1": ["loan:create","loan:read"],"2": ["person:list"]}}
{"data": {"username": "string"}}
Either an email address or phone number depending on the auth type and auth value type set up for the company.
The channel where interactions with a borrower occur. For example, an outbound call with a borrower is considered voice.
voice
Template specific properties to substitute in the corresponding ConfirmationCode template.
OK
{"username": "string","userType": "agent","channel": "voice","context": { }}
App Domain Type.
SAMLResponse=string&RelayState=string
If true, will return a URL to the login instead of redirecting to the login
true
Peach acts as the service provider