Skip to main content

Hi Developers!

 

Here’s the latest from the November edition of our Developer Newsletter:

 

Product Launches & Updates

Klaviyo’s New APIs are Publicly Available!

Tailor Klaviyo to your needs and get more relevant data with less work using Klaviyo’s improved API surface.

Klaviyo recently rolled out new APIs including new endpoints such as catalogs, flows, and more, as well as enhanced API consistency.

 

Developer Showcase - 5 participants!

We’re looking for 5 individuals who are interested in working with us to build new 'Developer Showcases' (see example here). We want to highlight the integrations you’ve built and increase user adoption!

Let us know if you’re interested by reaching out to developers@klaviyo.com. We’d love to connect!

 

Featured Articles:

Getting Started as a Klaviyo Developer - Part 2: Mapping Data and Workflows to Klaviyo

In the first part of the series, we discussed how to model data and workflows (see article here). In this segment, we highlight how to map these models to technical components (e.g. websites, services, and Klaviyo). Read Part II here
 

Solution Recipe 12: Using Klaviyo’s Webhook Action to Send Slack Notifications

If your team already uses Slack for internal communication, imagine if notifications could be sent right to your sales team's Slack channel when a new lead subscribes to your brand. Learn how to set up a list-triggered flow to automate a Slack message using a Klaviyo webhook. Learn more here
 

Drinking Our Own Champagne #1: Using Klaviyo Webhooks to Sync Form Data into Salesforce
 

The new 'Drinking Our Own Champagne' series will discuss how we use Klaviyo internally to solve a variety of business and data challenges. In this first post, we discuss how we use Klaviyo’s webhook action in flows to sync signups in real-time to another business system that requires a special form of authentication and has a rigid data schema. Read more here

 

How-to’s & Guides:

Authentication & API Key Scopes

Check out our new authentication process and learn more about scopes for private API keys. Now, brands can easily toggle access to each private key they create (read-only, full, or customized access). Learn more

  

JSON:API - Filtering & Sorting

Learn more about how to easily query for specific data and control how that data is returned. For example, you can now filter based on comparing literals such as strings, booleans, integers, and more. Learn more

 

Most-Viewed Developer Community Posts

  1. How to Control $consent Via an API

  2. What is the Rough Time Estimate for Custom Integration?

 

We want to hear from YOU!

Please take a brief survey 0~3 min] to help us improve your developer experience. Take the survey here!

 

Developer Resources

Developer Portal | Klaviyo Developer Twitter | Klaviyo Developers Blog | Engineering Blog

Question, seeing the new API key & scopes guide, is there currently a method through which one can tell what the scopes are for a private API key? (beyond logging into the UI) As a developer, want to have an automatic way to tell if a client’s provided API key has sufficient scopes.


Hi @retina-dev and thanks for the question!

At this time, there’s no way to determine the scope permissions of a private API key at a glance. The only way to determine the exact scope is to have the owner or admin of the account tell you the scope/permission for the key, or delete and recreate the key while taking note of the scope.

 

I hope this helps to clarify, and thanks for using the Community!

 

- Brian


Reply