v4.1.1: Fix `LoyaltyLedgerEntry` parsing from API

• Fix LoyaltyLedgerEntry's type property values, failing to parse when retrieving values from the API
• Flag API operations that return total count in their name for better visibility

v4.1.0: Dry Runs & Coupons discount limits

• Introduce "dry runs" for Integration API endpoints (See more details below)
• Add support to retrieve coupons as part of requesting customer profile inventories
• Add support for setting the discountLimit when creating or editing coupons

Introduce "dry runs" for Integration API endpoints

You can read more about the concept and where this feature could apply in your integration and workflow in our developers documentation center: https://developers.talon.one/Integration-API/dry-requests

Please Notice that all current integration request operations (trackEvent, updateCustomerProfile, updateCustomerSession, updateCustomerSessionV2 ) expects a boolean flag to determine whether this request is a dry run or not.
See code examples in the README.md as for reference.

v4.0.0: Integration API V2

• Replace code generator to OpenAPITools generator@v.4.2.3
• Add our new v2 integration api endpoint for customer sessions. Read more here: https://developers.talon.one/Getting-Started/APIV2
• Add v2-related management endpoints for managing AdditionalCosts

⚠️ Breaking Change: Please notice the new distinction between integration_auth and api_key_v1 authentication strategies

From version 4.0.0 onwards, the integration_auth strategy will be use for legacy HMAC authentication only (in deprecation process).
For the correct usage of this strategy, please consult this piece of code in the README file.

If until today you used the integration_auth while initiating your ApiClient instance and set the api-key and prefix as advised before:

ApiClient iApiClient = new ApiClient("integration_auth");
IntegrationApi iApi = new IntegrationApi(iApiClient );
        
// Setup: basePath, apiKeyPrefix and apiKey
iApi.getApiClient().setBasePath("https://mycompany.talon.one");
iApi.getApiClient().setApiKeyPrefix("ApiKey-v1");
iApi.getApiClient().setApiKey("dbc644d33aa74d582bd9479c59e16f970fe13bf34a208c39d6c7fa7586968468");

// ...

Please notice that you will have to pass the api_key_v1 strategy from now on, the rest of the code could be used as before:

- ApiClient iApiClient = new ApiClient("integration_auth");
+ ApiClient iApiClient = new ApiClient("api_key_v1"); 

// ... no change

v3.5.0

• Expose new profile inventory endpoint. Consult our developer docs for more information: https://developers.talon.one/Integration-API/API-Reference#getCustomerInventory
• Expose more attributes handling endpoints (create, update, get all)
• copyCampaignToApplications endpoint extended and now allows to override original campaign's description scheduling details and tags as part of the copy functionality. See parameters here: https://developers.talon.one/Management-API/API-Reference#copyCampaignToApplications

v3.4.0 (#11)

• More filtering parameters when querying changes endpoint
• The full Coupon object is now returned as part of an integration response
• Support for new limit configuration of amount of give discount effects

v3.3.0

• Add ReferralRejectionReason object and integration response properties
• Add users emails notifications subscriptions
• Remove stale usedAt and locked properties from Webhooks and Attributes

v3.2.3

• SessionId property of Event object returned from integration API is optional

v3.2.2

• Remove ApplicationStorages deprecation
• LoyaltyMemberships of Profile entity are optional

v3.2.1

• Update coupon reservations endpoints
• Loyalty Programs subledgers support
• No more optional body parameters