API and SDK for custom frontends.
Use Arky from the frontend stack you already like. Fetch content, products, bookings, forms, contacts, and workflows while keeping custom code.
Best for
- Astro sites
- Next apps
- Svelte frontends
- custom storefronts
Use it as the SDK layer between Arky modules and the frontend stack your agency already prefers.
What this module gives your project.
Storefront APIs
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
SDK helpers
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Typed modules
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Webhooks
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Frontend freedom
Use this capability from your custom frontend while the operational side stays manageable in Arky admin.
Custom UX with backend state managed in Arky.
- One storefront store
- Typed SDK helpers
- Reactive state
- Framework-agnostic APIs
A client-facing back office for the same module.
- Store configuration
- Connected account settings
- API tokens for trusted jobs
- Webhook configuration
Code the frontend. Connect Arky as the backend.
Start with the frontend stack the project deserves, then connect only the Arky modules it needs. The Admin, API, SDK, and backend workflows stay behind the custom experience.
- Install the SDK
- Initialize Arky
- Use only the modules the project needs
import { initialize } from "arky-sdk/storefront";
const arky = initialize({
baseUrl: "https://api.arky.io",
storeId: "your-store-id",
locale: "en",
});
await arky.eshop.cart.load();
// Use the module helpers your frontend needs.
// The client keeps full control over markup, routing, and UX.Useful API touchpoints.
-
initialize({ baseUrl, storeId }) -
arky.eshop.cart.load() -
arky.cms.entry.get({ id })