v15.0.0

Version 15.0.0

v14.0.0

Version 14.0.0

v13.0.0

Version 13.0.0

v12.0.1

Fixed

• Fixed NPM package issue

v12.0.0

Added

• Added several method aliases based on previous operation IDs

Fixed

• Breaking
  • Removed incorrect links property from several DTO classes

11.0.0

Added

• Forms API
• New FormsApi class with methods to get forms, form versions and relationships.
• Webhooks API
• New WebooksApi class containing CRUD operations for webhooks.
• FilterBuilder class
  • New class to help build filters in the correct format for endpoints that use them.
  • See the README for more information and usage examples.

Changed

• ProfilesApi.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.

v10.1.0

Added

• Segments Api

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

• Flows Api

  • New delete flows endpoint FlowsApi.deleteFlow()

v10.0.1

[10.0.1] - revision 2024-05-15

Changed

• Fix bug in the ObjectSerializer class

v10.0.0

[10.0.0] - revision 2024-05-15

Added

• Bulk Create Events API
  • We have added support for creating events in bulk via the EventsApi.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

  • AccountsApi.getAccounts and AccountsApi.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 ProfilesApi.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.

v9.0.0

Move OAuth into GA