Skip to main content

Webhook Authentication Tab

Secure your lead deliveries with multiple authentication options such as Basic, Digest, Bearer Token, and OAuth 2.0 authentication

Chris Arenas avatar
Written by Chris Arenas
Updated over 2 weeks ago

Overview

The Authentication Tab provides four methods to secure webhook connections between LeadExec and your client's systems. Choose the method that matches your client's API security requirements.

Authentication Types

Basic and Digest Authentications:

For Basic and Digest authentications, this is where you will set the username and password supplied by your client.

OAuth 2.0:


Provides the ability to authenticate with an OAuth server using Client Credentials or Password. Here you will set the TOKEN URL, select the required Grant Type and input the credentials supplied by the client.

Bearer Token:

If the client’s system uses Bearer Token authentication, this is where you will set the Prefix and Token provided by the client.

Configuration Guide

Basic & Digest Authentication

  1. Select Authentication Type → Choose Basic or Digest

  2. Enter Credentials:

    • Username: Provided by client

    • Password: Provided by client
      Note: Digest provides encrypted authentication compared to Basic

Bearer Token Authentication

  1. Select Authentication Type → Choose Bearer Token

  2. Configure Token:

    • Prefix: Usually "Bearer" (check client docs)

    • Token: Authentication token provided by client

OAuth 2.0 Authentication

  1. Select Authentication Type → Choose OAuth 2.0

  2. Configure Settings:

    • Token URL: OAuth server endpoint from client

    • Grant Type: Client Credentials or Password

    • Credentials: Client ID, Client Secret, or User credentials

Step-by-Step Setup

  1. Access the Authentication Tab in your Webhook Delivery Method

  2. Select the Authentication Type matching client requirements

  3. Enter Credentials exactly as provided by the client

  4. Test Authentication using the Test Connection button

  5. Save the Configuration once validation succeeds

Best Practices

  1. Security First:

    • Whenever possible, make sure to use HTTPS endpoints

    • Never share credentials via email or other open channels

  2. Validation:

    • Test authentication before going live

    • Verify token permissions with sample leads

  3. Documentation:

    • Record credential expiration dates

    • Note client contact for authentication issues

Troubleshooting

  1. "401 Unauthorized" errors

    • Verify credentials are entered correctly

  2. "403 Forbidden" error messages

    • Check token permissions/scopes

  3. OAuth Token Failures

    • Validate Token URL and grant type


Next article: Field Mappings Tab >

Did this answer your question?