Monitoring Notifications
Test in Sandbox environment notification for monitoring enabled accounts and policies
After completing an Ignition session and exchanging the authCode
for an accessToken
, you can trigger an Account event through POST /sandbox/account/{accountId}/event
or Policy event through POST /sandbox/policies/{policyId}/event
.
You can also test notifications sent to other communication channels such as
email or Slack by making a request to the same Axle API endpoints. Reach out
to the Axle team to ensure your client
is properly configured!
The following Account events and Policy events are supported:
account.modified
You can modify Account fields to simulate an account.modified
event. The following example will change email
, firstName
, and phone
fields on an existing Account.
account.disconnected
You can test account.disconnected
event by setting the connection status to one of the “inactive” states. Refer to Account object for all the available cases.
When account has been set as disconnected
, your user will need to complete
an Axle Ignition session to reconnect it. If the user reconnects the same
insurance account and policy, Axle will merge the updated information with any
existing Account or Policy objects. More info on account.disconnected
can be
found here.
policy.modified
You can modify Policy fields to simulate a policy.modified
event. The following example will set Policy as inactive (e.g., the policy has been cancelled) as well as update the Policy address.