Skip to main content

Configure Webhook Policy

Configure a webhook policy for appointment events, set the POST URL and authentication token, then add client accounts to the policy.

Written by Quinn Bott

To use webhooks, LSC Administrators first configure a webhook policy, then add accounts to it.

FAQs

  • Webhooks for appointments are supported.

    • Supported appointment activities are created, interpreter scheduled, canceled, changed, and scheduled.

  • Only one webhook can be added per client account.

  • The authentication token can be reset within an existing webhook policy.

  • There must be at least one appointment webhook event selected for each webhook policy.

  • Webhook policies can be disabled or turned off without deleting the policy.

Create the webhook policy

  1. In the LSC Administrator sidebar:

    go to Configuration > Company > Customize > Webhook Policies.

  1. Select "Create Webhook Policy" to add a new one. All existing policies are listed, so you can select an existing policy to make edits.

  1. Name the policy, add an optional description, then copy and paste the Webhook URL from your third-party API tool or integration into the corresponding field.

Configure the webhook policy

Once the policy is created, select it to edit. Select "+Add Event to Webhook" to add the appointment events you want. You must provide the POST URL where Boostlingo should send the data.

Boostlingo provides the authentication token you use to validate the messages.

Add accounts to the webhook policy

  1. Open the policy, then select the "Policy Members" tab in the policy's details.

  2. Select "+Add Accounts".

  1. Select each account from the drop-down, then select "Add Chosen".

Next steps / Getting more help

  • For LSC Admins: If webhook events aren't reaching your endpoint, confirm the POST URL, the selected events, and that the account is a member of the policy. Then reach out to Boostlingo Support with the policy name. If you're unsure how to reach Support, contact your Account Manager.

See also

Did this answer your question?