# Event

Events are how we communicate notable activity on an independent contractor's insurance application, policy, and certificate processing. When an event occurs, we create a new Event object. For example, when an insurance application is started, we create an `application.started` event; when a policy is issued, we create a `policy.active` event; and when a certificate evaluation completes, we create certificate events such as `certificate.approved`, `certificate.flagged`, or `certificate.denied`.

API resource state changes trigger events. The state of that resource at the time of the change is embedded in the event's data field. For example, an `application.started` event will contain an insurance application `Session` object, a `policy.active` event will contain a `Policy` object, and certificate events will contain a `Certificate` object with the evaluation results.

These events are sent to your registered webhook endpoint, allowing you to respond immediately when certificate processing completes without needing to poll the API.

Use the events endpoints to retrieve an individual event or a list of events. You can listen for events by registering your server endpoint via the 1099Policy [dashboard](https://dashboard.1099policy.com/webhooks). Our webhooks system send the Event objects directly to your registered endpoint.

## Operations

- [List all events](https://docs.1099policy.com/operation/operation-get-api-v1-events.md)
- [Retrieve an event](https://docs.1099policy.com/operation/operation-get-api-v1-events-parameter.md)