Headless Method
Headless architecture in web development refers to a system design where the frontend (the presentation layer or "head") is completely decoupled from the backend (the content/data and logic). The frontend is not tightly integrated with the backend; instead, they communicate through web service calls (e.g., REST or GraphQL APIs). As a result, content and presentation remain separate concerns. Developers can build any type of UI (such as websites or mobile apps) on top of the same backend, reusing business logic across multiple channels. This decoupled approach provides flexibility, scalability, and the ability to deliver consistent data to various platforms (omnichannel) without requiring the reimplementation of backend logic for each interface.
The backend does not dictate how the data is displayed; instead, it simply serves the data. This contrasts with a traditional system, where the frontend and backend are tightly coupled. By going headless, developers gain complete control over the frontend experience while leveraging backend services for content management, commerce, and more.
Architecture Approach
The Fynd platform provides a comprehensive set of REST APIs and SDKs enabling developers to integrate its e-commerce capabilities into any application. In other words, you can use Fynd's backend services (product catalog, inventory, orders, etc.) without being tied to a specific frontend. Developers are free to craft custom UX on the frontend while Fynd's APIs supply all the needed data and functionality.
Methods
In this Headless section, we will explain two ways to integrate with Fynd Commerce:
- JavaScript Method: Use the official SDK to interact with Platform and Application APIs from Node.js or browser environments. See the overview and examples in JavaScript Method.
- cURL Method: Use raw HTTP requests to call REST APIs directly. Start with Authentication, then follow the cURL Method guide and example endpoints, such as List Categories and List Departments.