Answer: Use `bearerAuth()` when the sender can attach an authorization header, or `publicEndpoint()` when webhook providers can't attach the agent alias token; with `publicEndpoint()` you must verify the provider's signature before starting a turn or calling a tool. For shared secret headers or HMAC-SHA256 signed raw bodies, use `sharedSecretAuth()` or `hmacSignatureAuth()` instead, which answer a bad delivery with `401`. Status: Confirmed Entry: tool/cursor/permissions-and-security/protect-public-webhooks Revision: 1 Digest: sha256:1737deb83660527d (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:41Z Last changed: 2026-11-13T03:08:41Z Last verified: 2026-11-20T12:33:19Z Next check: 2026-11-21T12:33:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of auth for header-capable senders | bearerAuth() | [1] | 2026-11-20 public endpoint option | publicEndpoint() | [1] | 2026-11-20 required verification | verify the provider's signature | [1] | 2026-11-20 shared secret auth | sharedSecretAuth() | [1] | 2026-11-20 HMAC signature auth | hmacSignatureAuth() | [1] | 2026-11-20 bad delivery status | 401 | [1] | 2026-11-20 default route behavior | Custom routes accept direct loopback requests by default and reject | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/guides/webhooks.md". https://cursor.com/docs/agent-sdk/guides/webhooks.md Role: primary. Accessed: 2026-11-20T12:33:19Z Quote: "Use `bearerAuth()` when the sender can attach an authorization header." (Supports: auth for header-capable senders) Quote: "`publicEndpoint()` lets a custom channel skip it on Cursor hosting." (Supports: public endpoint option) Quote: "That opens the route to every caller, so verify the provider's signature before you start a turn or call a tool." (Supports: required verification) Quote: "If the provider sends a shared secret header or signs the raw body with HMAC-SHA256, use `sharedSecretAuth()` or" (Supports: shared secret auth) Quote: "`hmacSignatureAuth()` instead." (Supports: HMAC signature auth) Quote: "answers a bad delivery with `401`." (Supports: bad delivery status) Quote: "Custom routes accept direct loopback requests by default and reject" (Supports: default route behavior) Snapshot SHA-256: f38fb3c7e7e7aee9b30612d7794b6266c66cff5a6e3b64504694ef383a45cf5e (captured 2026-11-13T03:08:40Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:41Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:33:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:33:19Z Last attempt: 2026-11-20T12:33:19Z Notes and limitations: Extracted automatically from a single official source (section "Protect public webhooks"). Related: https://latestn.com/tool/cursor/permissions-and-security/request-user-tokens-scope How do I request the namespace:user_tokens:write scope for a Cursor Origin app installation? https://latestn.com/tool/cursor/permissions-and-security/restrict-cloud-agent-repositories How do I restrict which repositories Cursor Cloud Agents can reach? https://latestn.com/tool/cursor/permissions-and-security/restrict-invites-domains How do I restrict invites to verified domains in Cursor Teams? https://latestn.com/tool/cursor/permissions-and-security/origin-repository-visibility What visibility options exist for Cursor Origin repositories and how are personal repos handled? https://latestn.com/tool/cursor/permissions-and-security/permissions-vs-sandbox-json What is the difference between permissions.json and sandbox.json in Cursor? https://latestn.com/tool/cursor/permissions-and-security/prevent-eval-side-effects How do I keep side effects out of Cursor eval sessions? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:41Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/protect-public-webhooks/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/permissions-and-security/protect-public-webhooks POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/protect-public-webhooks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/protect-public-webhooks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I protect public webhook endpoints in Cursor's Agent SDK? Revision 1, last verified 2026-11-20T12:33:19Z. https://latestn.com/tool/cursor/permissions-and-security/protect-public-webhooks (accessed 2026-11-21T10:03:42Z). @misc{LatestN_tool_cursor_permissions_and_security_protect_public_webhooks_r1, title = {How do I protect public webhook endpoints in Cursor's Agent SDK?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/protect-public-webhooks}}, note = {Revision 1; digest sha256:1737deb83660527d; last verified 2026-11-20T12:33:19Z; accessed 2026-11-21T10:03:42Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/permissions-and-security/protect-public-webhooks