klaviyo/api

[19.0.0] - revision 2026-04-15

Added

• Conversations API
  • Send an outbound message to a profile with $klaviyo->Conversations->createConversationMessage(). Supports SMS and WhatsApp — the channel is determined automatically from the
    conversation. Conversation message endpoints use the SMALL rate limit tier (3 requests/second burst, 60 requests/minute steady).
  • Retrieve the conversation thread for a given profile with $klaviyo->Profiles->getConversationForProfile(), or include it inline on profile retrievals using include: ['conversation'] on getProfile / getProfiles.

Changed

• Drag-and-drop templates
  • Create drag-and-drop email templates programmatically by setting editor_type: SYSTEM_DRAGGABLE and providing a definition body (mutually exclusive with html) via
    $klaviyo->Templates->createTemplate(). DnD template endpoints use the SMALL rate limit tier (3 requests/second burst, 60 requests/minute steady).
  • List and retrieve drag-and-drop templates with $klaviyo->Templates->getTemplates() and $klaviyo->Templates->getTemplate(). Use additional_fields_template: ['definition'] to
    include the full template definition in the response.
  • Update an existing drag-and-drop template's definition, name, or text independently via $klaviyo->Templates->updateTemplate().

[18.0.0] - revision 2026-01-15

Added

• Added a new single data source record create endpoint for one-at-a-time ingestion workloads

Changed

• Breaking: removed anonymous_id from profile payloads

[17.0.0] - revision 2025-10-15

Added

Flow Actions API

• Get flow actions, flow messages, flow action IDs, and more with the Flow Actions API.
• Update flow actions within a flow, including associated message content, with the Update Flow Action endpoint.

Updated

Forms API

• Retrieve a form and its definition with the Forms API.
• Use the Create Form endpoint to generate a new form by providing the status, A/B test preference, and name of the form.

[16.0.0] - revision 2025-07-15

Changed

• Various changes to improve support for PHP 8
• Breaking: Now requires PHP 8.1
• Breaking: A SplFileObject is required for uploading an image; you can no longer use a raw string

[15.0.0] - revision 2025-07-15

Added

Mapped Metrics API

• Use the Mapped Metrics API to retrieve some or all mapped metrics in your Klaviyo account, or update a mapped metric.
• Get the metric, custom metric, or associated metric IDs for a given mapped metric.

Custom Objects API

• Use the Custom Objects API to ingest data records from other third-party sources into Klaviyo and retrieve all available data sources for an account.
• Use ingested data records to create custom objects in a Klaviyo account.

[14.0.2] - revision 2025-04-15

Added

• Added some PHPDoc type hints

[14.0.1] - revision 2025-04-15

Changed

• Removed API revision from comment on files

Added

Web Feeds API

• Create, retrieve, update, and/or delete web feeds via the Web Feeds API.
• Create universal content blocks referencing these web feeds with our Universal Content API.

Custom Metrics API

• Create, retrieve, update, and/or delete custom metrics via the Custom Metrics API.
• Report on custom metric conversions in our Campaign and Flow Reporting APIs (set the custom metric ID as the conversion_metric_id).

🚧

Standard accounts can only have 1 custom metric. Upgrade to Klaviyo's Advanced KDP or Marketing Analytics plan to create up to 50 custom metrics. To learn more about these plans, visit our billing guide.

Get and Delete Push Token APIs

• Retrieve and/or delete a given push token via Get Push Token and Delete Push Token APIs.
• Include push tokens on GET /api/profiles.
• We've added relationship endpoints for both profiles and push tokens:
  • Retrieve push tokens associated with a profile (GET /api/profiles/{ID}/push-tokens).
  • Get IDs for push tokens associated with a profile (GET /api/profiles/{ID}/relationships/push-tokens).
  • Retrieve the profile associated with a push token (GET /api/push-tokens/{ID}/profile).
  • Get ID for the profile associated with a push token (GET /api/push-tokens/{ID}/relationships/profile).

Changed

Campaigns API endpoints updated to support options for push notification badges

• Badge count settings are supported on the "campaign-message" resource for push messages.
  • The following options for incrementing badge count have been added to the Campaigns API: increment_one (increment by 1), set_count (increment by a given value), and set_property (increment by profile property).

Optional AMP MIME-type field for Templates API

• We've added support for creating and updating AMP versions of an email template through an optional amp field (under attributes) in our Create and Update Template APIs.
• This field requires AMP Email to be enabled. Refer to our AMP Email setup guide for more information.

Added

