Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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.

...

  1. 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.

  2. Select an Event

...

  1. that will act as a trigger for the webhook

    image-20240514-183018.pngImage Added

    The available events are:

    1. Contract Recipient Status Change

    2. Contract Status Change

    3. Change Order Status Change

    4. Homeowners Signed Contract

    5. Milestone Comment Created

    6. Milestone Status Change

    7. Task Comment Created

    8. Qualification Update

    9. Site Archived

...

    1. Stage Transition

    2. Proposal Action

    3. Invoice Status Change

    4. Workflow Status Change

  1. Determine some settings for your Webhook:

    1. URL Path

...

    1. - this is the address for the API call when the event is triggered.

    2. Credential -

...

    1. this field is a dropdown menu. Each webhook is tied to a

...

    1. 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.

    2. HTTP Method - this field is a dropdown menu:

...

PUT: is most-often utilized for update capabilities

...

POST: utilized to create new resources.

...

    1. you can select PUT, POST, or PATCH. Most partners select POST

    2. 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.

    3. 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.