---
schema_version: "1"
id: 46ac43bcfaa63d85388affd64f0340a45b3f4ea163a573584fdd70cda55d7d70
title: Using Hooks Securely in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_using_hooks_securely.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_using_hooks_securely.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1546dfe5ed63a0a18072d90c50d17c81d28515468020ecb3b3a37db2805d3966
description: In Salesforce B2C Commerce, you can use hooks as a powerful tool to extend default functionality. Like all powerful tools, however, hooks are dangerous if not used properly.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Using Hooks Securely in B2C Commerce

In Salesforce B2C Commerce, you can use hooks as a powerful tool to extend default functionality. Like all powerful tools, however, hooks are dangerous if not used properly.

Hooks in Open Commerce API (OCAPI) and Commerce Script can functionally change the platform operation of OCAPI and platform method calls. Be cautious when using hooks because unprivileged users can make privileged OCAPI or method calls. Also, because of the design placement of OCAPI hooks, a developer can inadvertently modify API calls to accept no authentication or to bypass expected authorization entirely. Use caution when chaining any calls on the platform.