• Get and Update Reviews APIs
  • Retrieve all reviews with Reviews.getReviews or return a review with a specified ID using the Reviews.getReview endpoint.
  • Manage your reviews programmatically with the Reviews.updateReview endpoint, which allows you to change the status of a review, such as to reject or approve it. This endpoint modifies the moderation status of a review based on the provided review ID and status.
• Get and Create Flows APIs
  • Return a flow with the given flow ID using the Flows.getFlow endpoint.
  • Create a new flow with the Flows.createFlow endpoint.
• Campaigns API
  • Manage the images for your campaigns with a new set of endpoints for the Campaigns API, including: getImageForCampaignMessage, getImageIdForCampaignMessage, and updateImageForCampaignMessage.

Changed

• Breaking: Subscription endpoints required field
  • Calls to Profiles.bulkSubscribeProfiles and Profiles.unsubscribeProfiles now require the subscriptions field, which grants or revokes consent for the indicated message types on the specified channels, such as email or sms.
• Breaking: Campaigns API push notification support
  • The Campaigns API now supports the push notification channel.
  • Support for push notifications includes significant changes to the following endpoints: getCampaigns, getCampaign, createCampaign, updateCampaign, createCampaignClone, getMessagesForCampaign, getCampaignMessage, updateCampaignMessage, getCampaignForCampaignMessage, getCampaignIdForCampaignMessage.
  • We recommend that you review the Campaigns API Overview for more detailed information about changes to the structure and responses of these endpoints.
• Breaking: Pagination updates
  • The Flows.getMessagesForFlowAction and Flows.getActionIdForFlowMessage endpoints have been updated from offset pagination to cursor pagination.
• Create Template API
  • The Templates.createTemplate endpoint now supports the creation of hybrid templates when editorType is USER_DRAGGABLE and hybrid template HTML is included.
• Profiles API
  • The following server-side APIs have been updated to an enhanced identity resolution processor to better follow the Klaviyo identity resolution identifier priority order.
    • Profiles.createProfile
    • Profiles.updateProfile

Changed

• Updated REAME to use named arguments
• Some methods have been renamed- the old methods are now deprecated aliases

Fixed

• Updated Uploading Image From File section of README

Changed

• Breaking: Improved Retry Logic
  • To address 429 status codes, we have modified the retry logic to use exponential backoff and the Retry-After header. This is now the default behavior.
  • wait_seconds is now deprecated.

Added

• Universal Content API
  • Read, update, and delete universal content
  • For more information, see our Universal Content API overview
• Form Reporting API
  • Query form performance
  • For more information, see our Reporting API overview
• Segment Reporting API
  • Query segment growth data
  • For more information, see our Reporting API overview
• Reviews API
  • Get and list reviews
  • For more information, see our Reviews API overview
• Tracking Settings API
  • Read and update the Tracking Settings for an account (Account -> Settings -> UTM Tracking in UI)
  • For more information, see our Tracking Settings API documentation
• Metric Properties API
  • Access the properties for a given metric (e.g. "Placed Order")
  • For more information, see our Metric Properties API documentation
• Suppress/Unsuppress profile job APIs
  • Monitor the status of jobs created by Suppress Profiles and Unsuppress Profiles requests
  • For more information, see our Suppress Profiles Job API documentation

Changed

• Profiles.create_or_update_profile has been updated to an enhanced identity resolution processor to better follow the Klaviyo identity resolution identifier priority order
• Added support for $locale property for Profiles
• Numerous methods have been renamed as part of a large renaming effort - the old methods are now deprecated aliases

Added

• Added several method aliases based on previous operation IDs

Fixed

• Breaking
  • Removed incorrect $id parameter for Webhooks API functions

Added

• Forms API
• New klaviyo->Forms object with methods to get forms, form versions and relationships
• Webhooks API
• new klaviyo->Webooks class containing CRUD operations for webhooks

Changed

• Profiles->subscribe()
• added historical_import flag for importing historically consented profiles can now be optionally supplied in the payload for the Subscribe Profiles endpoint.
• When using this flag, a consented_at date must be provided and must be in the past.

Added

• Segments Api

  • New create segment endpoint $klaviyo->Segments->createSegment().
  • New delete segment endpoint $klaviyo->Segments->deleteSegment().
  • Updated exisiting segments endpoints to include the segment definition
  • For more information, see our Segments API overview.

• Flows Api

  • New delete flows endpoint $klaviyo->Flows->deleteFlow()

Added

• Bulk Create Events API with
  • We have added support for creating events in bulk via the $klaviyo->Events->bulkCreateEvents method
• Create multiple events for new and existing profiles and/or update profile properties in a single API call. For more information, see our Events API overview.

Changed

• Accounts Api

  • $klaviyo->Accounts->getAccounts and $klaviyo->Accounts->getAccount have been updated to return the account's locale, e.g. en-US.

