NowCerts Event Queue
In this article, we help you to configure your project in order to connect to a queue and get notified each time an event occurs in NowCerts.
Connect
NowCerts Event Queue is based on a RabbitMQ instance with customized authentication. In order to connect, you need to use a connection string (see below) as well as credentials we provide on demand.
You may use any library available in your code base language to connect to an instance and consume events from the queue.
Connection string
Connection string looks as follows: host=40.122.124.26:5672;virtualHost=/;username={your_username};password={your_password}
Credentials
Username and password are provided by us. In order to get one please send a request to vlad@nowcerts.com,kevin.techsolab@hotmail.com
Restrictions
Your user will have access to data of agencies that are explicitly allowed by agency administrator inside NowCerts portal. In order to enlist more agencies and start receiving events for them please send contact an agency.
Consume
In order to start consuming events from the queue you would need to subscribe to it.
Please follow the instructions on how to subscribe to a queue from the docs of RabbitMQ client library you chose for your project.
After a user has been created, you will receive access to an exclusive queue. Your user will be the only consumer of it.
In order to connect to a NowCerts queue you need to specify the name of the queue which we will provide.
Ack/Nack
Event acknowledgement is completely up to you. You may consume same event as many times as you want and ack it to proceed to the next one.
Retries
Retry logic is based on RabbitMQ default retry functionality. Event will be in the queue until you consume it with an ack.
Replays
Replay logic is based on a custom event log. We are storing at least the last 3 days of events for all the agencies. Events can be replayed on demand. Please send your replay requests to vlad@nowcerts.com,kevin.techsolab@hotmail.com
It is possible to replay events from custom date range if any events are present in that range. After replay is triggered, events will be sent to a separate queue. Authentication and consumption flows are the same as the main queue.
Event structure
Below is an example of an event payload you may receive.Click on below event type enum for individual expected JSON.
Event type enum
INSURED_INSERT
INSURED_UPDATE
INSURED_DELETE
PROSPECT_INSERT
PROSPECT_UPDATE
PROSPECT_DELETE
REFERRAL_INSERT
REFERRAL_UPDATE
REFERRAL_DELETE
POLICY_INSERT
POLICY_UPDATE
POLICY_DELETE
QUOTE_INSERT
QUOTE_UPDATE
QUOTE_DELETE
NOTE_INSERT
NOTE_UPDATE
NOTE_DELETE
TASK_INSERT
TASK_UPDATE
TASK_DELETE
MGA_INSERT
MGA_UPDATE
MGA_DELETE
CARRIER_INSERT
CARRIER_UPDATE
CARRIER_DELETE
FINANCECOMPANY_INSERT
FINANCECOMPANY_UPDATE
FINANCECOMPANY_DELETE
REFERRALSOURCE_INSERT
REFERRALSOURCE_UPDATE
REFERRALSOURCE_DELETE
OTHERTRUCKINGCOMPANY_INSERT
OTHERTRUCKINGCOMPANY_UPDATE
OTHERTRUCKINGCOMPANY_DELETE
DRIVER_INSERT
DRIVER_UPDATE
DRIVER_DELETE
TRUCKINGCOMPANYOPPORTUNITY_INSERT
TRUCKINGCOMPANYOPPORTUNITY_UPDATE
TRUCKINGCOMPANYOPPORTUNITY_DELETE
OTHERCLAIM_INSERT
OTHERCLAIM_UPDATE
OTHERCLAIM_DELETE
GENERALLIABILITYCLAIM_INSERT
GENERALLIABILITYCLAIM_UPDATE
GENERALLIABILITYCLAIM_DELETE
PROPERTYLOSSCLAIM_INSERT
PROPERTYLOSSCLAIM_UPDATE
PROPERTYLOSSCLAIM_DELETE
WORKERCOMPENSATIONCLAIM_INSERT
WORKERCOMPENSATIONCLAIM_UPDATE
WORKERCOMPENSATIONCLAIM_DELETE
VEHICLE_INSERT
VEHICLE_UPDATE
VEHICLE_DELETE
TAGAPPLY_INSERT
TAGAPPLY_UPDATE
TAGAPPLY_DELETE
PRINCIPAL_INSERT
PRINCIPAL_UPDATE
PRINCIPAL_DELETE
PENDINGCANCELLATION_INSERT
PENDINGCANCELLATION_UPDATE
PENDINGCANCELLATION_DELETE
PROPERTY_INSERT
PROPERTY_UPDATE
PROPERTY_DELETE
MASTERCERTIFICATE_INSERT
MASTERCERTIFICATE_UPDATE
MASTERCERTIFICATE_DELETE
AGENT_INSERT
AGENT_UPDATE
AGENT_DELETE
TAGAPPLYONPOLICY_INSERT
TAGAPPLYONPOLICY_UPDATE
TAGAPPLYONPOLICY_DELETE
TAG_INSERT
TAG_UPDATE
TAG_DELETE
INSURANCEAGENCY_INSERT
INSURANCEAGENCY_UPDATE
INSURANCEAGENCY_DELETE
OPPORTUNITYSTAGE_INSERT
OPPORTUNITYSTAGE_UPDATE
OPPORTUNITYSTAGE_DELETE
AUTOMOBILELOSSCLAIM_INSERT
AUTOMOBILELOSSCLAIM_UPDATE
AUTOMOBILELOSSCLAIM_DELETE
SERVICEREQUESTPOLICYCHANGE_INSERT
SERVICEREQUESTPOLICYCHANGE_UPDATE
SERVICEREQUESTPOLICYCHANGE_DELETE
SERVICEREQUESTADDDRIVER_INSERT
SERVICEREQUESTADDDRIVER_UPDATE
SERVICEREQUESTADDDRIVER_DELETE
SERVICEREQUESTADDRESSCHANGE_INSERT
SERVICEREQUESTADDRESSCHANGE_UPDATE
SERVICEREQUESTADDRESSCHANGE_DELETE
SERVICEREQUESTREMOVEDRIVER_INSERT
SERVICEREQUESTREMOVEDRIVER_UPDATE
SERVICEREQUESTREMOVEDRIVER_DELETE
SERVICEREQUESTREPLACEDRIVER_INSERT
SERVICEREQUESTREPLACEDRIVER_UPDATE
SERVICEREQUESTREPLACEDRIVER_DELETE
SERVICEREQUESTVEHICLETRANSFER_INSERT
SERVICEREQUESTVEHICLETRANSFER_UPDATE
SERVICEREQUESTVEHICLETRANSFER_DELETE
SERVICEREQUESTGENERALNEW_INSERT
SERVICEREQUESTGENERALNEW_UPDATE
SERVICEREQUESTGENERALNEW_DELETE
SERVICEREQUESTGENERIC_INSERT
SERVICEREQUESTGENERIC_UPDATE
SERVICEREQUESTGENERIC_DELETE
LOB_INSERT
LOB_UPDATE
LOB_DELETE