Klaviyo APIs: Which One Gets Your Order, Stock and Shipping Data Into Your Flows
Klaviyo is the email and SMS platform most e-commerce stores run abandoned-cart, post-purchase and win-back flows on. Its native integrations (Shopify above all) bring purchase data in for you. When orders, stock or shipping status live somewhere those integrations don't reach, Klaviyo's APIs are the way in, and there are several of them. Here's which one does what, which key it takes, and what to settle before anyone writes code.
Flows run on purchase and browsing data, but inventory, support history and the CRM aren't in the profile.
Stuck on Klaviyo? Let's solve it →Server-side API (/api paths): the full set, for profiles, events, catalogs, lists, flows and more. Authenticated with a private API key in the header. Never put this key in a browser.
Client-side API (/client paths): for code running on your storefront. Uses your 6-character public key (site ID), can only create certain things such as events and subscriptions, and returns nothing sensitive.
Webhooks out of Klaviyo: a Webhook action inside a flow POSTs JSON to your URL when a profile reaches that step. Account-wide system webhooks exist too, but managing them in the app is a CDP feature, and app partners reach them over OAuth.
Every request carries a dated revision header that picks the API version. Pin one and move up on purpose, rather than drifting.
Which Klaviyo API for which data
Start from where the data lives today. The examples are common store setups, not a specific client.
Settle these before the first API call
Each one is cheap to decide now and expensive to change after flows depend on it.
One private key per integration, with only the scopes it needs
Scopes are fixed when a key is created, and the full key is only shown once. Changing access means making a new key and swapping it in, so name keys after the system that uses them.
Event names and properties written down
Flows, segments and reports key off the exact metric name and property names. "Order Placed" from one system and "Placed Order" from another become two metrics nobody can combine.
A pinned revision, and a date to review it
Klaviyo dates its API versions and retires old ones. A pinned revision keeps responses stable until you choose to move.
What happens on a 429 or a timeout
Limits are per endpoint and per account, with a short burst window and a longer steady one. A sync that drops events on a busy sale day is the usual failure.
Who gets told when the feed stops
Flows don't complain when events stop arriving. They just go quiet, and nobody notices until revenue from that flow drops.
What this looks like when it works
Klaviyo's own flows do most of the lifecycle work well: welcome series, abandoned cart, browse abandonment, post-purchase and win-back are built in and trigger on what Klaviyo already sees. The API work is about what it doesn't see. A wholesale order placed through a portal, a subscription renewal from a separate billing tool, a parcel scanned at a 3PL: each becomes an event, and the flows you already have start firing on it.
Stock is the one stores feel most. When the storefront's count lags the warehouse, a reminder can push a product that's gone, or a back-in-stock alert goes out before the item is sellable. Feeding the catalog from the system that holds the real count fixes the email without touching the flow. The same goes for a VIP segment that should count wholesale and retail spend together.
n-frames builds and runs these feeds on Klaviyo's APIs: the event design, the catalog sync, the retries and the alert when something stops. Endpoint-level detail is on our Klaviyo API page, flow design on Klaviyo flows, and off-the-shelf options on Klaviyo integrations.
Questions people ask
What is Klaviyo used for?
Email and SMS marketing for online stores. Purchase history, browsing behavior and customer value drive its segments and automated flows such as abandoned cart, post-purchase follow-up and win-back. It's built around store data, so it suits e-commerce far better than a business with no orders flowing through it.
Is Klaviyo free, and how much does it cost?
There's a free tier for a small number of profiles and sends. Past that, the price scales with how many active profiles you have and whether you use email, SMS or both, so a single figure is misleading. Klaviyo's pricing page gives a current number for your list size. API access itself isn't sold separately.
Does Klaviyo only work with Shopify?
No. Shopify is the deepest integration, and there are native ones for BigCommerce, WooCommerce, Magento and several other platforms. A store on something outside that list, or a wholesale or B2B order system running alongside the store, gets its data in through the APIs instead.
Does Klaviyo handle marketing automation on its own?
For the standard e-commerce lifecycle, yes. The built-in flows for welcome, abandoned cart and post-purchase cover what most stores need. Where it runs short is anything depending on data it doesn't hold: live stock from another system, fulfillment status, or orders from a channel without a native integration.
How do I use Klaviyo if I'm just getting started?
Connect your store through the native integration, then switch on the built-in flows and edit them. Klaviyo's onboarding and help center cover that part well. The APIs only come into it once you have data the integration can't bring in.
Does Klaviyo have built-in automation, or do I need Zapier?
Klaviyo's flow builder handles automation triggered by anything it already knows: a purchase, a click, a signup, a property change. Zapier or a direct API connection is for events that start in a system Klaviyo can't see. At order volume, a direct connection with retries is usually the steadier choice.
What's the difference between Klaviyo's public and private API keys?
The public key is your 6-character site ID. It's safe in storefront code and only works with the client endpoints, which can create events and subscriptions. A private key unlocks the server-side API, can read and change your data within its scopes, and must stay on a server.
Who builds custom Klaviyo API integrations?
n-frames builds them: order and shipping events from systems Klaviyo doesn't integrate with, catalog and stock syncs from an ERP or 3PL, and webhook receivers that pass Klaviyo activity to your CRM or help desk, with monitoring so a stalled feed is caught early.