• Breaking Subscribe API Synchronous Validation Improved

  • To provide better feedback for handling SMS subscriptions, we’ve added improved validation behavior to $klaviyo->Profiles->subscribeProfiles method. In prior revisions, such requests may appear as 202s but will fail to update SMS consent. To handle this issue, 400 validation errors are returned for the following cases
    1. If a profile is subscribed to SMS marketing and age-gating is enabled but age_gated_date_of_birth is not provided, or the DOB does not meet the region's requirements.
    2. If the account does not have a sending number in the phone number’s region.
    3. If the phone number is in a region not supported by Klaviyo.
    4. If consented_at is set and the list or global setting is double opt-in.

Fixed:

• Patched a bug due to incorrect handling of page_cursor

Fixed:

• Patched a bug due to colliding enum variable names

Added:

• Optional $user_agent_suffix param to client instantiation
  • example usage:

    $klaviyo = new KlaviyoAPI(
        'YOUR_API_KEY', 
        $num_retries = 3, 
        $wait_seconds = 3,
        $guzzle_options = [],
        $user_agent_suffix = "/YOUR_APP_NAME");
  

Added:

• New Reporting allows you to request campaign and flow performance data that you can view in the Klaviyo UI.

• campaignValuesQuery

  • Request campaign analytics data, for example, a campaign performance report on the open rate over the past 30 days.

• flowValuesQuery

  • Request flow analytics data, for example, a flow performance report on the revenue per recipient value over the past 3 months.

• flowSeriesQuery

  • Fetch flow series data for a specific interval and timeframe, for example, a flow performance report on weekly click rates over the past 12 months.

• New Profiles endpoint allows you to create or update a profile with a set of profile attributes.

  • createOrUpdateProfile
    • This endpoint operates synchronously and offers an upsert pattern similar to the v1/v2 Identify API.

Changed:

• Removed the $attribution field from event_properties in getEvent and getEvents (breaking change).

  • To include this data in your request, add include=attributions to your request.

Added

New Endpoints: Bulk Profile Imports

We have added the following endpoints to enable bulk profile imports:

• Profiles->spawnBulkProfileImportJob
• Profiles->getBulkProfileImportJob
• Profiles->getBulkProfileImportJobs
• Profiles->getBulkProfileImportJobLists
• Profiles->getBulkProfileImportJobProfiles
• Profiles->getBulkProfileImportJobImportErrors
• Profiles->getBulkProfileImportJobRelationshipsProfiles
• Profiles->getBulkProfileImportJobRelationshipsLists

Changed

Relationships field of Profiles->subscribeProfiles payload is now optional

When using Profiles->subscribeProfiles, the relationships field of the payload is now optional (see Profiles->subscribeProfiles reference for details).

Added

Support for returning list suppressions via the /profiles endpoint

We now support filtering on list suppression with the get profiles endpoint, which brings us to parity with v2 list suppression endpoint that was the previously recommended solution.

Rules for suppression filtering:

• You may not mix-and-match list and global filters
• You may only specify a single date filter
• You may or may not specify a reason
• You must specify a list_id to filter on any list suppression properties

Examples:

• To return profiles who were suppressed after a certain date:
  $filter="greater-than(subscriptions.email.marketing.suppression.timestamp,2023-03-01T01:00:00Z)"
• To return profiles who were suppressed from a specific list after a certain date:
  $filter="greater-than(subscriptions.email.marketing.list_suppressions.timestamp,2023-03-01T01:00:00Z),equals(subscriptions.email.marketing.list_suppressions.list_id,\"LIST_ID\")"
• To return all profiles who were suppressed for a specific reason after a certain date:
  $filter="greater-than(subscriptions.email.marketing.suppression.timestamp,2023-03-01T01:00:00Z),equals(subscriptions.email.marketing.suppression.reason,\"user_suppressed\")"

Optionally retrieve subscription status on Get List Profiles, Get Segment Profiles, Get Event Profile

Now you can retrieve subscription status on any endpoint that returns profiles, including Get List Profiles, Get Segment Profiles and Get Event Profile. Use $additional_fields_profile="subscriptions" on these endpoints to include subscription information.

Changed

Subscription object not returned by default on Get Profile / Get Profiles

The subscription object is no longer returned by default with get profile(s) requests. However, it can be included by adding the $additional_fields_profile="subscriptions" to the request. This change will allow us to provide a more performant experience when making requests to Get Profiles without including the subscriptions object.

Profile Subscription Fields Renamed

In the interest of providing more clarity and information on the subscription object, we have renamed several fields, and added several as well. This will provide more context on a contact's subscriptions and consent, as well as boolean fields to see who you can or cannot message.

