What You Build vs. What CC Provides
| You Build | CC Provides |
|---|---|
| Custom React/Vue/etc. frontend | Creator data API |
| Your own design system | Attribution engine |
| Custom user flows | Order tracking |
| Unique animations | Integration sync |
| Platform-specific features | Webhook infrastructure |
Architecture
API Endpoints
Read Creator Data
Read Attribution Metrics
SDK Alternative
For client-side, use the CC SDK:Common Patterns
Custom Landing Pages
Build React/Vue landing pages that fetch CC data:Hydrogen Storefront
Integrate CC into Shopify Hydrogen:Custom Partner Portal
Build your own partner dashboard:What You Still Get
Even building headless, CC handles:- Attribution — Order tracking, partner credit
- Integrations — Klaviyo, Flow, analytics sync
- Data Storage — Shopify metaobjects
- Webhooks — Event notifications
- Rate Limiting — Managed API access
When to Use
Use Headless API when:- You need complete UI control
- You’re building custom storefronts (Hydrogen, etc.)
- You have frontend development resources
- You want unique interactive experiences
- You’re building a platform for others
- You need complete infrastructure control
- You want to resell/license the solution
- You need multi-tenant architecture