This table contains the possible Actions that may appear in the History section of the user's profile. To view the user's history, from the Narmi Command sidebar, select Customers/Members or Staff members > Staff, depending on the user type. Select a specific user from the list and then scroll to the History section. These actions can be used as webhook events. For more information, go to Webhooks.
For a list of events performed in Narmi Banking that may appear in the Activity History page of the enhanced user profile, go to Activity History Events.
Action (in resource.action syntax) | Definition |
|---|---|
accept_terms.create | User accepted terms of service |
account.destroy | Attempt to unlink an external account |
accountapplication.cancelled | An account application was canceled |
accountapplication.create | A new account application was created |
accountapplication.opened | The application has entered "Opened" status |
accountapplication.rejected | The application has entered "Rejected" status |
accountapplication.review | The application has entered "Review" status |
accountapplication.state | The application has changed status |
accountapplication.submitted | The application has entered "Submitted" status |
accountapplication.update | A change has been made to an application |
accountbalances.update | Account balance of an account is updated |
accountbalance.update | Account balance of an account is updated |
accounts.create | Account added for user |
account_stop.create | Stop payment created |
account.update | Account information updated |
accountverify.create | Verification of external account via microdeposit created |
accountverifyinstant.create | Account verified using instant account verification (MX) |
ach.review | ACH transaction moved to review state |
address.update | User’s address was updated |
appauthorize.create | NAF app credentials added for user |
appauthorize.update | NAF app credentials updated for user |
applicant.create | A new applicant is created |
applicant.update | An applicant's information has been updated |
application.change_state | Account application state changed by a staff member (for example, force-pushing to "Rejected") |
backoffice_ach_transaction.destroy | User’s ACH transaction canceled by a staff member |
backoffice_ach_transaction.update | User’s ACH transaction updated/processed by a staff member |
backoffice_workflow_rule.create | New risk rule created |
backoffice_workflow_rules.create | New risk rule created |
backupcodes.generate | Backup codes generated by a user |
billpay_credential.create | New bill pay credential created by a staff member |
billpay_credential.update | Bill pay credential updated by a staff member |
billshark.create | Billshark integration set up for user |
billsharkuser.create | Billshark integration set up for user |
deposit.create | Remote deposit capture (RDC) deposit created by user |
deposits.create | Remote deposit capture (RDC) deposit created by user |
deposits.update | Remote deposit capture (RDC) deposit updated by user |
enroll_user.update | A user enrolled or logged in for the first time |
enroll_verify.create | Created user enrollment verification |
enrollment.complete | User completed enrollment in digital banking |
estatements.create | User enrolled in estatements (paperless statements) |
estatements.destroy | User un-enrolled in estatements (paperless statements) |
external_account.destroy | User deleted an external account |
external_accounts.create | User manually added an external account to their account |
external_accounts_verify_instant.create | User added an external account using instant account verification |
external_account.update | External account information is updated |
external_account.verify | User verified external account using microdeposit verification |
external_account_verify.create | User verified external account using microdeposit verification |
insurance_policy.create | Created Lemonade policy |
insurance_quote.create | Created Lemonade quote |
intrainstitutiontransfer.update | Log generated when some data about the intra-institution transfer was changed, for example, because it was processed by the scheduled transfer processor. An intra-institution transfer is an internal transfer between accounts at the institution. |
limits.update | User ACH or Remote deposit capture (RDC) limits were updated |
linkedorganizations.create | Staff user linked an organization (shows on the staff profile only) |
linkedorganizations.destroy | Staff user unlinked an organization (shows on the staff profile only) |
m2ms.create | Member to member (or friend to friend) transfer initiated or member/friend contact added |
memberfriend.create | User adds a new member/friend contact |
memberfriend.transfer | A member to member (or friend to friend) transfer initiated |
message.create | Secure message sent by a Digital Banking user |
message.delete | Secure message deleted by staff member |
messages.create | Secure message sent by a staff member |
offline_verification_push_notification.sent | Generated when a push notification is sent to a user when a staff member attempts offline verification |
organizationusers.create | A new sub-business user was added to a business |
password_reset_confirm.create | Generated when a password reset request is sent |
payee.create | User created a payee |
payee.delete | User deleted one of their payees |
payees.update | Updated billpay payee |
payee.update | Updated billpay payee |
payment.create | Created a billpay payment |
payment.delete | Canceled a billpay payment |
payments.update | Updated a billpay payment |
phone.update | User updated their phone number |
referralcodes.update | User profile’s referral code is updated |
rdc.holds.create | Holds created as a result of remote deposit capture (RDC) |
saved_search.alert | User transaction alert sent |
saved_search.destroy | User transaction alert rule deleted |
saved_searches.create | User transaction alert rule created |
savedsearches.create | User transaction alert rule created |
scheduledtransfer.create | Created a scheduled transfer (either recurring or one time) through the mobile application |
scheduledtransfer.destroy | Deleted a scheduled transfer (either recurring or one time) through the mobile application |
security_devices.create | Generated when a user adds a new multi-factor authentication device |
security_devices.destroy | Generated when a user deletes a multi-factor authentication device |
signed_urls.update | New service credentials were created for a user when they logged into SSO |
session.create | New user session created |
sudo.create | User performed elevated authentication using two-factor authentication |
thread.create | New secure message thread created by Digital Banking user |
thread.destroy | Secure message thread deleted |
threads.create | New secure message thread created by a staff member |
tokens.create | Login token for mobile app created |
tokens.destroy | Login token for mobile app deleted/expired |
transaction.update | Transaction updated by user |
transfer.create | Called when transfers.create is called and the scheduled transfer is for the current day |
transfer.destroy | Deleted a scheduled transfer (either recurring or one time) through a web browser, not the mobile application |
transfer.error | An error occurred during a transfer |
transfer.process | Scheduled transfer was processed |
transfers.create | Called when any transfer is being scheduled either recurring or one time on any type of device or mobile application |
transfer.update | Transfer updated by user |
user.account_access_changed | A user gains access or loses access to an account |
user.create | A user is created |
user.email_confirm | User email verification completed |
user_email.create | User email entry was created |
user.email_update | User updated email |
user.emulate | Staff member emulated a user |
user.enroll | User enrollment completed |
user.lock | Generated when the user is locked out of Digital Banking by a risk rule or if a staff member manually locks the user (mobile and web). If Actor column displays the user, they triggered a risk rule. If the Actor column displays a staff user, the user was locked manually by staff. |
user.send_email | System email sent to user for any action that automatically sends an email |
user.unlock | User account is manually unlocked by a staff member (mobile and web) |
user.login | Generated when a user logs in via web (not mobile) |
user.login_failed | User failed login via web or mobile with incorrect password; generated when an incorrect password is entered for a username |
user.login_with_password | Generated when a user successfully authenticates with their password via mobile |
user.password_change | A user changed their password from Digital Banking |
user.refresh_token | Mobile application authentication token refreshed |
user.remember_device | Generated when a user verifies 2FA and selects "Remember this device" via web |
user.request_email_update | Generated when a user resets their email. |
user.request_password_reset | Generated when a user or staff member requests a password reset |
user.reset_password | Generated when a user changes their password via self-service or when they follow through on a Reset Password email request. |
users.create | A user is created |
user.verify | Generated when a user verifies their account (for example, after logging in on an unknown device) |
user.verify_{device_type} | Generated when a 2FA device is successfully verified via web or mobile; |
user.verify_with_existing_refresh_token | Generated when a user authenticates with an existing, non-expired refresh token via mobile |
verify.create | Create user verification |
wire.review | Wire moved to review |
wires.create | User initiated a wire transfer |