You are here:
Common HTTP Headers for B2C Commerce Events
Every B2C Commerce event includes the same set of standard x-sf-cc-*
headers, so your connector can identify and correlate events consistently regardless of the
event type.
| Header | Description | Example |
|---|---|---|
x-sf-cc-timestamp |
ISO-8601 timestamp when event was generated | 2026-03-11T13:31:13.755934395Z |
x-sf-cc-instance-id |
Instance identifier (lowercase) | zzzz_prd |
x-sf-cc-site-id |
Site identifier (empty for org-level operations) | RefArch or "" |
x-sf-cc-correlation-id |
Correlation ID for tracking across systems | 550e8400-e29b-41d4-a716-446655440000 |
x-sf-cc-event-id |
Event type identifier (matches the eventType in the
payload) |
sf.cc.replication.completed |
Notes
- All timestamps use ISO-8601 format with timezone indicator.
- Instance IDs are normalized to lowercase.
- Site ID is empty for organization-level operations (such as process-level replication, which runs at the organization level).
Did this article solve your issue?
Let us know so we can improve!
