> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Developer Webinar: OAuth for Connect (Webhooks) 10.17.23 | Webinars

#### Developer Webinar: OAuth for Connect (Webhooks) 10.17.23 | Webinars

In this webinar, we’ll cover one of our most adopted developer features this year: OAuth for Connect. By integrating the OAuth for Connect security protocol into your Webhook-driven applications, you can enhance the security level and verify that the notification messages your application receives are from DocuSign. It also ensures the messages received aren’t from an outside source and gives you more control over the security mechanism used.