For SMSMarketing:

• timestamp is now consent_timestamp
• last_updated is a new field that mirrors consent_timestamp
• can_receive_sms_marketing is a new field which is True if the profile is consented for SMS

For EmailMarketing:

• timestamp is now consent_timestamp
• can_receive_email_marketing is True if the profile does not have a global suppression
• suppressions is now suppression
• last_updated is a new field that is the most recent of all the dates on the object

Added

• Images API
  • We now support the following operations to work with images:
    • getImage
    • getImages
    • updateImage
    • uploadImageFromFile
    • uploadImageFromUrl
• Coupons API
  • We now support CRUD operations for both Coupons and Coupon Codes
  • Check out Coupons API guide for more information.
• New profile merge endpoint: Profiles->mergeProfiles
• Additional filtering/sorting option for getting profiles from Lists and Segments: joined_group_at
• Increased the maximum page size limit for Lists->getListRelationshipsProfiles and Segments->getSegmentRelationshipsProfiles to 1000

Added

• Flow Message Templates
• You can now retrieve the templates associated with flow messages using Flows->getFlowMessageTemplate() or Flows->getFlowMessageRelationshipsTemplate() . You’re also able to include the template HTML for a flow message using Flows->getFlowMessage($id, $include=['template']).
• Create or Update Push Tokens
• We have added an endpoint to create or update push tokens, Profiles->createPushToken(). This endpoint can be used to migrate profiles and their push tokens from another platform to Klaviyo. If you’re looking to register push tokens from users’ devices, please use our mobile SDKs.

Added

• Back-In-stock APIs
  • We have added support for subscribing profiles to back-in-stock notifications, for both email and SMS, using the new createBackInStockSubscription endpoint.
• New functionality to Campaigns API
  • CRUD support for SMS campaigns is now available
  • You can now also retrieve all messages for a campaign to determine performance data on campaigns where you're running A/B tests
    • To support this functionality, we introduced a relationship between campaigns and campaign messages, and between campaign messages and templates

Changed

• Relationship Standardization
  • We are making a number of changes across endpoints to standardize how we handle relationships in our APIs and leverage consistently typed objects across endpoints. For example, you can create a profile in our APIs in the same shape, regardless of whether you're calling the profiles endpoint or the events endpoint.
  • The changes include:
    • Updating 1:1 relationships to use singular tense and return an object (instead of plural and return an array)
      • example: for getFlowAction, if you want to use the include param, you would set include= to "flow" (instead of "flows"); the response will be an object (previously an array)
    • Moving related object IDs from the attributes payload to relationships
      • example: The format for the body of create_tag has changed, with tag_group_id previously at data.attributes.tag_group_id being removed and replaced by a data object containing type+id and located at data.relationships.tag-group.data.
    • Specifying a relationship between two Klaviyo objects to allow for improved consistency and greater interoperability across endpoints
      • example: for createEvent, you can now create/update a profile for an event in the same way you would when using the profiles API directly
  • NOTE: The examples for the above relationship changes are illustrative, not comprehensive. For a complete list of ALL the endpoints that have changed and exactly how, please refer to our latest API Changelog
• For getCampaigns endpoint, filter param is now required, to, at minimum, filter on messages.channel

Removed

• We removed the company_id from the response for getTemplate and getTemplates. If you need to obtain the company ID / public API key for an account, please use the Accounts API.

Added

• Accounts API is now available, this will allow you to access information about the Klaviyo account associated with your API key.
  • getAccounts
  • getAccount

Note: You will need to generate a new API key with either the Accounts scope enabled or Full Access to use these endpoints.

Removed

• All client endpoints
  • createClientEvent
  • createClientProfile
  • createClientSubscription

Changed

• Fixed order of params, and added page_size, so some calls may need to be updated.

Fixed

• Fixed a bug that caused paging through events to periodically fail.

Added

• Added support for Campaigns (which were previously in our Beta API/SDKs).

Changed

• Pagination for Flows changed from page offset to cursor.

Added

• Added the following endpoints (which were previously in our Beta API/SDKs):
  • Data Privacy
  • All Tags endpoints, as well as the following related resource-specific endpoints:
    • Get Flow Tags
    • Get List Tags
    • Get Segment Tags

Added

• Initial release

Changed

• Naming changes:
  • Packagist package name: klaviyo/sdk-beta → klaviyo/api
  • Namespace: KlaviyoBeta → KlaviyoAPI
  • client name: Client → KlaviyoAPI
  • Client variable name in readme examples: $client → $klaviyo
  • Some functions have changed name
• Parameter ordering: The order of params has changed; you will need to update these for your existing implementation to work