Cartly v1.4: Developer Portal, Headless API & Cross-Border Markets
Full developer documentation portal with 12 guide pages, Headless Storefront API v1 with dual-token auth, Cross-Border Markets with multi-currency pricing, and GitHub Theme Sync.
Full developer documentation portal with 12 guide pages, Headless Storefront API v1 with dual-token auth, Cross-Border Markets with multi-currency pricing, and GitHub Theme Sync.
Cartly v1.4 is a developer-focused release that ships the tools needed to build production-grade headless storefronts, multi-region stores, and custom themes synced directly from GitHub.
The new Developer Portal brings together everything a developer needs to integrate with Cartly. Twelve comprehensive guide pages cover Authentication, Webhooks, the Storefront API, GraphQL, App Bridge, Liquid Themes, GitHub Theme Sync, Custom Data, App Extensions, Headless API, Cross-Border Markets, and Inventory management.
Each guide includes live code examples, endpoint references, and integration patterns — all versioned alongside the platform itself.
The new /storefront/v1/ endpoint group provides a complete headless commerce layer for custom frontends, mobile apps, and third-party integrations. Highlights include:
Merchants can now sell globally with native multi-currency and localisation support. Define Markets for each region, set per-market prices for every product variant, and let Cartly automatically route customers to the right market based on their IP address. Translated product titles, descriptions, and UI strings are served automatically once configured.
Connect your theme repository on GitHub and Cartly automatically deploys every push to your main branch. The OAuth flow takes under a minute: select your repo and branch, and a webhook is registered automatically. Theme files sync directly into the theme engine — no manual uploads, no FTP.
MetafieldDefinitions (16 field types) and MetaobjectDefinitions give merchants and developers a flexible schema system for extending any entity — products, orders, customers, collections — with structured custom data. All custom data is accessible via the GraphQL API and Liquid templates.