Skip to content

Latest commit

 

History

History
179 lines (140 loc) · 10.2 KB

CHANGELOG.md

File metadata and controls

179 lines (140 loc) · 10.2 KB
Raw

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[5.1.0] - revision 2023-12-15

Added

  • New Endpoints: Bulk Profile Imports:
    • Profiles.spawn_bulk_profile_import_job
    • Profiles.get_bulk_profile_import_job
    • Profiles.get_bulk_profile_import_jobs
    • Profiles.get_bulk_profile_import_job_lists
    • Profiles.get_bulk_profile_import_job_profiles
    • Profiles.get_bulk_profile_import_job_import_errors
    • Profiles.get_bulk_profile_import_job_relationships_profiles
    • Profiles.get_bulk_profile_import_job_relationships_lists

Changed

[5.0.0] - revision 2023-10-15

Added

  • Support for returning list suppressions via the /profiles endpoint

    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

    • Use {additional_fields_profile = ["subscriptions"]} on these endpoints to include subscription information.

Changes

  • 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 {additional_fields_profile = ["subscriptions"]}s 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

[4.2.0] - revision 2023-09-15

Added

  • Images API
    • We now support the following operations to work with images:
      • get_image
      • get_images
      • update_image
      • upload_image_from_file
      • upload_image_from_url
  • Coupons API
    • We now support CRUD operations for both Coupons and Coupon Codes
    • Check out Coupons API guide for more information.
  • Additional filtering/sorting option for Lists and Segments: joined_group_at
  • New profile merge endpoint: Profiles.merge_profiles
  • Increased the maximum page size limit for List and Segment Profile Relationship Endpoints to 1000

[4.1.0] - revision 2023-08-15

Added

  • Flow Message Templates
  • You can now retrieve the templates associated with flow messages using Flows.get_flow_message_template() or Flows.get_flow_message_relationships_template() . You’re also able to include the template HTML for a flow message using Flows.get_flow_message(id, {"include": ["template"]}).
  • Create or Update Push Tokens
  • We have added an endpoint to create push tokens, Profiles.create_push_token(). 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.

[4.0.0] - revision 2023-07-15

Added

  • Back-In-stock APIs
  • 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

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 an object (instead of plural and an array)
        • example: for get_flow_action, if you want to use the include param, you would set include= to "flow" (instead of "flows")
      • 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 create_event, 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 get_campaigns endpoint, filter param is now required, to, at minimum, filter on messages.channel

Removed

[3.0.0] - revision 2023-06-15

Added

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

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
    • create_client_event
    • create_client_profile
    • create_client_subscription

[2.0.0] - 2023-04-06

Added

  • Profiles API now returns predictive analytics when calling get_profile and get_profiles by passing in additional_fields_profile: ["predictive_analytics"].

Changed

  • Relationship endpoints that were previously grouped together are now split into related-resource-specific endpoints.

Migration Guide

  • To migrate to this latest version, all calls to relationship endpoints need to be updated, as in the following example:
    • get_campaign_relationships(id, "tags") will become get_campaign_relationships_tags(id).

[1.2.0] - 2023-02-22

Added

  • Campagins (which were previously in our Beta API/SDKs)

Changes

  • Profiles
    • Fix longitude value in ProfileLocation type mapping
  • Flows
    • Pagination changed from page offset to cursor

[1.1.0] - 2022-01-24

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

[1.0.1] - 2022-12-06

Changes

  • Support for cursor pagination
    • Passing the next value from a paginated result to the following call via the page_cursor query string argument will now result in the cursor being parsed and set appropriately by the ApiClient.

[1.0.0] - 2022-10-19

Added

  • Initial release

Changes

  • Naming changes:
    • Package name: klaviyo_sdk -> klaviyo-api-sdk
    • Module name: KlaviyoBeta -> KlaviyoAPI
    • Some functions have changed name
  • New resources and endpoints:
    • See API Changelog for full details