| Info |
|---|
Note: this feature is only available to customers with API integrations who have expressed interest in managing their own webhooks. If this feature is turned on, and you have Organization Admin permissions then you can view this page. access enabled. To learn more, please reach out to support@goeverbright.com |
Webhooks (also called a web callback or HTTP push API) are a way for Sighten EverBright to provide other applications with real-time event-based information.
...
First, navigate to Settings and select Integrations Integration Settings on the left sidebar.The Credentials and Webhooks tab is the second tab on this page.
...
Above is an example of an account with no webhooks set up.
Before you can create a webhook, you must create credentials. Please follow instructions here to create credentials.
How do I add Webhooks to my account?
To add a credentialwebhook, click the green Add Webhook button highlighted below:
...
From there, an Add Webhook modal will open.
...
Name your webhook: this should be something simple that identifies the webhook and is associated with your account to assist with any triaging of EverBright logs.
Select an Event
...
that will act as a trigger for the webhook
...
...
The available events are:
Contract Recipient Status Change
Contract Status Change
Change Order Status Change
Homeowners Signed Contract
Milestone Comment Created
Milestone Status Change
Task Comment Created
Qualification Update
Site Archived
Stage Transition
Proposal Action
Invoice Status Change
Workflow Status Change
Determine some settings for your Webhook:
URL Path
...
- this is the address for the API call when the event is triggered.
Credential -
...
this field is a dropdown menu. Each webhook is tied to a
...
credential. If it is a test webhook, then you will only see test credentials and if it is a production credential, you will only see production credentials.
HTTP Method - this field is a dropdown menu: you can select PUT, POST, or PATCH. Most partners select POST
Test Webhook - toggle: This determines if the webhook is applied in a test (Onboard) or production environment (Engine). Once your webhook is created, there will be a test label next to the name for test webhooks.
Active - toggle: This determines if the webhook is active or not. Once your webhook is created, there will be an inactive label next to the name for webhooks that have been deactivated.