sfcc-ocapi-hooks

To create and register OCAPI hooks in SFCC, place CommonJS scripts under cartridge/scripts/hooks and update hooks.json and package.json accordingly. This structure supports before, after, and modifyResponse hooks across shop, data, and content APIs.

OCAPI hooks in Salesforce Commerce Cloud are server-side extension points that let you inject custom logic into API request lifecycles. They enable you to validate incoming requests, enrich responses with custom attributes, and trigger external integrations without altering core platform code.

Yes, you can use OCAPI hooks to validate incoming SFCC API requests. By implementing before hooks, you can intercept and validate request payloads before they reach the core endpoint, ensuring adherence to security and reliability guidelines.

Before hooks intercept requests prior to core processing for validation, after hooks execute following core processing, and modifyResponse hooks alter the API response payload to enrich data with custom attributes.

Yes, SFCC OCAPI hooks must follow the CommonJS script structure. Adhering to this standard is required for proper hook registration and satisfies the platform's security, performance, and reliability guidelines.

OCAPI hooks maintain transactional integrity during external integrations by applying specific performance and reliability guidelines. You can trigger external calls within after or modifyResponse hooks while preserving transactional state.