diff --git a/.openapi-generator/FILES b/.openapi-generator/FILES
index 459fe77..b57bbc8 100644
--- a/.openapi-generator/FILES
+++ b/.openapi-generator/FILES
@@ -220,6 +220,9 @@ docs/DeleteUserRequest.md
docs/Effect.md
docs/EffectEntity.md
docs/EmailEntity.md
+docs/EmbeddedAnalyticsConfiguration.md
+docs/EmbeddedAnalyticsConfigurationDashboards.md
+docs/EmbeddedDashboardConfiguration.md
docs/Endpoint.md
docs/Entity.md
docs/EntityWithTalangVisibleID.md
@@ -238,6 +241,9 @@ docs/Experiment.md
docs/ExperimentCampaignCopy.md
docs/ExperimentCopy.md
docs/ExperimentCopyExperiment.md
+docs/ExperimentListResults.md
+docs/ExperimentListResultsRequest.md
+docs/ExperimentResult.md
docs/ExperimentResults.md
docs/ExperimentVariant.md
docs/ExperimentVariantAllocation.md
@@ -316,6 +322,8 @@ docs/GetRulesets200Response.md
docs/GetUsers200Response.md
docs/GetWebhooks200Response.md
docs/Giveaway.md
+docs/GiveawayPoolNotification.md
+docs/GiveawayPoolNotificationData.md
docs/GiveawaysPool.md
docs/HiddenConditionsEffects.md
docs/History.md
@@ -559,6 +567,7 @@ docs/RoleV2PermissionSet.md
docs/RoleV2Permissions.md
docs/RoleV2Readonly.md
docs/RoleV2RolesGroup.md
+docs/RolesV2Thresholds.md
docs/RollbackAddedLoyaltyPointsEffectProps.md
docs/RollbackCouponEffectProps.md
docs/RollbackDeductedLoyaltyPointsEffectProps.md
@@ -567,6 +576,7 @@ docs/RollbackIncreasedAchievementProgressEffectProps.md
docs/RollbackReferralEffectProps.md
docs/Rule.md
docs/RuleFailureReason.md
+docs/RuleMetadata.md
docs/Ruleset.md
docs/SSOConfig.md
docs/SamlConnection.md
@@ -911,6 +921,9 @@ talon_one/models/delete_user_request.py
talon_one/models/effect.py
talon_one/models/effect_entity.py
talon_one/models/email_entity.py
+talon_one/models/embedded_analytics_configuration.py
+talon_one/models/embedded_analytics_configuration_dashboards.py
+talon_one/models/embedded_dashboard_configuration.py
talon_one/models/endpoint.py
talon_one/models/entity.py
talon_one/models/entity_with_talang_visible_id.py
@@ -929,6 +942,9 @@ talon_one/models/experiment.py
talon_one/models/experiment_campaign_copy.py
talon_one/models/experiment_copy.py
talon_one/models/experiment_copy_experiment.py
+talon_one/models/experiment_list_results.py
+talon_one/models/experiment_list_results_request.py
+talon_one/models/experiment_result.py
talon_one/models/experiment_results.py
talon_one/models/experiment_variant.py
talon_one/models/experiment_variant_allocation.py
@@ -1007,6 +1023,8 @@ talon_one/models/get_rulesets200_response.py
talon_one/models/get_users200_response.py
talon_one/models/get_webhooks200_response.py
talon_one/models/giveaway.py
+talon_one/models/giveaway_pool_notification.py
+talon_one/models/giveaway_pool_notification_data.py
talon_one/models/giveaways_pool.py
talon_one/models/hidden_conditions_effects.py
talon_one/models/history.py
@@ -1248,6 +1266,7 @@ talon_one/models/role_v2_permission_set.py
talon_one/models/role_v2_permissions.py
talon_one/models/role_v2_readonly.py
talon_one/models/role_v2_roles_group.py
+talon_one/models/roles_v2_thresholds.py
talon_one/models/rollback_added_loyalty_points_effect_props.py
talon_one/models/rollback_coupon_effect_props.py
talon_one/models/rollback_deducted_loyalty_points_effect_props.py
@@ -1256,6 +1275,7 @@ talon_one/models/rollback_increased_achievement_progress_effect_props.py
talon_one/models/rollback_referral_effect_props.py
talon_one/models/rule.py
talon_one/models/rule_failure_reason.py
+talon_one/models/rule_metadata.py
talon_one/models/ruleset.py
talon_one/models/saml_connection.py
talon_one/models/saml_connection_internal.py
@@ -1589,6 +1609,9 @@ test/test_delete_user_request.py
test/test_effect.py
test/test_effect_entity.py
test/test_email_entity.py
+test/test_embedded_analytics_configuration.py
+test/test_embedded_analytics_configuration_dashboards.py
+test/test_embedded_dashboard_configuration.py
test/test_endpoint.py
test/test_entity.py
test/test_entity_with_talang_visible_id.py
@@ -1607,6 +1630,9 @@ test/test_experiment.py
test/test_experiment_campaign_copy.py
test/test_experiment_copy.py
test/test_experiment_copy_experiment.py
+test/test_experiment_list_results.py
+test/test_experiment_list_results_request.py
+test/test_experiment_result.py
test/test_experiment_results.py
test/test_experiment_variant.py
test/test_experiment_variant_allocation.py
@@ -1685,6 +1711,8 @@ test/test_get_rulesets200_response.py
test/test_get_users200_response.py
test/test_get_webhooks200_response.py
test/test_giveaway.py
+test/test_giveaway_pool_notification.py
+test/test_giveaway_pool_notification_data.py
test/test_giveaways_pool.py
test/test_hidden_conditions_effects.py
test/test_history.py
@@ -1928,6 +1956,7 @@ test/test_role_v2_permission_set.py
test/test_role_v2_permissions.py
test/test_role_v2_readonly.py
test/test_role_v2_roles_group.py
+test/test_roles_v2_thresholds.py
test/test_rollback_added_loyalty_points_effect_props.py
test/test_rollback_coupon_effect_props.py
test/test_rollback_deducted_loyalty_points_effect_props.py
@@ -1936,6 +1965,7 @@ test/test_rollback_increased_achievement_progress_effect_props.py
test/test_rollback_referral_effect_props.py
test/test_rule.py
test/test_rule_failure_reason.py
+test/test_rule_metadata.py
test/test_ruleset.py
test/test_saml_connection.py
test/test_saml_connection_internal.py
diff --git a/.openapi-generator/VERSION b/.openapi-generator/VERSION
index 2540a3a..a29ba3d 100644
--- a/.openapi-generator/VERSION
+++ b/.openapi-generator/VERSION
@@ -1 +1 @@
-7.20.0
+7.21.0
diff --git a/README.md b/README.md
index 648db00..2a4c740 100644
--- a/README.md
+++ b/README.md
@@ -180,7 +180,6 @@ Class | Method | HTTP request | Description
*IntegrationApi* | [**get_loyalty_program_profile_transactions**](docs/IntegrationApi.md#get_loyalty_program_profile_transactions) | **GET** /v1/loyalty_programs/{loyaltyProgramId}/profile/{integrationId}/transactions | List customer's loyalty transactions
*IntegrationApi* | [**get_reserved_customers**](docs/IntegrationApi.md#get_reserved_customers) | **GET** /v1/coupon_reservations/customerprofiles/{couponValue} | List customers that have this coupon reserved
*IntegrationApi* | [**link_loyalty_card_to_profile**](docs/IntegrationApi.md#link_loyalty_card_to_profile) | **POST** /v2/loyalty_programs/{loyaltyProgramId}/cards/{loyaltyCardId}/link_profile | Link customer profile to card
-*IntegrationApi* | [**price_history**](docs/IntegrationApi.md#price_history) | **POST** /v1/best_prior_price_history | Get summary of price history
*IntegrationApi* | [**reopen_customer_session**](docs/IntegrationApi.md#reopen_customer_session) | **PUT** /v2/customer_sessions/{customerSessionId}/reopen | Reopen customer session
*IntegrationApi* | [**return_cart_items**](docs/IntegrationApi.md#return_cart_items) | **POST** /v2/customer_sessions/{customerSessionId}/returns | Return cart items
*IntegrationApi* | [**sync_catalog**](docs/IntegrationApi.md#sync_catalog) | **PUT** /v1/catalogs/{catalogId}/sync | Sync cart item catalog
@@ -338,6 +337,7 @@ Class | Method | HTTP request | Description
*ManagementApi* | [**list_experiments**](docs/ManagementApi.md#list_experiments) | **GET** /v1/applications/{applicationId}/experiments | List experiments
*ManagementApi* | [**list_stores**](docs/ManagementApi.md#list_stores) | **GET** /v1/applications/{applicationId}/stores | List stores
*ManagementApi* | [**okta_event_handler_challenge**](docs/ManagementApi.md#okta_event_handler_challenge) | **GET** /v1/provisioning/okta | Validate Okta API ownership
+*ManagementApi* | [**price_history**](docs/ManagementApi.md#price_history) | **POST** /v1/applications/{applicationId}/price_history | Get summary of price history
*ManagementApi* | [**remove_loyalty_points**](docs/ManagementApi.md#remove_loyalty_points) | **PUT** /v1/loyalty_programs/{loyaltyProgramId}/profile/{integrationId}/deduct_points | Deduct points from customer profile
*ManagementApi* | [**reset_password**](docs/ManagementApi.md#reset_password) | **POST** /v1/reset_password | Reset password
*ManagementApi* | [**scim_create_group**](docs/ManagementApi.md#scim_create_group) | **POST** /v1/provisioning/scim/Groups | Create SCIM group
@@ -587,6 +587,9 @@ Class | Method | HTTP request | Description
- [Effect](docs/Effect.md)
- [EffectEntity](docs/EffectEntity.md)
- [EmailEntity](docs/EmailEntity.md)
+- [EmbeddedAnalyticsConfiguration](docs/EmbeddedAnalyticsConfiguration.md)
+- [EmbeddedAnalyticsConfigurationDashboards](docs/EmbeddedAnalyticsConfigurationDashboards.md)
+- [EmbeddedDashboardConfiguration](docs/EmbeddedDashboardConfiguration.md)
- [Endpoint](docs/Endpoint.md)
- [Entity](docs/Entity.md)
- [EntityWithTalangVisibleID](docs/EntityWithTalangVisibleID.md)
@@ -605,6 +608,9 @@ Class | Method | HTTP request | Description
- [ExperimentCampaignCopy](docs/ExperimentCampaignCopy.md)
- [ExperimentCopy](docs/ExperimentCopy.md)
- [ExperimentCopyExperiment](docs/ExperimentCopyExperiment.md)
+- [ExperimentListResults](docs/ExperimentListResults.md)
+- [ExperimentListResultsRequest](docs/ExperimentListResultsRequest.md)
+- [ExperimentResult](docs/ExperimentResult.md)
- [ExperimentResults](docs/ExperimentResults.md)
- [ExperimentVariant](docs/ExperimentVariant.md)
- [ExperimentVariantAllocation](docs/ExperimentVariantAllocation.md)
@@ -683,6 +689,8 @@ Class | Method | HTTP request | Description
- [GetUsers200Response](docs/GetUsers200Response.md)
- [GetWebhooks200Response](docs/GetWebhooks200Response.md)
- [Giveaway](docs/Giveaway.md)
+- [GiveawayPoolNotification](docs/GiveawayPoolNotification.md)
+- [GiveawayPoolNotificationData](docs/GiveawayPoolNotificationData.md)
- [GiveawaysPool](docs/GiveawaysPool.md)
- [HiddenConditionsEffects](docs/HiddenConditionsEffects.md)
- [History](docs/History.md)
@@ -924,6 +932,7 @@ Class | Method | HTTP request | Description
- [RoleV2Permissions](docs/RoleV2Permissions.md)
- [RoleV2Readonly](docs/RoleV2Readonly.md)
- [RoleV2RolesGroup](docs/RoleV2RolesGroup.md)
+- [RolesV2Thresholds](docs/RolesV2Thresholds.md)
- [RollbackAddedLoyaltyPointsEffectProps](docs/RollbackAddedLoyaltyPointsEffectProps.md)
- [RollbackCouponEffectProps](docs/RollbackCouponEffectProps.md)
- [RollbackDeductedLoyaltyPointsEffectProps](docs/RollbackDeductedLoyaltyPointsEffectProps.md)
@@ -932,6 +941,7 @@ Class | Method | HTTP request | Description
- [RollbackReferralEffectProps](docs/RollbackReferralEffectProps.md)
- [Rule](docs/Rule.md)
- [RuleFailureReason](docs/RuleFailureReason.md)
+- [RuleMetadata](docs/RuleMetadata.md)
- [Ruleset](docs/Ruleset.md)
- [SSOConfig](docs/SSOConfig.md)
- [SamlConnection](docs/SamlConnection.md)
@@ -1060,15 +1070,3 @@ Authentication schemes defined for the API:
- **API key parameter name**: Authorization
- **Location**: HTTP header
-### manager_auth
-
-- **Type**: API key
-- **API key parameter name**: Authorization
-- **Location**: HTTP header
-
-### management_key
-
-- **Type**: API key
-- **API key parameter name**: Authorization
-- **Location**: HTTP header
-
diff --git a/docs/ActivateLoyaltyPoints.md b/docs/ActivateLoyaltyPoints.md
index 872ecc1..8fa2388 100644
--- a/docs/ActivateLoyaltyPoints.md
+++ b/docs/ActivateLoyaltyPoints.md
@@ -6,7 +6,7 @@ Activate loyalty points
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**transaction_uuids** | **List[UUID]** | An array of transaction UUIDs used to activate specific pending point transactions. If provided, do not include the `sessionId` parameter. | [optional]
+**transaction_uuids** | **List[UUID]** | An array of transaction UUIDs used to activate specific pending point transactions. If provided, do not include the `sessionId` parameter. | [optional]
**session_id** | **str** | The ID of the session containing the pending point transactions to activate. If provided, do not include the `transactionUUIDs` parameter. | [optional]
## Example
diff --git a/docs/AddPriceAdjustmentCatalogAction.md b/docs/AddPriceAdjustmentCatalogAction.md
index 9203683..05187f7 100644
--- a/docs/AddPriceAdjustmentCatalogAction.md
+++ b/docs/AddPriceAdjustmentCatalogAction.md
@@ -1,6 +1,6 @@
# AddPriceAdjustmentCatalogAction
-The specific properties of the \"ADD_PRICE_ADJUSTMENT\" catalog sync action.
+The specific properties of the \"ADD_PRICE_ADJUSTMENT\" catalog sync action. **Note:** You can only use this object if the `Beta` **price types** feature is enabled for your Application. To enable it, contact your Technical Account Manager.
## Properties
diff --git a/docs/ApplicationCustomer.md b/docs/ApplicationCustomer.md
index 9e7c509..53e5b40 100644
--- a/docs/ApplicationCustomer.md
+++ b/docs/ApplicationCustomer.md
@@ -8,13 +8,13 @@ Name | Type | Description | Notes
**id** | **int** | The internal ID of the customer profile. |
**created** | **datetime** | The time this entity was created. |
**integration_id** | **str** | The integration ID set by your integration layer. |
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
**account_id** | **int** | The ID of the Talon.One account that owns this profile. |
**closed_sessions** | **int** | The total number of closed sessions. Does not include closed sessions that have been cancelled or reopened. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states). |
**total_sales** | **float** | The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. |
**loyalty_memberships** | [**List[LoyaltyMembership]**](LoyaltyMembership.md) | **DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. | [optional]
**audience_memberships** | [**List[AudienceMembership]**](AudienceMembership.md) | The audiences the customer belongs to. | [optional]
-**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. |
+**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. |
**sandbox** | **bool** | An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). | [optional]
**advocate_integration_id** | **str** | The Integration ID of the Customer Profile that referred this Customer in the Application. | [optional]
diff --git a/docs/AudienceCustomer.md b/docs/AudienceCustomer.md
index ed0aa14..47b3b61 100644
--- a/docs/AudienceCustomer.md
+++ b/docs/AudienceCustomer.md
@@ -8,13 +8,13 @@ Name | Type | Description | Notes
**id** | **int** | The internal ID of the customer profile. |
**created** | **datetime** | The time this entity was created. |
**integration_id** | **str** | The integration ID set by your integration layer. |
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
**account_id** | **int** | The ID of the Talon.One account that owns this profile. |
**closed_sessions** | **int** | The total number of closed sessions. Does not include closed sessions that have been cancelled or reopened. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states). |
**total_sales** | **float** | The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. |
**loyalty_memberships** | [**List[LoyaltyMembership]**](LoyaltyMembership.md) | **DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. | [optional]
**audience_memberships** | [**List[AudienceMembership]**](AudienceMembership.md) | The audiences the customer belongs to. | [optional]
-**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. |
+**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. |
**sandbox** | **bool** | An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). | [optional]
**connected_applications_ids** | **List[int]** | A list of the IDs of the Applications that are connected to this customer profile. | [optional]
**connected_audiences** | **List[int]** | A list of the IDs of the audiences that are connected to this customer profile. | [optional]
diff --git a/docs/BaseCampaign.md b/docs/BaseCampaign.md
index bf8f489..e134731 100644
--- a/docs/BaseCampaign.md
+++ b/docs/BaseCampaign.md
@@ -11,7 +11,7 @@ Name | Type | Description | Notes
**end_time** | **datetime** | Timestamp when the campaign will become inactive. | [optional]
**attributes** | **object** | Arbitrary properties associated with this campaign. | [optional]
**state** | **str** | A disabled or archived campaign is not evaluated for rules or coupons. | [default to 'enabled']
-**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
+**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
**tags** | **List[str]** | A list of tags for the campaign. |
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. | [optional]
**features** | **List[str]** | The features enabled in this campaign. |
@@ -21,6 +21,7 @@ Name | Type | Description | Notes
**campaign_groups** | **List[int]** | The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. | [optional]
**type** | **str** | The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. | [optional] [default to 'advanced']
**linked_store_ids** | **List[int]** | A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
## Example
diff --git a/docs/Campaign.md b/docs/Campaign.md
index a942f51..8116c22 100644
--- a/docs/Campaign.md
+++ b/docs/Campaign.md
@@ -15,7 +15,7 @@ Name | Type | Description | Notes
**end_time** | **datetime** | Timestamp when the campaign will become inactive. | [optional]
**attributes** | **object** | Arbitrary properties associated with this campaign. | [optional]
**state** | **str** | A disabled or archived campaign is not evaluated for rules or coupons. | [default to 'enabled']
-**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
+**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
**tags** | **List[str]** | A list of tags for the campaign. |
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. |
**features** | **List[str]** | The features enabled in this campaign. |
@@ -25,6 +25,7 @@ Name | Type | Description | Notes
**campaign_groups** | **List[int]** | The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. | [optional]
**type** | **str** | The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. | [optional] [default to 'advanced']
**linked_store_ids** | **List[int]** | A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
**budgets** | [**List[CampaignBudget]**](CampaignBudget.md) | A list of all the budgets that are defined by this campaign and their usage. **Note:** Budgets that are not defined do not appear in this list and their usage is not counted until they are defined. | [optional]
**coupon_redemption_count** | **int** | This property is **deprecated**. The count should be available under *budgets* property. Number of coupons redeemed in the campaign. | [optional]
**referral_redemption_count** | **int** | This property is **deprecated**. The count should be available under *budgets* property. Number of referral codes redeemed in the campaign. | [optional]
diff --git a/docs/CartItem.md b/docs/CartItem.md
index 94eb95e..3cf6d07 100644
--- a/docs/CartItem.md
+++ b/docs/CartItem.md
@@ -8,8 +8,8 @@ Name | Type | Description | Notes
**name** | **str** | Name of item. | [optional]
**sku** | **str** | Stock keeping unit of item. |
**quantity** | **int** | Number of units of this item. Due to [cart item flattening](https://docs.talon.one/docs/product/rules/understanding-cart-item-flattening), if you provide a quantity greater than 1, the item will be split in as many items as the provided quantity. This will impact the number of **per-item** effects triggered from your campaigns. |
-**returned_quantity** | **int** | Number of returned items, calculated internally based on returns of this item. | [optional]
-**remaining_quantity** | **int** | Remaining quantity of the item, calculated internally based on returns of this item. | [optional]
+**returned_quantity** | **int** | Number of returned items, calculated internally based on returns of this item. | [optional] [readonly]
+**remaining_quantity** | **int** | Remaining quantity of the item, calculated internally based on returns of this item. | [optional] [readonly]
**price** | **float** | Price of the item in the currency defined by your Application. This field is required if this item is not part of a [catalog](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). If it is part of a catalog, setting a price here overrides the price from the catalog. | [optional]
**category** | **str** | Type, group or model of the item. | [optional]
**product** | [**Product**](Product.md) | | [optional]
@@ -17,15 +17,15 @@ Name | Type | Description | Notes
**height** | **float** | Height of item in mm. | [optional]
**width** | **float** | Width of item in mm. | [optional]
**length** | **float** | Length of item in mm. | [optional]
-**position** | **float** | Position of the Cart Item in the Cart (calculated internally). | [optional]
+**position** | **float** | Position of the Cart Item in the Cart (calculated internally). | [optional] [readonly]
**attributes** | **object** | Use this property to set a value for the attributes of your choice. [Attributes](https://docs.talon.one/docs/dev/concepts/attributes) represent any information to attach to this cart item. Custom _cart item_ attributes must be created in the Campaign Manager before you set them with this property. **Note:** Any previously defined attributes that you do not include in the array will be removed. | [optional]
**additional_costs** | [**Dict[str, AdditionalCost]**](AdditionalCost.md) | Use this property to set a value for the additional costs of this item, such as a shipping cost. They must be created in the Campaign Manager before you set them with this property. See [Managing additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs). | [optional]
-**catalog_item_id** | **int** | The catalog item ID. | [optional]
-**selected_price_type** | **str** | The selected price type for this cart item (e.g. the price for members only). | [optional]
-**adjustment_reference_id** | **UUID** | The reference ID of the selected price adjustment for this cart item. Only returned if the selected price resulted from a price adjustment. | [optional]
-**adjustment_effective_from** | **datetime** | The date and time from which the price adjustment is effective. Only returned if the selected price resulted from a price adjustment that contains this field. | [optional]
-**adjustment_effective_until** | **datetime** | The date and time until which the price adjustment is effective. Only returned if the selected price resulted from a price adjustment that contains this field. | [optional]
-**prices** | [**Dict[str, PriceDetail]**](PriceDetail.md) | A map of keys and values representing the price types and related price adjustment details for this cart item. The keys correspond to the `priceType` names. | [optional]
+**catalog_item_id** | **int** | The catalog item ID. | [optional] [readonly]
+**selected_price_type** | **str** | The selected price type for this cart item (e.g. the price for members only). | [optional] [readonly]
+**adjustment_reference_id** | **UUID** | The reference ID of the selected price adjustment for this cart item. Only returned if the selected price resulted from a price adjustment. | [optional] [readonly]
+**adjustment_effective_from** | **datetime** | The date and time from which the price adjustment is effective. Only returned if the selected price resulted from a price adjustment that contains this field. | [optional] [readonly]
+**adjustment_effective_until** | **datetime** | The date and time until which the price adjustment is effective. Only returned if the selected price resulted from a price adjustment that contains this field. | [optional] [readonly]
+**prices** | [**Dict[str, PriceDetail]**](PriceDetail.md) | A map of keys and values representing the price types and related price adjustment details for this cart item. The keys correspond to the `priceType` names. | [optional] [readonly]
## Example
diff --git a/docs/CustomerProfile.md b/docs/CustomerProfile.md
index a8a142f..ddaaf1d 100644
--- a/docs/CustomerProfile.md
+++ b/docs/CustomerProfile.md
@@ -8,13 +8,13 @@ Name | Type | Description | Notes
**id** | **int** | The internal ID of the customer profile. |
**created** | **datetime** | The time this entity was created. |
**integration_id** | **str** | The integration ID set by your integration layer. |
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
**account_id** | **int** | The ID of the Talon.One account that owns this profile. |
**closed_sessions** | **int** | The total number of closed sessions. Does not include closed sessions that have been cancelled or reopened. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states). |
**total_sales** | **float** | The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. |
**loyalty_memberships** | [**List[LoyaltyMembership]**](LoyaltyMembership.md) | **DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. | [optional]
**audience_memberships** | [**List[AudienceMembership]**](AudienceMembership.md) | The audiences the customer belongs to. | [optional]
-**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. |
+**last_activity** | **datetime** | Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. |
**sandbox** | **bool** | An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). | [optional]
## Example
diff --git a/docs/CustomerProfileAudienceRequestItem.md b/docs/CustomerProfileAudienceRequestItem.md
index 26144ff..446df4d 100644
--- a/docs/CustomerProfileAudienceRequestItem.md
+++ b/docs/CustomerProfileAudienceRequestItem.md
@@ -7,7 +7,7 @@ Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**action** | **str** | Defines the action to perform: - `add`: Adds the customer profile to the audience. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `delete`: Removes the customer profile from the audience. |
**profile_integration_id** | **str** | The ID of this customer profile in the third-party integration. |
-**audience_id** | **int** | The ID of the audience. You get it via the `id` property when [creating an audience](#operation/createAudienceV2). |
+**audience_id** | **int** | The ID of the audience. You get it via the `id` property when [creating an audience](#tag/Audiences/operation/createAudienceV2). |
## Example
diff --git a/docs/CustomerProfileIntegrationRequestV2.md b/docs/CustomerProfileIntegrationRequestV2.md
index 21eb8a2..49d43f2 100644
--- a/docs/CustomerProfileIntegrationRequestV2.md
+++ b/docs/CustomerProfileIntegrationRequestV2.md
@@ -5,7 +5,7 @@
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
**evaluable_campaign_ids** | **List[int]** | When using the `dry` query parameter, use this property to list the campaign to be evaluated by the Rule Engine. These campaigns will be evaluated, even if they are disabled, allowing you to test specific campaigns before activating them. | [optional]
**response_content** | **List[str]** | Extends the response with the chosen data entities. Use this property to get as much data back as needed from one request instead of sending extra requests to other endpoints. | [optional]
**audiences_changes** | [**ProfileAudiencesChanges**](ProfileAudiencesChanges.md) | Audiences memberships changes for this profile. | [optional]
diff --git a/docs/CustomerSessionV2.md b/docs/CustomerSessionV2.md
index 7a922ba..3cd3fc9 100644
--- a/docs/CustomerSessionV2.md
+++ b/docs/CustomerSessionV2.md
@@ -20,7 +20,7 @@ Name | Type | Description | Notes
**experiment_variant_allocations** | [**List[ExperimentVariantAllocation]**](ExperimentVariantAllocation.md) | The experiment variant allocations to add to this session. | [optional]
**additional_costs** | [**Dict[str, AdditionalCost]**](AdditionalCost.md) | Use this property to set a value for the additional costs of this session, such as a shipping cost. They must be created in the Campaign Manager before you set them with this property. See [Managing additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs). | [optional]
**identifiers** | **List[str]** | Session custom identifiers that you can set limits on or use inside your rules. For example, you can use IP addresses as identifiers to potentially identify devices and limit discounts abuse in case of customers creating multiple accounts. See the [tutorial](https://docs.talon.one/docs/dev/tutorials/using-identifiers). **Important**: Ensure the session contains an identifier by the time you close it if: - You [create a unique identifier budget](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets/#budget-types) for your campaign. - Your campaign has [coupons](https://docs.talon.one/docs/product/campaigns/coupons/coupon-page-overview). - We recommend passing an anonymized (hashed) version of the identifier value. | [optional]
-**attributes** | **object** | Use this property to set a value for the attributes of your choice. Attributes represent any information to attach to your session, like the shipping city. You can use [built-in attributes](https://docs.talon.one/docs/dev/concepts/attributes#built-in-attributes) or [custom ones](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes). Custom attributes must be created in the Campaign Manager before you set them with this property. | [optional]
+**attributes** | **Dict[str, object]** | Use this property to set a value for the attributes of your choice. Attributes represent any information to attach to your session, like the shipping city. You can use [built-in attributes](https://docs.talon.one/docs/dev/concepts/attributes#built-in-attributes) or [custom ones](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes). Custom attributes must be created in the Campaign Manager before you set them with this property. | [optional]
**first_session** | **bool** | Indicates whether this is the first session for the customer's profile. It's always `true` for anonymous sessions. |
**update_count** | **int** | The number of times the session was updated. When the session is created, this value is initialized to `1`. |
**total** | **float** | The total value of cart items and additional costs in the session, before any discounts are applied. |
diff --git a/docs/EmbeddedAnalyticsConfiguration.md b/docs/EmbeddedAnalyticsConfiguration.md
new file mode 100644
index 0000000..19d5590
--- /dev/null
+++ b/docs/EmbeddedAnalyticsConfiguration.md
@@ -0,0 +1,29 @@
+# EmbeddedAnalyticsConfiguration
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**dashboards** | [**EmbeddedAnalyticsConfigurationDashboards**](EmbeddedAnalyticsConfigurationDashboards.md) | |
+
+## Example
+
+```python
+from talon_one.models.embedded_analytics_configuration import EmbeddedAnalyticsConfiguration
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of EmbeddedAnalyticsConfiguration from a JSON string
+embedded_analytics_configuration_instance = EmbeddedAnalyticsConfiguration.from_json(json)
+# print the JSON string representation of the object
+print(EmbeddedAnalyticsConfiguration.to_json())
+
+# convert the object into a dict
+embedded_analytics_configuration_dict = embedded_analytics_configuration_instance.to_dict()
+# create an instance of EmbeddedAnalyticsConfiguration from a dict
+embedded_analytics_configuration_from_dict = EmbeddedAnalyticsConfiguration.from_dict(embedded_analytics_configuration_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/EmbeddedAnalyticsConfigurationDashboards.md b/docs/EmbeddedAnalyticsConfigurationDashboards.md
new file mode 100644
index 0000000..1161a02
--- /dev/null
+++ b/docs/EmbeddedAnalyticsConfigurationDashboards.md
@@ -0,0 +1,29 @@
+# EmbeddedAnalyticsConfigurationDashboards
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**campaign_insights** | [**EmbeddedDashboardConfiguration**](EmbeddedDashboardConfiguration.md) | The configuration of the embedded Insights dashboard for campaigns. | [optional]
+
+## Example
+
+```python
+from talon_one.models.embedded_analytics_configuration_dashboards import EmbeddedAnalyticsConfigurationDashboards
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of EmbeddedAnalyticsConfigurationDashboards from a JSON string
+embedded_analytics_configuration_dashboards_instance = EmbeddedAnalyticsConfigurationDashboards.from_json(json)
+# print the JSON string representation of the object
+print(EmbeddedAnalyticsConfigurationDashboards.to_json())
+
+# convert the object into a dict
+embedded_analytics_configuration_dashboards_dict = embedded_analytics_configuration_dashboards_instance.to_dict()
+# create an instance of EmbeddedAnalyticsConfigurationDashboards from a dict
+embedded_analytics_configuration_dashboards_from_dict = EmbeddedAnalyticsConfigurationDashboards.from_dict(embedded_analytics_configuration_dashboards_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/EmbeddedDashboardConfiguration.md b/docs/EmbeddedDashboardConfiguration.md
new file mode 100644
index 0000000..edd038d
--- /dev/null
+++ b/docs/EmbeddedDashboardConfiguration.md
@@ -0,0 +1,30 @@
+# EmbeddedDashboardConfiguration
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**workspace_id** | **str** | The ID of the workspace that contains dashboards. |
+**dashboard_id** | **str** | The ID of the dashboard that contains metrics. |
+
+## Example
+
+```python
+from talon_one.models.embedded_dashboard_configuration import EmbeddedDashboardConfiguration
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of EmbeddedDashboardConfiguration from a JSON string
+embedded_dashboard_configuration_instance = EmbeddedDashboardConfiguration.from_json(json)
+# print the JSON string representation of the object
+print(EmbeddedDashboardConfiguration.to_json())
+
+# convert the object into a dict
+embedded_dashboard_configuration_dict = embedded_dashboard_configuration_instance.to_dict()
+# create an instance of EmbeddedDashboardConfiguration from a dict
+embedded_dashboard_configuration_from_dict = EmbeddedDashboardConfiguration.from_dict(embedded_dashboard_configuration_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/ExperimentListResults.md b/docs/ExperimentListResults.md
new file mode 100644
index 0000000..c7cf258
--- /dev/null
+++ b/docs/ExperimentListResults.md
@@ -0,0 +1,29 @@
+# ExperimentListResults
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**results** | [**List[ExperimentResult]**](ExperimentResult.md) | | [optional]
+
+## Example
+
+```python
+from talon_one.models.experiment_list_results import ExperimentListResults
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of ExperimentListResults from a JSON string
+experiment_list_results_instance = ExperimentListResults.from_json(json)
+# print the JSON string representation of the object
+print(ExperimentListResults.to_json())
+
+# convert the object into a dict
+experiment_list_results_dict = experiment_list_results_instance.to_dict()
+# create an instance of ExperimentListResults from a dict
+experiment_list_results_from_dict = ExperimentListResults.from_dict(experiment_list_results_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/ExperimentListResultsRequest.md b/docs/ExperimentListResultsRequest.md
new file mode 100644
index 0000000..b3a64f9
--- /dev/null
+++ b/docs/ExperimentListResultsRequest.md
@@ -0,0 +1,29 @@
+# ExperimentListResultsRequest
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**experiment_ids** | **List[int]** | |
+
+## Example
+
+```python
+from talon_one.models.experiment_list_results_request import ExperimentListResultsRequest
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of ExperimentListResultsRequest from a JSON string
+experiment_list_results_request_instance = ExperimentListResultsRequest.from_json(json)
+# print the JSON string representation of the object
+print(ExperimentListResultsRequest.to_json())
+
+# convert the object into a dict
+experiment_list_results_request_dict = experiment_list_results_request_instance.to_dict()
+# create an instance of ExperimentListResultsRequest from a dict
+experiment_list_results_request_from_dict = ExperimentListResultsRequest.from_dict(experiment_list_results_request_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/ExperimentResult.md b/docs/ExperimentResult.md
new file mode 100644
index 0000000..6a4e126
--- /dev/null
+++ b/docs/ExperimentResult.md
@@ -0,0 +1,31 @@
+# ExperimentResult
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**variants** | [**List[ExperimentVariantResult]**](ExperimentVariantResult.md) | |
+**confidence** | [**ExperimentVariantResultConfidence**](ExperimentVariantResultConfidence.md) | |
+**experiment_id** | **int** | |
+
+## Example
+
+```python
+from talon_one.models.experiment_result import ExperimentResult
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of ExperimentResult from a JSON string
+experiment_result_instance = ExperimentResult.from_json(json)
+# print the JSON string representation of the object
+print(ExperimentResult.to_json())
+
+# convert the object into a dict
+experiment_result_dict = experiment_result_instance.to_dict()
+# create an instance of ExperimentResult from a dict
+experiment_result_from_dict = ExperimentResult.from_dict(experiment_result_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/ExperimentResults.md b/docs/ExperimentResults.md
index fb29aa7..a3074d2 100644
--- a/docs/ExperimentResults.md
+++ b/docs/ExperimentResults.md
@@ -5,7 +5,7 @@
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**variants** | [**List[ExperimentVariantResult]**](ExperimentVariantResult.md) | | [optional]
+**variants** | [**List[ExperimentVariantResult]**](ExperimentVariantResult.md) | |
**confidence** | [**ExperimentVariantResultConfidence**](ExperimentVariantResultConfidence.md) | |
## Example
diff --git a/docs/ExperimentVariantResult.md b/docs/ExperimentVariantResult.md
index f56aa00..14e4e94 100644
--- a/docs/ExperimentVariantResult.md
+++ b/docs/ExperimentVariantResult.md
@@ -8,6 +8,7 @@ Name | Type | Description | Notes
**variant_id** | **int** | The ID of the variant. | [optional]
**variant_name** | **str** | The name of the variant. | [optional]
**variant_weight** | **int** | The weight of the variant. | [optional]
+**is_winner** | **bool** | Calculated flag if the variant is the winner. | [optional]
**total_revenue** | **float** | The total, pre-discount value of all items purchased in a customer session. | [optional]
**sessions_count** | **float** | The number of all closed sessions. | [optional]
**avg_items_per_session** | **float** | The number of items from sessions divided by the number of sessions. | [optional]
diff --git a/docs/GiveawayPoolNotification.md b/docs/GiveawayPoolNotification.md
new file mode 100644
index 0000000..0813260
--- /dev/null
+++ b/docs/GiveawayPoolNotification.md
@@ -0,0 +1,31 @@
+# GiveawayPoolNotification
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**total_result_size** | **int** | |
+**data** | [**List[GiveawayPoolNotificationData]**](GiveawayPoolNotificationData.md) | The array of giveaway pool notifications. |
+**notification_type** | **str** | The type of notification. |
+
+## Example
+
+```python
+from talon_one.models.giveaway_pool_notification import GiveawayPoolNotification
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of GiveawayPoolNotification from a JSON string
+giveaway_pool_notification_instance = GiveawayPoolNotification.from_json(json)
+# print the JSON string representation of the object
+print(GiveawayPoolNotification.to_json())
+
+# convert the object into a dict
+giveaway_pool_notification_dict = giveaway_pool_notification_instance.to_dict()
+# create an instance of GiveawayPoolNotification from a dict
+giveaway_pool_notification_from_dict = GiveawayPoolNotification.from_dict(giveaway_pool_notification_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/GiveawayPoolNotificationData.md b/docs/GiveawayPoolNotificationData.md
new file mode 100644
index 0000000..05c54fe
--- /dev/null
+++ b/docs/GiveawayPoolNotificationData.md
@@ -0,0 +1,38 @@
+# GiveawayPoolNotificationData
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**event** | **str** | The event type of the notification. |
+**pool_id** | **int** | The ID of the giveaway pool. |
+**pool_name** | **str** | The name of the giveaway pool. |
+**pool_description** | **str** | The description of the giveaway pool. |
+**account_id** | **int** | The ID of the account that owns the giveaway pool. |
+**application_id** | **int** | The ID of the Application connected to the giveaway pool. |
+**total_codes** | **int** | The total number of codes in the giveaway pool. |
+**used_codes** | **int** | The number of codes that have been used. |
+**remaining_codes** | **int** | The number of codes remaining in the giveaway pool. |
+**threshold_percent** | **int** | The percentage threshold for the notification. The notification is triggered when the number of codes drops below this threshold. |
+
+## Example
+
+```python
+from talon_one.models.giveaway_pool_notification_data import GiveawayPoolNotificationData
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of GiveawayPoolNotificationData from a JSON string
+giveaway_pool_notification_data_instance = GiveawayPoolNotificationData.from_json(json)
+# print the JSON string representation of the object
+print(GiveawayPoolNotificationData.to_json())
+
+# convert the object into a dict
+giveaway_pool_notification_data_dict = giveaway_pool_notification_data_instance.to_dict()
+# create an instance of GiveawayPoolNotificationData from a dict
+giveaway_pool_notification_data_from_dict = GiveawayPoolNotificationData.from_dict(giveaway_pool_notification_data_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/IntegrationApi.md b/docs/IntegrationApi.md
index 539468e..ebe8ce4 100644
--- a/docs/IntegrationApi.md
+++ b/docs/IntegrationApi.md
@@ -28,7 +28,6 @@ Method | HTTP request | Description
[**get_loyalty_program_profile_transactions**](IntegrationApi.md#get_loyalty_program_profile_transactions) | **GET** /v1/loyalty_programs/{loyaltyProgramId}/profile/{integrationId}/transactions | List customer's loyalty transactions
[**get_reserved_customers**](IntegrationApi.md#get_reserved_customers) | **GET** /v1/coupon_reservations/customerprofiles/{couponValue} | List customers that have this coupon reserved
[**link_loyalty_card_to_profile**](IntegrationApi.md#link_loyalty_card_to_profile) | **POST** /v2/loyalty_programs/{loyaltyProgramId}/cards/{loyaltyCardId}/link_profile | Link customer profile to card
-[**price_history**](IntegrationApi.md#price_history) | **POST** /v1/best_prior_price_history | Get summary of price history
[**reopen_customer_session**](IntegrationApi.md#reopen_customer_session) | **PUT** /v2/customer_sessions/{customerSessionId}/reopen | Reopen customer session
[**return_cart_items**](IntegrationApi.md#return_cart_items) | **POST** /v2/customer_sessions/{customerSessionId}/returns | Return cart items
[**sync_catalog**](IntegrationApi.md#sync_catalog) | **PUT** /v1/catalogs/{catalogId}/sync | Sync cart item catalog
@@ -143,8 +142,6 @@ Returns the best prior price based on historical pricing data for the specified
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -165,18 +162,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -213,7 +198,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -233,22 +218,28 @@ Name | Type | Description | Notes
Create audience
-Create an audience. The audience can be created directly from scratch or can come from third party platforms.
+Create an audience. The audience can be created directly from scratch or can
+come from third party platforms.
+
+> [!note] Audiences can also be created from scratch via the Campaign
+Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences).
-**Note:** Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences).
+To create an audience from an existing audience from a [technology
+partner](https://docs.talon.one/docs/dev/technology-partners/overview):
-To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview):
-1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform.
+1. Set the `integration` property to `mparticle`, `segment` etc., depending
+on a third-party platform.
1. Set `integrationId` to the ID of this audience in a third-party platform.
To create an audience from an existing audience in another platform:
+
1. Do not use the `integration` property.
1. Set `integrationId` to the ID of this audience in the 3rd-party platform.
-To create an audience from scratch:
-1. Only set the `name` property.
+To create an audience from scratch, only set the `name` property.
-Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
+Once you create your first audience, audience-specific rule conditions are
+enabled in the Rule Builder.
### Example
@@ -283,7 +274,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- new_audience = talon_one.NewAudience() # NewAudience | body
+ new_audience = {"name":"VIP Customers","description":"Customers with high lifetime value and frequent purchases","sandbox":false,"createdIn3rdParty":false} # NewAudience | body
try:
# Create audience
@@ -340,25 +331,24 @@ You can also create a reservation via the Campaign Manager using the
reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code)
effect.
-**Note:**
-
-- If the **Reservation mandatory** option was selected when creating the
- specified coupon, the endpoint creates a **hard** reservation, meaning only users who have
- this coupon code reserved can redeem it.
- Otherwise, the endpoint creates a **soft** reservation, meaning the coupon
- is associated with the specified customer profiles (they show up when using
- the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory)
- endpoint), but any user can redeem it.
- This can be useful, for example, to display a _coupon wallet_ for customers
- when they visit your store.
-
-- If the **Coupon visibility** option was selected when creating the
- specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code
- will be returned for all customer profiles in the [List customer
- data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint.
-
-- This endpoint overrides the coupon reservation limit set when
- [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons).
+> [!note] **Note**
+> - If the **Reservation mandatory** option was selected when creating the
+> specified coupon, the endpoint creates a **hard** reservation, meaning only users who have
+> this coupon code reserved can redeem it.
+>
+> Otherwise, the endpoint creates a **soft** reservation, meaning the coupon
+> is associated with the specified customer profiles (they show up when using
+> the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory)
+> endpoint), but any user can redeem it.
+>
+> This can be useful, for example, to display a _coupon wallet_ for customers
+> when they visit your store.
+> - If the **Coupon visibility** option was selected when creating the
+> specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code
+> will be returned for all customer profiles in the [List customer
+> data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) endpoint.
+> - This endpoint overrides the coupon reservation limit set when
+> [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons).
To ensure that coupons cannot be reserved after the reservation limit is
reached, use the [Create coupon code
@@ -402,7 +392,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- coupon_value = 'coupon_value_example' # str | The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`.
+ coupon_value = 'coupon_value_example' # str | The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`.
coupon_reservations = talon_one.CouponReservations() # CouponReservations | body
try:
@@ -421,7 +411,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **coupon_value** | **str**| The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. |
+ **coupon_value** | **str**| The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. |
**coupon_reservations** | [**CouponReservations**](CouponReservations.md)| body |
### Return type
@@ -453,9 +443,13 @@ Name | Type | Description | Notes
Create referral code for an advocate
-Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile.
+Creates a referral code for an advocate. The code will be valid for the
+referral campaign for which is created, indicated in the `campaignId`
+parameter, and will be associated with the profile specified in the
+`advocateProfileIntegrationId` parameter as the advocate's profile.
-**Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+> [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits)
+> set are ignored when you use this endpoint.
### Example
@@ -538,9 +532,14 @@ Name | Type | Description | Notes
Create referral codes for multiple advocates
-Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile.
+Creates unique referral codes for multiple advocates. The code will be valid
+for the referral campaign for which it is created, indicated in the
+`campaignId` parameter, and one referral code will be associated with one
+advocate using the profile specified in the `advocateProfileIntegrationId`
+parameter as the advocate's profile.
-**Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+> [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits)
+> set are ignored when you use this endpoint.
### Example
@@ -707,9 +706,11 @@ Delete audience
Delete an audience created by a third-party integration.
-**Warning:** This endpoint also removes any associations recorded between a customer profile and this audience.
+> [!warning] This endpoint also removes any associations recorded between a
+customer profile and this audience.
-**Note:** Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
+> [!note] Audiences can also be deleted via the Campaign Manager. See the
+[docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
### Example
@@ -824,7 +825,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- coupon_value = 'coupon_value_example' # str | The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`.
+ coupon_value = 'coupon_value_example' # str | The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`.
coupon_reservations = talon_one.CouponReservations() # CouponReservations | body
try:
@@ -841,7 +842,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **coupon_value** | **str**| The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. |
+ **coupon_value** | **str**| The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. |
**coupon_reservations** | [**CouponReservations**](CouponReservations.md)| body |
### Return type
@@ -873,14 +874,17 @@ void (empty response body)
Delete customer's personal data
-Delete all attributes on the customer profile and on entities that reference this customer profile.
+Delete all attributes on the customer profile and on entities that reference
+this customer profile.
-**Important:**
-- Customer data is deleted from all Applications in the [environment](https://docs.talon.one/docs/product/applications/overview#application-environments)
- that the API key belongs to. For example, if you use this endpoint with an API key that belongs to a sandbox Application,
- customer data will be deleted from all sandbox Applications. This is because customer data is shared
- between Applications from the same environment.
-- To preserve performance, we recommend avoiding deleting customer data during peak-traffic hours.
+> [!warning] **Warning**
+> - Customer data is deleted from all Applications in the
+> [environment](https://docs.talon.one/docs/product/applications/overview#application-environments)
+> that the API key belongs to. For example, if you use this endpoint with an API key that belongs
+> to a sandbox Application, customer data will be deleted from all sandbox Applications.
+> This is because customer data is shared between Applications from the same environment.
+> - To preserve performance, we recommend avoiding deleting customer data
+> during peak-traffic hours.
### Example
@@ -913,7 +917,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
try:
# Delete customer's personal data
@@ -929,7 +933,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
### Return type
@@ -961,9 +965,9 @@ Delete customer's transactions from loyalty ledgers
Delete a customer's transactions in all loyalty ledgers or a specified ledger.
-**Note:** To retrieve loyalty transaction logs for a specific customer in a given
-loyalty program, use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions)
-endpoint.
+> [!note] To retrieve loyalty transaction logs for a specific customer in a given loyalty program,
+> use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions)
+> endpoint.
### Example
@@ -998,7 +1002,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
loyalty_program_id = 56 # int | Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
- integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
delete_loyalty_transactions_request = talon_one.DeleteLoyaltyTransactionsRequest() # DeleteLoyaltyTransactionsRequest |
try:
@@ -1016,7 +1020,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
- **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
**delete_loyalty_transactions_request** | [**DeleteLoyaltyTransactionsRequest**](DeleteLoyaltyTransactionsRequest.md)| |
### Return type
@@ -1054,16 +1058,13 @@ program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-ba
To link the card to one or more customer profiles, use the
`customerProfileIds` parameter in the request body.
-**Note:**
-
-- The number of customer profiles linked to the loyalty card cannot exceed
-the loyalty program's `usersPerCardLimit`. To find the program's limit, use
-the [Get loyalty
-program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram)
-endpoint.
-
-- If the loyalty program has a defined code format, it will be used for the
-loyalty card identifier.
+> [!note] **Note**
+> - The number of customer profiles linked to the loyalty card cannot exceed
+> the loyalty program's `usersPerCardLimit`. To find the program's limit, use
+> the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram)
+> endpoint.
+> - If the loyalty program has a defined code format, it will be used for the
+> loyalty card identifier.
### Example
@@ -1375,7 +1376,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ integration_id = 'integration_id_example' # str | The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
profile = True # bool | Set to `true` to include customer profile information in the response. (optional)
referrals = True # bool | Set to `true` to include referral information in the response. (optional)
coupons = True # bool | Set to `true` to include coupon information in the response. (optional)
@@ -1399,7 +1400,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **integration_id** | **str**| The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
**profile** | **bool**| Set to `true` to include customer profile information in the response. | [optional]
**referrals** | **bool**| Set to `true` to include referral information in the response. | [optional]
**coupons** | **bool**| Set to `true` to include coupon information in the response. | [optional]
@@ -1474,7 +1475,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint.
+ customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint.
try:
# Get customer session
@@ -1492,7 +1493,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. |
+ **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. |
### Return type
@@ -1522,12 +1523,18 @@ Name | Type | Description | Notes
Get customer's loyalty balances
-Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program.
-You can filter balances by date and subledger ID, and include tier-related information in the response.
+Retrieve loyalty ledger balances for the given Integration ID in the
+specified loyalty program.
-**Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID.
+You can filter balances by date and subledger ID, and include tier-related
+information in the response.
-Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance.
+> [!note] If no filtering options are applied, you retrieve all loyalty
+> balances on the current date for the given integration ID.
+
+Loyalty balances are calculated when Talon.One receives your request using
+the points stored in our database, so retrieving a large number of balances
+at once can impact performance.
For more information, see:
- [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards)
@@ -1567,7 +1574,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.IntegrationApi(api_client)
loyalty_program_id = 56 # int | Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger by which we filter the data. (optional)
include_tiers = False # bool | Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. (optional) (default to False)
include_projected_tier = False # bool | Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. (optional) (default to False)
@@ -1590,7 +1597,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**integration_id** | **str**| The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**subledger_id** | **str**| The ID of the subledger by which we filter the data. | [optional]
**include_tiers** | **bool**| Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. | [optional] [default to False]
**include_projected_tier** | **bool**| Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. | [optional] [default to False]
@@ -1661,7 +1668,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.IntegrationApi(api_client)
loyalty_program_id = 56 # int | Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
loyalty_card_id = 'loyalty_card_id_example' # str | Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
subledger_id = ['subledger_id_example'] # List[str] | Filter results by one or more subledger IDs. Must be exact match. (optional)
try:
@@ -1682,7 +1689,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**loyalty_card_id** | **str**| Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**subledger_id** | [**List[str]**](str.md)| Filter results by one or more subledger IDs. Must be exact match. | [optional]
### Return type
@@ -1857,8 +1864,8 @@ with talon_one.ApiClient(configuration) as api_client:
loyalty_card_id = 'loyalty_card_id_example' # str | Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`.
subledger_id = ['subledger_id_example'] # List[str] | Filter results by one or more subledger IDs. Must be exact match. (optional)
loyalty_transaction_type = 'loyalty_transaction_type_example' # str | Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. (optional)
- start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
page_size = 50 # int | The number of items in the response. (optional) (default to 50)
@@ -1885,8 +1892,8 @@ Name | Type | Description | Notes
**loyalty_card_id** | **str**| Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. |
**subledger_id** | [**List[str]**](str.md)| Filter results by one or more subledger IDs. Must be exact match. | [optional]
**loyalty_transaction_type** | **str**| Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. | [optional]
- **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
- **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
**transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
**page_size** | **int**| The number of items in the response. | [optional] [default to 50]
@@ -2026,12 +2033,15 @@ Name | Type | Description | Notes
List customer's loyalty transactions
-Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program.
+Retrieve paginated results of loyalty transaction logs for the given
+Integration ID in the specified loyalty program.
-You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned.
+You can filter transactions by date. If no filters are applied, the last 50
+loyalty transactions for the given integration ID are returned.
-**Note:** To retrieve all loyalty program transaction logs in a given loyalty program,
-use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+> [!note] To retrieve all loyalty program transaction logs in a given
+> loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions)
+> endpoint.
### Example
@@ -2067,12 +2077,12 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.IntegrationApi(api_client)
loyalty_program_id = 56 # int | Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
- customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
- transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
+ customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
+ transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger by which we filter the data. (optional)
loyalty_transaction_type = 'loyalty_transaction_type_example' # str | Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. (optional)
- start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
page_size = 50 # int | The number of items in the response. (optional) (default to 50)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
awaits_activation = True # bool | If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. (optional)
@@ -2095,12 +2105,12 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**integration_id** | **str**| The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. |
- **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
- **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
+ **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
+ **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
**subledger_id** | **str**| The ID of the subledger by which we filter the data. | [optional]
**loyalty_transaction_type** | **str**| Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. | [optional]
- **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
- **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**page_size** | **int**| The number of items in the response. | [optional] [default to 50]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
**awaits_activation** | **bool**| If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. | [optional]
@@ -2217,14 +2227,22 @@ Name | Type | Description | Notes
Link customer profile to card
-[Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect
-and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types).
-They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them.
+[Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview)
+allow customers to collect and spend loyalty points within a [card-based loyalty
+program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types).
+
+They are useful to gamify loyalty programs and can be used with or without
+customer profiles linked to them.
-Link a customer profile to a given loyalty card for the card to be set as **Registered**.
-This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card).
+Link a customer profile to a given loyalty card for the card to be set as
+**Registered**.
-**Note:** You can link as many customer profiles to a given loyalty card as the [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) allows.
+This affects how it can be used. See the
+[docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card).
+
+> [!note] You can link as many customer profiles to a given loyalty card as the
+> [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs)
+> allows.
### Example
@@ -2307,122 +2325,31 @@ Name | Type | Description | Notes
[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
-# **price_history**
-> PriceHistoryResponse price_history(price_history_request)
-
-Get summary of price history
-
-Fetch the historical price data for a given SKU within a defined timeframe.
-
-
-### Example
-
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
-* Api Key Authentication (api_key_v1):
-
-```python
-import talon_one
-from talon_one.models.price_history_request import PriceHistoryRequest
-from talon_one.models.price_history_response import PriceHistoryResponse
-from talon_one.rest import ApiException
-from pprint import pprint
-
-# Defining the host is optional and defaults to https://yourbaseurl.talon.one
-# See configuration.py for a list of all supported configuration parameters.
-configuration = talon_one.Configuration(
- host = "https://yourbaseurl.talon.one"
-)
-
-# The client must configure the authentication and authorization parameters
-# in accordance with the API server security policy.
-# Examples for each auth method are provided below, use the example that
-# satisfies your auth use case.
-
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
-# Configure API key authorization: api_key_v1
-configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['api_key_v1'] = 'Bearer'
-
-# Enter a context with an instance of the API client
-with talon_one.ApiClient(configuration) as api_client:
- # Create an instance of the API class
- api_instance = talon_one.IntegrationApi(api_client)
- price_history_request = talon_one.PriceHistoryRequest() # PriceHistoryRequest | body
-
- try:
- # Get summary of price history
- api_response = api_instance.price_history(price_history_request)
- print("The response of IntegrationApi->price_history:\n")
- pprint(api_response)
- except Exception as e:
- print("Exception when calling IntegrationApi->price_history: %s\n" % e)
-```
-
-
-
-### Parameters
-
-
-Name | Type | Description | Notes
-------------- | ------------- | ------------- | -------------
- **price_history_request** | [**PriceHistoryRequest**](PriceHistoryRequest.md)| body |
-
-### Return type
-
-[**PriceHistoryResponse**](PriceHistoryResponse.md)
-
-### Authorization
-
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
-
-### HTTP request headers
-
- - **Content-Type**: application/json
- - **Accept**: application/json
-
-### HTTP response details
-
-| Status code | Description | Response headers |
-|-------------|-------------|------------------|
-**200** | Ok | - |
-
-[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
-
# **reopen_customer_session**
> ReopenSessionResponse reopen_customer_session(customer_session_id)
Reopen customer session
-Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions).
-For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint.
+Reopen a closed [customer
+session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions).
+
+For example, if a session has been completed but still needs to be edited,
+you can reopen it with this endpoint.
+
A reopen session is treated like a standard open session.
When reopening a session:
+
- The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager.
- The session state is updated to `open`.
- Any modified budgets and triggered effects are rolled back when the session closes.
- Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy)
in your loyalty programs, points are rolled back in the following ways:
- Pending points are rolled back automatically.
- - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed
+ - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed
are rolled back.
- If **Negative balance** is enabled, the rollback can create a negative points balance.
-
Effects and budgets unimpacted by a session reopening
@@ -2437,12 +2364,15 @@ When reopening a session:
Update cart item attribute value
-
-
-To see an example of a rollback, see the Cancelling a session with campaign budgets tutorial.
-**Note:** If your order workflow requires you to create a new session instead of reopening a session, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint to cancel a closed session and create a new one.
+To see an example of a rollback, see the
+[Cancelling a session with campaign budgets](https://docs.talon.one/docs/dev/tutorials/rolling-back-effects) tutorial.
+
+> [!note] If your order workflow requires you to create a new session
+> instead of reopening a session, use the
+> [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2)
+> endpoint to cancel a closed session and create a new one.
### Example
@@ -2476,7 +2406,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint.
+ customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint.
try:
# Reopen customer session
@@ -2494,7 +2424,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. |
+ **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. |
### Return type
@@ -2526,11 +2456,18 @@ Return cart items
Create a new return request for the specified cart items.
-This endpoint automatically changes the session state from `closed` to `partially_returned`.
+This endpoint automatically changes the session state from `closed` to
+`partially_returned`.
+
+> [!note] This will roll back any effects associated with these cart items.
+> For more information, see [our documentation on session
+> states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states)
+> and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session).
-**Note:** This will roll back any effects associated with these cart items. For more information, see
-[our documentation on session states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states)
-and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session).
+> [!note] To make request processing idempotent for this endpoint, include the `Idempotency-Key` header with an idempotency key in requests. Also:
+> - Requests with the `Idempotency-Key` header are logged in the Talon.One access logs.
+> - Responses for idempotent requests are stored in the database and expire 24 hours after the request is sent.
+> - Idempotency keys are typically UUID keys and should not exceed 255 characters in length.
### Example
@@ -2565,7 +2502,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint.
+ customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint.
return_integration_request = talon_one.ReturnIntegrationRequest() # ReturnIntegrationRequest | body
dry = True # bool | Indicates whether to persist the changes. Changes are ignored when `dry=true`. (optional)
@@ -2585,7 +2522,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. |
+ **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. |
**return_integration_request** | [**ReturnIntegrationRequest**](ReturnIntegrationRequest.md)| body |
**dry** | **bool**| Indicates whether to persist the changes. Changes are ignored when `dry=true`. | [optional]
@@ -2626,24 +2563,28 @@ Perform the following actions for a given cart item catalog:
- Remove an item from the catalog.
- Remove multiple items from the catalog.
-You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`.
+You can either add, update, or delete up to 1000 cart items in a single
+request. Each item synced to a catalog must have a unique `SKU`.
-**Important**: You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code.
+> [!important] You can perform only one type of action in a single sync
+request. Syncing items with duplicate `SKU` values in a single request
+returns an error message with a `400` status code.
-For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs).
+For more information, read [managing cart item
+catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs).
### Filtering cart items
Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes)
-to filter items and select the ones you want to edit or delete when editing or deleting more than one item
-at a time.
+to filter items and select the ones you want to edit or delete when editing
+or deleting more than one item at a time.
The `filters` array contains an object with the following properties:
- `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes)
connected to the catalog. It is applied to all items in the catalog.
-- `op`: The filtering operator indicating the relationship between the value of each
- cart item in the catalog and the value of the `value` property for the attribute selected
+- `op`: The filtering operator indicating the relationship between the value
+ of each cart item in the catalog and the value of the `value` property for the attribute selected
in `attr`.
The value of `op` can be one of the following:
@@ -2656,12 +2597,12 @@ The `filters` array contains an object with the following properties:
- `IN`: One of the comma-separated values that `value` is set to.
**Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only.
-
- `value`: The value of the attribute selected in `attr`.
### Payload examples
-Synchronization actions are sent as `PUT` requests. See the structure for each action:
+Synchronization actions are sent as `PUT` requests. See the structure for
+each action:
Adding an item to the catalog
@@ -2951,26 +2892,28 @@ Track event
Triggers a custom event.
To use this endpoint:
-1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager.
-1. Update or create a rule to check for this event.
-1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager.
-Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create
-a custom event when you can use a built-in event.
-
-For example, use this endpoint to trigger an event when a customer shares a link to a product.
-See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing).
+1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event)
+in the Campaign Manager.
+1. Update or create a rule to check for this event.
+1. Trigger the event with this endpoint. After you have successfully sent an
+event to Talon.One, you can list the received events in the **Events** view
+in the Campaign Manager.
-
+Talon.One also offers a set of [built-in
+events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure
+you do not create a custom event when you can use a built-in event.
-
Important
+For example, use this endpoint to trigger an event when a customer shares a
+link to a product.
- 1. `profileId` is required even though the schema does not specify it.
- 1. If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered.
- 1. We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
- 1. [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
+See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing).
-
+> [!note] **Note**
+> - `profileId` is required even though the schema does not specify it.
+> - If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered.
+> - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
+> - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
### Example
@@ -3005,7 +2948,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- integration_event_v2_request = talon_one.IntegrationEventV2Request() # IntegrationEventV2Request | body
+ integration_event_v2_request = {profileId=customer-123, type=newsletter_signup, attributes={SubscriptionType=weekly}, responseContent=[customerProfile, triggeredCampaigns]} # IntegrationEventV2Request | body
silent = 'yes' # str | Possible values: `yes` or `no`. - `yes`: Increases the performance of the API call by returning a 204 response. - `no`: Returns a 200 response that contains the updated customer profiles. (optional) (default to 'yes')
dry = True # bool | Indicates whether to persist the changes. Changes are ignored when `dry=true`. (optional)
force_complete_evaluation = False # bool | Forces evaluation for all matching campaigns regardless of the [campaign evaluation mode](https://docs.talon.one/docs/product/applications/managing-campaign-evaluation#setting-campaign-evaluation-mode). Requires `dry=true`. (optional) (default to False)
@@ -3063,7 +3006,7 @@ Unlink customer profile from a loyalty card
Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card.
To get the `integrationId` of a customer profile, you can use the
-[Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2)
+[Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2)
endpoint.
@@ -3324,7 +3267,9 @@ Add customer profiles to or remove them from an audience.
The endpoint supports 1000 audience actions (`add` or `remove`) per request.
-**Note:** You can also do this using the [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) effect.
+> [!note] You can also do this using the
+> [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience)
+> effect.
### Example
@@ -3405,21 +3350,21 @@ void (empty response body)
Update customer profile
-Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder.
+Update or create a [Customer
+Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles).
+This endpoint triggers the Rule Builder.
You can use this endpoint to:
- Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first.
- Modify the audience the customer profile is a member of.
-**Note:** [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`.
-
-
Performance tips
- - Updating a customer profile returns a response with the requested integration state.
- - You can use the `responseContent` property to save yourself extra API calls. For example, you can get
- the customer profile details directly without extra requests.
- - We recommend sending requests sequentially.
- See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
-
+> [!note] **Note**
+> - Updating a customer profile returns a response with the requested integration state.
+> - You can use the `responseContent` property to save yourself extra API calls. For example, you can get
+> the customer profile details directly without extra requests.
+> - We recommend sending requests sequentially.
+> See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
+> - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`.
### Example
@@ -3455,7 +3400,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
- customer_profile_integration_request_v2 = talon_one.CustomerProfileIntegrationRequestV2() # CustomerProfileIntegrationRequestV2 | body
+ customer_profile_integration_request_v2 = {"attributes":{"Name":"Chris Taylor","Email":"chris.taylor@example.com","SignupDate":"2026-01-21T15:04:05+07:00","PaymentMethod":"Bank transfer"}} # CustomerProfileIntegrationRequestV2 | body
run_rule_engine = False # bool | Indicates whether to run the Rule Engine. If `true`, the response includes: - The effects generated by the triggered campaigns are returned in the `effects` property. - The created coupons and referral objects. If `false`: - The rules are not executed and the `effects` property is always empty. - The response time improves. - You cannot use `responseContent` in the body. (optional) (default to False)
dry = True # bool | (Only works when `runRuleEngine=true`) Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`, you can use the `evaluableCampaignIds` body property to select specific campaigns to run. (optional)
@@ -3509,16 +3454,20 @@ Name | Type | Description | Notes
Update multiple customer profiles
-Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request.
+Update (or create) up to 1000 [customer
+profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles)
+in 1 request.
The `integrationId` must be any identifier that remains stable for
the customer. Do not use an ID that the customer can update
themselves. For example, you can use a database ID.
-A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions).
+A customer profile [can be linked to one or more
+sessions](https://docs.talon.one/integration-api#tag/Customer-sessions).
-**Note:** This endpoint does not trigger the Rule Engine. To trigger the Rule Engine for customer profile updates,
-use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
+> [!note] This endpoint does not trigger the Rule Engine.
+> To trigger the Rule Engine for customer profile updates,
+> use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
### Example
@@ -3603,38 +3552,49 @@ Name | Type | Description | Notes
Update customer session
-Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions).
-The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart.
-For example, use this endpoint to share the contents of a customer's cart with Talon.One.
+Update or create a [customer
+session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions).
-**Note:**
-- The currency for the session and the cart items in it is the currency set for the Application linked to this session. - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation.
+The endpoint responds with the potential promotion rule
+[effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that
+match the current cart.
+
+For example, use this endpoint to share the contents of a customer's cart
+with Talon.One.
+
+> [!note] **Note**
+> - The currency for the session and the cart items in it is the currency set for the Application linked to this session.
+> - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation.
### Session management
-To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions)
-and their states and refer to the `state` parameter documentation the request body schema docs below.
+To use this endpoint, start by learning about [customer
+sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions)
+and their states and refer to the `state` parameter documentation the
+request body schema docs below.
### Sessions and customer profiles
-- To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`.
-- While you can create an anonymous session with `profileId=""`, we recommend you use a guest ID instead.
-- A profile can be linked to simultaneous sessions in different Applications. Either:
- - Use unique session integration IDs or,
- - Use the same session integration ID across all of the Applications.
+- To link a session to a customer profile, set the `profileId` parameter in
+the request body to a customer profile's `integrationId`.
-**Note:** If the specified profile does not exist, an empty profile is **created automatically**.
- You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2).
+- While you can create an anonymous session with `profileId=""`, we
+recommend you use a guest ID instead.
-
-
Performance tips
+- A profile can be linked to simultaneous sessions in different
+Applications. Either:
+ - Use unique session integration IDs or,
+ - Use the same session integration ID across all of the Applications.
- - Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls.
- For example, you can get the customer profile details directly without extra requests.
- - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
-
+> [!note] **Note**
+> - If the specified profile does not exist, an empty profile is **created automatically**.
+> You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2).
+> - Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls.
+> For example, you can get the customer profile details directly without extra requests.
+> - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
For more information, see:
+
- The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview).
- The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
@@ -3671,10 +3631,10 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.IntegrationApi(api_client)
- customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint.
- integration_request = talon_one.IntegrationRequest() # IntegrationRequest | body
+ customer_session_id = 'customer_session_id_example' # str | The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint.
+ integration_request = {"customerSession":{"profileId":"382370BKDB946","cartItems":[{"name":"Wireless Bluetooth Headphones","sku":"AUDIO-WH350","quantity":1,"price":79.99,"weight":310},{"name":"USB-C Charging Cable","sku":"CABLE-USBC-2M","quantity":2,"price":15.99,"weight":40}]},"responseContent":["customerSession","customerProfile"]} # IntegrationRequest | body
dry = True # bool | Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests). (optional)
- now = '2013-10-20T19:20:30+01:00' # datetime | A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`. (optional)
+ now = '2013-10-20T19:20:30+01:00' # datetime | A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`. (optional)
try:
# Update customer session
@@ -3692,10 +3652,10 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. |
+ **customer_session_id** | **str**| The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. |
**integration_request** | [**IntegrationRequest**](IntegrationRequest.md)| body |
**dry** | **bool**| Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests). | [optional]
- **now** | **datetime**| A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`. | [optional]
+ **now** | **datetime**| A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`. | [optional]
### Return type
diff --git a/docs/ManagementApi.md b/docs/ManagementApi.md
index 94c9e42..ec97836 100644
--- a/docs/ManagementApi.md
+++ b/docs/ManagementApi.md
@@ -150,6 +150,7 @@ Method | HTTP request | Description
[**list_experiments**](ManagementApi.md#list_experiments) | **GET** /v1/applications/{applicationId}/experiments | List experiments
[**list_stores**](ManagementApi.md#list_stores) | **GET** /v1/applications/{applicationId}/stores | List stores
[**okta_event_handler_challenge**](ManagementApi.md#okta_event_handler_challenge) | **GET** /v1/provisioning/okta | Validate Okta API ownership
+[**price_history**](ManagementApi.md#price_history) | **POST** /v1/applications/{applicationId}/price_history | Get summary of price history
[**remove_loyalty_points**](ManagementApi.md#remove_loyalty_points) | **PUT** /v1/loyalty_programs/{loyaltyProgramId}/profile/{integrationId}/deduct_points | Deduct points from customer profile
[**reset_password**](ManagementApi.md#reset_password) | **POST** /v1/reset_password | Reset password
[**scim_create_group**](ManagementApi.md#scim_create_group) | **POST** /v1/provisioning/scim/Groups | Create SCIM group
@@ -196,8 +197,6 @@ Enable a [disabled user](https://docs.talon.one/docs/product/account/account-set
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -217,18 +216,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -263,7 +250,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -288,8 +275,6 @@ Add points to the given loyalty card in the specified card-based loyalty program
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -309,18 +294,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -359,7 +332,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -385,13 +358,11 @@ Add points to customer profile
Add points in the specified loyalty program for the given customer.
To get the `integrationId` of the profile from a `sessionId`, use the
-[Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+[Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -411,18 +382,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -461,7 +420,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -488,8 +447,6 @@ Copy the campaign into all specified Applications.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -510,18 +467,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -562,7 +507,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -586,8 +531,6 @@ Create an account-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -608,18 +551,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -656,7 +587,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -683,8 +614,6 @@ Create a new achievement in a specific campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -705,18 +634,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -757,7 +674,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -787,8 +704,6 @@ These additional costs are shared across all applications in your account, and a
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -809,18 +724,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -857,7 +760,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -893,8 +796,6 @@ These attributes are shared across all Applications in your account and are neve
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -915,18 +816,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -963,7 +852,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -983,20 +872,20 @@ Name | Type | Description | Notes
Create loyalty cards
-Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types).
+Create a batch of loyalty cards in a specified [card-based loyalty
+program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types).
Customers can use loyalty cards to collect and spend loyalty points.
-**Important:**
-
-- The specified card-based loyalty program must have a defined card code format that is used to generate the loyalty card codes.
-- Trying to create more than 20,000 loyalty cards in a single request returns an error message with a `400` status code.
+> [!important] **Note**
+> - The specified card-based loyalty program must have a defined card code
+> format that is used to generate the loyalty card codes.
+> - Trying to create more than 20,000 loyalty cards in a single request
+> returns an error message with a `400` status code.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1017,18 +906,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1067,7 +944,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1099,8 +976,6 @@ the corresponding collections for the new campaign are created automatically.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1121,18 +996,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1171,7 +1034,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1195,8 +1058,6 @@ Create a new store budget for a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1216,18 +1077,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1266,7 +1115,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1292,8 +1141,6 @@ Create a campaign-level collection in a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1314,18 +1161,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1366,7 +1201,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1390,8 +1225,6 @@ Create coupons according to some pattern. Up to 20.000 coupons can be created wi
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1412,18 +1245,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1466,7 +1287,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1494,8 +1315,6 @@ If you want to create less than 20,001 coupons, you can use the [Create coupons]
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1516,18 +1335,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1568,7 +1375,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1593,8 +1400,6 @@ This endpoint handles creating a job to delete coupons asynchronously.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1615,18 +1420,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1667,7 +1460,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1691,8 +1484,6 @@ Create coupons according to some pattern for up to 1000 recipients.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1713,18 +1504,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1767,7 +1546,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1790,13 +1569,11 @@ Resend invitation email
Resend an email invitation to an existing user.
-**Note:** The invitation token is valid for 24 hours after the email has been sent.
+> [!note] The invitation token is valid for 24 hours after the email has been sent.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1816,18 +1593,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1864,7 +1629,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1884,15 +1649,17 @@ Name | Type | Description | Notes
Invite user
-Create a new user in the account and send an invitation to their email address.
+Create a new user in the account and send an invitation to their email
+address.
-**Note**: The invitation token is valid for 24 hours after the email has been sent. You can resend an invitation to a user with the [Resend invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) endpoint.
+> [!note] The invitation token is valid for 24 hours after the email has
+> been sent. You can resend an invitation to a user with the [Resend
+> invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail)
+> endpoint.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -1913,18 +1680,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -1961,7 +1716,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -1981,15 +1736,14 @@ Name | Type | Description | Notes
Request a password reset
-Send an email with a password recovery link to the email address of an existing account.
+Send an email with a password recovery link to the email address of an
+existing account.
-**Note:** The password recovery link expires 30 minutes after this endpoint is triggered.
+> [!note] The password recovery link expires 30 minutes after this endpoint is triggered.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2009,18 +1763,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2057,7 +1799,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2078,24 +1820,23 @@ Name | Type | Description | Notes
Create session
Create a session to use the Management API endpoints.
-Use the value of the `token` property provided in the response as bearer token in other API calls.
-A token is valid for 3 months. In accordance with best pratices, use your generated token
-for all your API requests. Do **not** regenerate a token for each request.
+Use the value of the `token` property provided in the response as bearer
+token in other API calls.
+
+A token is valid for 3 months. In accordance with best pratices, use your
+generated token for all your API requests. Do **not** regenerate a token for each request.
-This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup.
+This endpoint has a rate limit of 3 to 6 requests per second per account,
+depending on your setup.
-
-
Granular API key
- Instead of using a session, you can also use the
Management API key feature
- in the Campaign Manager to decide which endpoints can be used with a given key.
-
+> [!note]
+> Instead of using a session, you can also use the Management API key feature
+> in the Campaign Manager to decide which endpoints can be used with a given key.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2116,18 +1857,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2164,7 +1893,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2188,8 +1917,6 @@ Create a new store in a specific Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2210,18 +1937,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2260,7 +1975,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2287,8 +2002,6 @@ Disable user by email address
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2308,18 +2021,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2354,7 +2055,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2379,8 +2080,6 @@ Deduct points from the given loyalty card in the specified card-based loyalty pr
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2400,18 +2099,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2450,7 +2137,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2477,8 +2164,6 @@ Delete a given account-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2497,18 +2182,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2519,7 +2192,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
try:
# Delete account-level collection
@@ -2535,7 +2208,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
### Return type
@@ -2543,7 +2216,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2568,8 +2241,6 @@ Delete the specified achievement.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2588,18 +2259,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2638,7 +2297,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2664,8 +2323,6 @@ Delete the given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2684,18 +2341,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2732,7 +2377,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2756,8 +2401,6 @@ Delete the store budgets for a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2776,18 +2419,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2828,7 +2459,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2853,8 +2484,6 @@ Delete a given campaign-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2873,18 +2502,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -2897,7 +2514,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.
try:
# Delete campaign-level collection
@@ -2915,7 +2532,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. |
### Return type
@@ -2923,7 +2540,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -2948,8 +2565,6 @@ Delete the specified coupon.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -2968,18 +2583,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3018,7 +2621,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3042,8 +2645,6 @@ Deletes all the coupons matching the specified criteria.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3062,18 +2663,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3136,7 +2725,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3160,8 +2749,6 @@ Delete the given loyalty card.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3180,18 +2767,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3228,7 +2803,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3254,8 +2829,6 @@ Delete the specified referral.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3274,18 +2847,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3324,7 +2885,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3348,8 +2909,6 @@ Delete the specified store.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3368,18 +2927,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3416,7 +2963,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3441,8 +2988,6 @@ Delete a specific user.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3461,18 +3006,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3507,7 +3040,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3532,8 +3065,6 @@ Delete user by email address
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3553,18 +3084,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3599,7 +3118,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3623,8 +3142,6 @@ Destroys the session.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3643,18 +3160,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3685,7 +3190,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3709,8 +3214,6 @@ Disconnect the stores linked to a specific campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3729,18 +3232,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3777,7 +3268,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3802,13 +3293,12 @@ Export account-level collection's items
Download a CSV file containing items from a given account-level collection.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3827,18 +3317,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3849,7 +3327,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
try:
# Export account-level collection's items
@@ -3867,7 +3345,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
### Return type
@@ -3875,7 +3353,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -3912,8 +3390,6 @@ The CSV file contains the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -3932,18 +3408,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -3984,7 +3448,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4007,12 +3471,16 @@ Name | Type | Description | Notes
Export Application analytics aggregated by campaign
-Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application.
+Download a CSV file containing analytics data aggregated by campaign for the
+campaigns of an Application.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
-- `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data).
+
+- `campaign_id`: The ID of the campaign. This column also contains labels
+ for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data).
- `start_date`: The start of the aggregation time frame in UTC.
- `end_date`: The end of the aggregation time frame in UTC.
- `revenue`: The total, pre-discount value of all items purchased in a customer session.
@@ -4025,8 +3493,6 @@ The CSV file contains the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4045,18 +3511,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4068,8 +3522,8 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
campaign_ids = ['campaign_ids_example'] # List[str] | Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned. (optional)
try:
@@ -4089,8 +3543,8 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**campaign_ids** | [**List[str]**](str.md)| Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned. | [optional]
### Return type
@@ -4099,7 +3553,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4119,18 +3573,19 @@ Name | Type | Description | Notes
Export audience members
-Download a CSV file containing the integration IDs of the members of an audience.
+Download a CSV file containing the integration IDs of the members of an
+audience.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The file contains the following column:
+
- `profileintegrationid`: The integration ID of the customer profile.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4149,18 +3604,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4197,7 +3640,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4222,7 +3665,8 @@ Export campaign store budgets
Download a CSV file containing the store budgets for a given campaign.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
@@ -4232,8 +3676,6 @@ The CSV file contains the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4252,18 +3694,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4306,7 +3736,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4331,7 +3761,8 @@ Export stores
Download a CSV file containing the stores linked to a specific campaign.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following column:
@@ -4340,8 +3771,6 @@ The CSV file contains the following column:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4360,18 +3789,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4410,7 +3827,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4435,13 +3852,12 @@ Export campaign-level collection's items
Download a CSV file containing items from a given campaign-level collection.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4460,18 +3876,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4484,7 +3888,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.
try:
# Export campaign-level collection's items
@@ -4504,7 +3908,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. |
### Return type
@@ -4512,7 +3916,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4536,7 +3940,8 @@ Export coupons
Download a CSV file containing the coupons that match the given properties.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file can contain the following columns:
@@ -4558,7 +3963,7 @@ The CSV file can contain the following columns:
- `limits`: The limits set on this coupon.
- `limitval`: The maximum number of redemptions of this code.
- `recipientintegrationid`: The integration ID of the recipient of the coupon.
- Only the customer with this integration ID can redeem this code. Available only for personal codes.
+ Only the customer with this integration ID can redeem this code. Available only for personal codes.
- `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect).
- `reservation`: Whether the coupon can be reserved for multiple customers.
- `reservation_counter`: How many times this coupon has been reserved.
@@ -4569,8 +3974,6 @@ The CSV file can contain the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4589,18 +3992,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4665,7 +4056,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4687,9 +4078,11 @@ Export customer sessions
Download a CSV file containing the customer sessions that match the request.
-**Important:** Archived sessions cannot be exported. See the [retention policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention).
+> [!important] Archived sessions cannot be exported. See the [retention
+> policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention).
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
- `id`: The internal ID of the session.
- `firstsession`: Whether this is a first session.
@@ -4698,7 +4091,8 @@ Download a CSV file containing the customer sessions that match the request.
- `profileid`: The internal ID of the customer profile.
- `profileintegrationid`: The integration ID of the customer profile.
- `created`: The timestamp when the session was created.
-- `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session.
+- `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states)
+ of the session.
- `cartitems`: The cart items in the session.
- `discounts`: The discounts in the session.
- `total`: The total value of cart items and additional costs in the session, before any discounts are applied.
@@ -4707,7 +4101,8 @@ Download a CSV file containing the customer sessions that match the request.
- `cancelledat`: Timestamp when the session was cancelled.
- `referral`: The referral code in the session.
- `identifiers`: The identifiers in the session.
-- `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session.
+- `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs)
+ in the session.
- `updated`: Timestamp of the last session update.
- `store_integration_id`: The integration ID of the store.
- `coupons`: Coupon codes in the session.
@@ -4715,8 +4110,6 @@ Download a CSV file containing the customer sessions that match the request.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4735,18 +4128,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4793,7 +4174,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4832,8 +4213,6 @@ You can filter the results by providing the following optional input parameters:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4852,18 +4231,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -4904,7 +4271,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -4924,9 +4291,11 @@ Name | Type | Description | Notes
Export triggered effects
-Download a CSV file containing the triggered effects that match the given attributes.
+Download a CSV file containing the triggered effects that match the given
+attributes.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The generated file can contain the following columns:
@@ -4950,8 +4319,6 @@ The generated file can contain the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -4970,18 +4337,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5026,7 +4381,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5046,18 +4401,18 @@ Name | Type | Description | Notes
Export customer loyalty balance to CSV
-⚠️ Deprecation notice: Support for requests to this endpoint will end soon.
-To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint.
+To export customer loyalty balances to CSV, use the [Export customer loyalty
+balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint.
-Download a CSV file containing the balance of each customer in the loyalty program.
+Download a CSV file containing the balance of each customer in the loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5076,18 +4431,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5099,7 +4442,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 'loyalty_program_id_example' # str | The identifier for the loyalty program.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
try:
# Export customer loyalty balance to CSV
@@ -5118,7 +4461,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **str**| The identifier for the loyalty program. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
### Return type
@@ -5126,7 +4469,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5148,14 +4491,16 @@ Name | Type | Description | Notes
Export customer loyalty balances
-Download a CSV file containing the balance of each customer in the loyalty program.
+Download a CSV file containing the balance of each customer in the loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The generated file can contain the following columns:
- `loyaltyProgramID`: The ID of the loyalty program.
-- `loyaltySubledger`: The name of the subdleger, when applicatble.
+- `loyaltySubledger`: The name of the subledger, when applicable.
- `profileIntegrationID`: The integration ID of the customer profile.
- `currentBalance`: The current point balance.
- `pendingBalance`: The number of pending points.
@@ -5166,8 +4511,6 @@ The generated file can contain the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5186,18 +4529,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5209,7 +4540,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 'loyalty_program_id_example' # str | The identifier for the loyalty program.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. (optional)
try:
# Export customer loyalty balances
@@ -5228,7 +4559,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **str**| The identifier for the loyalty program. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. | [optional]
### Return type
@@ -5236,7 +4567,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5258,15 +4589,19 @@ Name | Type | Description | Notes
Export all card transaction logs
-Download a CSV file containing the balances of all cards in the loyalty program.
+Download a CSV file containing the balances of all cards in the loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
- `loyaltyProgramID`: The ID of the loyalty program.
- `loyaltySubledger`: The name of the subdleger, when applicatble.
-- `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`.
-- `cardState`:The state of the loyalty card. It can be `active` or `inactive`.
+- `cardIdentifier`: The identifier of the loyalty card, which must match the regular
+expression `^[A-Za-z0-9._%+@-]+$`.
+- `cardState`:The state of the loyalty card. It can be `active` or
+`inactive`.
- `currentBalance`: The current point balance.
- `pendingBalance`: The number of pending points.
- `expiredBalance`: The number of expired points.
@@ -5275,8 +4610,6 @@ The CSV file contains the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5295,18 +4628,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5318,7 +4639,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
try:
# Export all card transaction logs
@@ -5337,7 +4658,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
### Return type
@@ -5345,7 +4666,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5367,15 +4688,15 @@ Name | Type | Description | Notes
Export card's ledger log
-Download a CSV file containing a loyalty card ledger log of the loyalty program.
+Download a CSV file containing a loyalty card ledger log of the loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5394,18 +4715,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5418,8 +4727,8 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
loyalty_card_id = 'loyalty_card_id_example' # str | Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`.
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
date_format = 'date_format_example' # str | Determines the format of dates in the export document. (optional)
try:
@@ -5440,8 +4749,8 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**loyalty_card_id** | **str**| Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. |
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**date_format** | **str**| Determines the format of dates in the export document. | [optional]
### Return type
@@ -5450,7 +4759,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5472,11 +4781,14 @@ Name | Type | Description | Notes
Export loyalty cards
-Download a CSV file containing the loyalty cards from a specified loyalty program.
+Download a CSV file containing the loyalty cards from a specified loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
+
- `identifier`: The unique identifier of the loyalty card.
- `created`: The date and time the loyalty card was created.
- `status`: The status of the loyalty card.
@@ -5485,12 +4797,11 @@ The CSV file contains the following columns:
- `blockreason`: The reason for transferring and blocking the loyalty card.
- `generated`: An indicator of whether the loyalty card was generated.
- `batchid`: The ID of the batch the loyalty card is in.
+- `attributes`: The custom attributes of this loyalty card. Currently, this feature is only available upon request.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5509,18 +4820,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5533,8 +4832,8 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
batch_id = 'batch_id_example' # str | Filter results by loyalty card batch ID. (optional)
- created_before = '2013-10-20T19:20:30+01:00' # datetime | Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string. (optional)
- created_after = '2013-10-20T19:20:30+01:00' # datetime | Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string. (optional)
+ created_before = '2013-10-20T19:20:30+01:00' # datetime | Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string. (optional)
+ created_after = '2013-10-20T19:20:30+01:00' # datetime | Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string. (optional)
date_format = 'date_format_example' # str | Determines the format of dates in the export document. (optional)
try:
@@ -5555,8 +4854,8 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**batch_id** | **str**| Filter results by loyalty card batch ID. | [optional]
- **created_before** | **datetime**| Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string. | [optional]
- **created_after** | **datetime**| Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string. | [optional]
+ **created_before** | **datetime**| Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string. | [optional]
+ **created_after** | **datetime**| Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string. | [optional]
**date_format** | **str**| Determines the format of dates in the export document. | [optional]
### Return type
@@ -5565,7 +4864,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5589,7 +4888,8 @@ Export customers' loyalty program join dates
Download a CSV file containing the join dates of all customers in the loyalty program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The generated file can contain the following columns:
@@ -5600,8 +4900,6 @@ The generated file can contain the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5620,18 +4918,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5668,7 +4954,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5690,9 +4976,11 @@ Name | Type | Description | Notes
Export customer's transaction logs
-Download a CSV file containing a customer's transaction logs in the loyalty program.
+Download a CSV file containing a customer's transaction logs in the loyalty
+program.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The generated file can contain the following columns:
@@ -5717,8 +5005,6 @@ The generated file can contain the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5737,18 +5023,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5759,8 +5033,8 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
loyalty_program_id = 'loyalty_program_id_example' # str | The identifier for the loyalty program.
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
date_format = 'date_format_example' # str | Determines the format of dates in the export document. (optional)
@@ -5781,8 +5055,8 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**loyalty_program_id** | **str**| The identifier for the loyalty program. |
**integration_id** | **str**| The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. |
**date_format** | **str**| Determines the format of dates in the export document. | [optional]
@@ -5793,7 +5067,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5813,9 +5087,11 @@ Name | Type | Description | Notes
Export giveaway codes of a giveaway pool
-Download a CSV file containing the giveaway codes of a specific giveaway pool.
+Download a CSV file containing the giveaway codes of a specific giveaway
+pool.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
@@ -5828,14 +5104,16 @@ The CSV file contains the following columns:
- `used`: An indication of whether the giveaway is already awarded.
- `importid`: The ID of the import which created the giveaway.
- `created`: The creation time of the giveaway code.
-- `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded.
-- `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
+- `profileintegrationid`: The third-party integration ID of the customer
+ profile that was awarded the giveaway. Can be empty if the giveaway was not
+ awarded.
+- `profileid`: The internal ID of the customer profile that was awarded the
+ giveaway. Can be empty if the giveaway was not awarded or an internal ID
+ does not exist.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5854,18 +5132,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -5906,7 +5172,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -5927,9 +5193,11 @@ Name | Type | Description | Notes
Export referrals
-Download a CSV file containing the referrals that match the given parameters.
+Download a CSV file containing the referrals that match the given
+parameters.
-**Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+> [!tip] If the exported CSV file is too large to view, you can
+> [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
The CSV file contains the following columns:
@@ -5943,8 +5211,6 @@ The CSV file contains the following columns:
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -5963,18 +5229,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6025,7 +5279,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6050,8 +5304,6 @@ Create a summary of the reasons for coupon redemption failures in a given custom
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6071,18 +5323,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6125,7 +5365,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6150,8 +5390,6 @@ Retrieve the list of API calls sent to the specified Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6171,18 +5409,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6194,8 +5420,8 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
path = 'path_example' # str | Only return results where the request path matches the given regular expression. (optional)
method = 'method_example' # str | Only return results where the request method matches the given regular expression. (optional)
status = 'status_example' # str | Filter results by HTTP status codes. (optional)
@@ -6220,8 +5446,8 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**path** | **str**| Only return results where the request path matches the given regular expression. | [optional]
**method** | **str**| Only return results where the request method matches the given regular expression. | [optional]
**status** | **str**| Filter results by HTTP status codes. | [optional]
@@ -6235,7 +5461,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6260,8 +5486,6 @@ Return the details of your companies Talon.One account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6281,18 +5505,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6303,7 +5515,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- account_id = 56 # int | The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property.
+ account_id = 56 # int | The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property.
try:
# Get account details
@@ -6321,7 +5533,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **account_id** | **int**| The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. |
+ **account_id** | **int**| The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. |
### Return type
@@ -6329,7 +5541,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6354,8 +5566,6 @@ Return the analytics of your Talon.One account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6375,18 +5585,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6397,7 +5595,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- account_id = 56 # int | The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property.
+ account_id = 56 # int | The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property.
try:
# Get account analytics
@@ -6415,7 +5613,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **account_id** | **int**| The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. |
+ **account_id** | **int**| The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. |
### Return type
@@ -6423,7 +5621,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6447,8 +5645,6 @@ Retrieve a given account-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6468,18 +5664,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6490,7 +5674,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
try:
# Get account-level collection
@@ -6508,7 +5692,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
### Return type
@@ -6516,7 +5700,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6541,8 +5725,6 @@ Get the details of a specific achievement.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6562,18 +5744,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6614,7 +5784,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6641,8 +5811,6 @@ Returns the additional cost.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6662,18 +5830,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6710,7 +5866,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6735,8 +5891,6 @@ Returns all the defined additional costs for the account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6756,18 +5910,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6808,7 +5950,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6832,8 +5974,6 @@ Get the application specified by the ID.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6853,18 +5993,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6901,7 +6029,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -6930,8 +6058,6 @@ See the [docs](https://docs.talon.one/docs/dev/tutorials/monitoring-integration-
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -6951,18 +6077,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -6999,7 +6113,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7024,8 +6138,6 @@ Retrieve the customers of the specified application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7045,18 +6157,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7068,7 +6168,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
- customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
try:
# Get application's customer
@@ -7087,7 +6187,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
- **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
### Return type
@@ -7095,7 +6195,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7120,8 +6220,6 @@ List the friends referred by the specified customer profile in this Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7141,18 +6239,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7199,7 +6285,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7223,8 +6309,6 @@ List all the customers of the specified application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7244,18 +6328,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7300,7 +6372,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7327,8 +6399,6 @@ The match is successful if all the attributes of the request are found in a prof
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7349,18 +6419,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7405,7 +6463,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7432,8 +6490,6 @@ See also: [Track an event](https://docs.talon.one/integration-api#tag/Events/ope
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7453,18 +6509,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7507,7 +6551,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7532,8 +6576,6 @@ Lists all events recorded for an application. Instead of having the total number
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7553,18 +6595,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7631,7 +6661,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7657,8 +6687,6 @@ You can list the sessions with the [List Application sessions](https://docs.talo
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7678,18 +6706,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7728,7 +6744,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7753,8 +6769,6 @@ List all the sessions of the specified Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7774,18 +6788,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7846,7 +6848,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7870,8 +6872,6 @@ List all applications in the current account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7891,18 +6891,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -7943,7 +6931,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -7968,8 +6956,6 @@ Retrieve the specified custom attribute.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -7989,18 +6975,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8037,7 +7011,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8062,8 +7036,6 @@ Return all the custom attributes for the account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8083,18 +7055,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8145,7 +7105,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8172,8 +7132,6 @@ A maximum of 1000 customer profiles per page is allowed.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8193,18 +7151,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8249,7 +7195,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8275,8 +7221,6 @@ Get all audiences created in the account. To create an audience, use [Create aud
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8296,18 +7240,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8350,7 +7282,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8375,8 +7307,6 @@ Get a list of audience IDs and their member count.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8396,18 +7326,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8446,7 +7364,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8470,8 +7388,6 @@ Retrieve the given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8491,18 +7407,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8541,7 +7445,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8565,8 +7469,6 @@ Retrieve statistical data about the performance of the given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8586,18 +7488,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8610,8 +7500,8 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
granularity = 'granularity_example' # str | The time interval between the results in the returned time-series. (optional)
try:
@@ -8632,8 +7522,8 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**granularity** | **str**| The time interval between the results in the returned time-series. | [optional]
### Return type
@@ -8642,7 +7532,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8667,8 +7557,6 @@ Get a list of all the campaigns that match a set of attributes.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8689,18 +7577,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8747,7 +7623,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8771,8 +7647,6 @@ Get a campaign access group specified by its ID.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8792,18 +7666,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8840,7 +7702,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8864,8 +7726,6 @@ List the campaign access groups in the current account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8885,18 +7745,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -8937,7 +7785,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -8961,8 +7809,6 @@ Retrieve a list of campaign templates.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -8982,18 +7828,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9042,7 +7876,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9067,8 +7901,6 @@ List the campaigns of the specified application that match your filter criteria.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9088,18 +7920,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9166,7 +7986,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9192,8 +8012,6 @@ Retrieve the audit logs displayed in **Accounts > Audit logs**.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9213,18 +8031,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9281,7 +8087,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9305,8 +8111,6 @@ Retrieve a given campaign-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9326,18 +8130,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9350,7 +8142,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.
try:
# Get campaign-level collection
@@ -9370,7 +8162,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. |
### Return type
@@ -9378,7 +8170,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9406,8 +8198,6 @@ You can retrieve items from both account-level collections and campaign-level co
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9427,18 +8217,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9449,7 +8227,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
page_size = 1000 # int | The number of items in the response. (optional) (default to 1000)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
@@ -9469,7 +8247,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
**page_size** | **int**| The number of items in the response. | [optional] [default to 1000]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
@@ -9479,7 +8257,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9505,8 +8283,6 @@ List all the coupons matching the specified criteria.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9526,18 +8302,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9612,7 +8376,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9636,8 +8400,6 @@ Fetch the summary report of a given customer in the given application, in a time
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9657,18 +8419,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9679,10 +8429,10 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
- customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
page_size = 1000 # int | The number of items in the response. (optional) (default to 1000)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
@@ -9702,10 +8452,10 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
- **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
**page_size** | **int**| The number of items in the response. | [optional] [default to 1000]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
@@ -9715,7 +8465,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9741,8 +8491,6 @@ in the response, this endpoint only mentions whether there are more results.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9762,18 +8510,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9784,8 +8520,8 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
page_size = 1000 # int | The number of items in the response. (optional) (default to 1000)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
@@ -9811,8 +8547,8 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**page_size** | **int**| The number of items in the response. | [optional] [default to 1000]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
@@ -9828,7 +8564,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9852,8 +8588,6 @@ Fetch analytics for a given customer in the given application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9873,18 +8607,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -9896,7 +8618,7 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
- customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
page_size = 1000 # int | The number of items in the response. (optional) (default to 1000)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
sort = 'sort_example' # str | The field by which results should be sorted. By default, results are sorted in ascending order. To sort them in descending order, prefix the field name with `-`. **Note:** You may not be able to use all fields for sorting. This is due to performance limitations. (optional)
@@ -9918,7 +8640,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
- **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
**page_size** | **int**| The number of items in the response. | [optional] [default to 1000]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
**sort** | **str**| The field by which results should be sorted. By default, results are sorted in ascending order. To sort them in descending order, prefix the field name with `-`. **Note:** You may not be able to use all fields for sorting. This is due to performance limitations. | [optional]
@@ -9929,7 +8651,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -9951,21 +8673,15 @@ Get customer profile
Return the details of the specified customer profile.
-
-
Performance tips
-
- You can retrieve the same information via the Integration API, which can save you extra API requests. consider these options:
-
- - Request the customer profile to be part of the response content using
- [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2).
- - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
-
+> [!note]
+> You can retrieve the same information via the Integration API, which can save you extra API requests. Consider these options:
+> - Request the customer profile to be part of the response content using
+> [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2).
+> - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -9985,18 +8701,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10007,7 +8711,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint.
+ customer_id = 56 # int | The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint.
try:
# Get customer profile
@@ -10025,7 +8729,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. |
+ **customer_id** | **int**| The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. |
### Return type
@@ -10033,7 +8737,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10058,8 +8762,6 @@ For the given customer profile, list all the achievements that match your filter
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10079,18 +8781,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10137,7 +8827,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10163,8 +8853,6 @@ List all customer profiles.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10184,18 +8872,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10236,7 +8912,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10263,8 +8939,6 @@ The match is successful if all the attributes of the request are found in a prof
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10285,18 +8959,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10339,7 +9001,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10359,17 +9021,16 @@ Name | Type | Description | Notes
Get statistics for loyalty dashboard
-Retrieve the statistics displayed on the specified loyalty program's dashboard,
-such as the total active points, pending points, spent points, and expired points.
+Retrieve the statistics displayed on the specified loyalty program's
+dashboard, such as the total active points, pending points, spent points, and expired
+points.
-**Important:** The returned data does not include the current day. All statistics
-are updated daily at 11:59 PM in the loyalty program time zone.
+> [!important] The returned data does not include the current day. All statistics
+> are updated daily at 11:59 PM in the loyalty program time zone.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10389,18 +9050,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10412,8 +9061,8 @@ with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
- range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
- range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_start = '2013-10-20T19:20:30+01:00' # datetime | Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ range_end = '2013-10-20T19:20:30+01:00' # datetime | Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
subledger_id = 'subledger_id_example' # str | The ID of the subledger by which we filter the data. (optional)
try:
@@ -10433,8 +9082,8 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
- **range_start** | **datetime**| Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
- **range_end** | **datetime**| Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_start** | **datetime**| Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
+ **range_end** | **datetime**| Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. |
**subledger_id** | **str**| The ID of the subledger by which we filter the data. | [optional]
### Return type
@@ -10443,7 +9092,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10468,8 +9117,6 @@ Fetch all event type definitions for your account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10489,18 +9136,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10545,7 +9180,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10569,8 +9204,6 @@ Retrieve the given experiment associated with the Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10590,18 +9223,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10640,7 +9261,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10665,8 +9286,6 @@ List all past exports
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10686,18 +9305,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10742,7 +9349,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10766,8 +9373,6 @@ Get the given loyalty card.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10787,18 +9392,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10837,7 +9430,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10867,8 +9460,6 @@ If no filtering options are applied, the last 50 loyalty transactions for the gi
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -10888,18 +9479,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -10912,8 +9491,8 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
loyalty_card_id = 'loyalty_card_id_example' # str | Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`.
- start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
page_size = 1000 # int | The number of items in the response. (optional) (default to 1000)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger by which we filter the data. (optional)
@@ -10938,8 +9517,8 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**loyalty_card_id** | **str**| Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. |
- **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
- **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**page_size** | **int**| The number of items in the response. | [optional] [default to 1000]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
**subledger_id** | **str**| The ID of the subledger by which we filter the data. | [optional]
@@ -10952,7 +9531,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -10979,8 +9558,6 @@ For the given card-based loyalty program, list the loyalty cards that match your
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11000,18 +9577,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11060,7 +9625,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11082,22 +9647,30 @@ Name | Type | Description | Notes
Get customer's loyalty balances
-Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program.
-You can filter balances by date and subledger ID, and include tier-related information in the response.
+Retrieve loyalty ledger balances for the given Integration ID in the
+specified loyalty program.
+
+You can filter balances by date and subledger ID, and include tier-related
+information in the response.
-**Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID.
+> [!note] If no filtering options are applied, you retrieve all loyalty
+> balances on the current date for the given integration ID.
-Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance.
+Loyalty balances are calculated when Talon.One receives your request using
+the points stored in our database, so retrieving a large number of balances
+at once can impact performance.
For more information, see:
-- [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards)
-- [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+
+- [Managing card-based loyalty program
+data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards)
+
+- [Managing profile-based loyalty program
+data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11117,18 +9690,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11141,7 +9702,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger. (optional)
include_tiers = False # bool | Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. (optional) (default to False)
include_projected_tier = False # bool | Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. (optional) (default to False)
@@ -11164,7 +9725,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**integration_id** | **str**| The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. |
- **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**subledger_id** | **str**| The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger. | [optional]
**include_tiers** | **bool**| Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. | [optional] [default to False]
**include_projected_tier** | **bool**| Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. | [optional] [default to False]
@@ -11175,7 +9736,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11201,7 +9762,7 @@ Get customer's full loyalty ledger
Get the loyalty ledger for this profile integration ID.
To get the `integrationId` of the profile from a `sessionId`, use the
-[Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+[Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
**Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program,
we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
@@ -11209,8 +9770,6 @@ we recommend using the Integration API's [Get customer's loyalty logs](https://d
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11230,18 +9789,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11280,7 +9827,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11300,17 +9847,18 @@ Name | Type | Description | Notes
Get loyalty program
-Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview).
-To list all loyalty programs in your Application, use [List loyalty programs](#operation/getLoyaltyPrograms).
+Get the specified [loyalty
+program](https://docs.talon.one/docs/product/loyalty-programs/overview).
-To list the loyalty programs that a customer profile is part of, use the
-[List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory)
+To list all loyalty programs in your Application, use [List loyalty
+programs](#tag/Loyalty/operation/getLoyaltyPrograms).
+
+To list the loyalty programs that a customer profile is part of, use
+[List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11330,18 +9878,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11378,7 +9914,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11398,18 +9934,19 @@ Name | Type | Description | Notes
List customer's loyalty transactions
-Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program.
+Retrieve paginated results of loyalty transaction logs for the given
+Integration ID in the specified loyalty program.
-You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned.
+You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50
+loyalty transactions for the given integration ID are returned.
-**Note:** To retrieve all loyalty program transaction logs in a given loyalty program,
-use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+> [!note] To retrieve all loyalty program transaction logs in a given
+> loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions)
+> endpoint.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11429,18 +9966,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11453,12 +9978,12 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
loyalty_program_id = 56 # int | Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
integration_id = 'integration_id_example' # str | The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier.
- customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
- transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
+ customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
+ transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger. (optional)
loyalty_transaction_type = 'loyalty_transaction_type_example' # str | Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. (optional)
- start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
page_size = 50 # int | The number of items in the response. (optional) (default to 50)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
awaits_activation = True # bool | If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. (optional)
@@ -11481,12 +10006,12 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**loyalty_program_id** | **int**| Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**integration_id** | **str**| The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. |
- **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
- **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
+ **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
+ **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
**subledger_id** | **str**| The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger. | [optional]
**loyalty_transaction_type** | **str**| Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. | [optional]
- **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
- **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**page_size** | **int**| The number of items in the response. | [optional] [default to 50]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
**awaits_activation** | **bool**| If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. | [optional]
@@ -11497,7 +10022,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11520,17 +10045,19 @@ Name | Type | Description | Notes
List loyalty program transactions
-Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included.
-**Note:** If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned.
+Retrieve loyalty program transaction logs in a given loyalty program with
+filtering options applied. Manual and imported transactions are also
+included.
-**Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program,
-we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+> [!note] **Note**
+> - If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned.
+> - To get loyalty transaction logs for a given Integration ID in
+> a loyalty program, we recommend using the Integration API's [Get customer's loyalty
+> logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11550,18 +10077,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11575,10 +10090,10 @@ with talon_one.ApiClient(configuration) as api_client:
loyalty_program_id = 56 # int | Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint.
loyalty_transaction_type = 'loyalty_transaction_type_example' # str | Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. (optional)
subledger_id = 'subledger_id_example' # str | The ID of the subledger by which we filter the data. (optional)
- customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
- transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
- start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
- end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ customer_session_ids = ['customer_session_ids_example'] # List[str] | Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. (optional)
+ transaction_uuids = ['transaction_uuids_example'] # List[str] | Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. (optional)
+ start_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
+ end_date = '2013-10-20T19:20:30+01:00' # datetime | Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (optional)
page_size = 50 # int | The number of items in the response. (optional) (default to 50)
skip = 56 # int | The number of items to skip when paging through large result sets. (optional)
awaits_activation = True # bool | If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. (optional)
@@ -11602,10 +10117,10 @@ Name | Type | Description | Notes
**loyalty_program_id** | **int**| Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. |
**loyalty_transaction_type** | **str**| Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. | [optional]
**subledger_id** | **str**| The ID of the subledger by which we filter the data. | [optional]
- **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
- **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
- **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
- **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **customer_session_ids** | [**List[str]**](str.md)| Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. | [optional]
+ **transaction_uuids** | [**List[str]**](str.md)| Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. | [optional]
+ **start_date** | **datetime**| Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
+ **end_date** | **datetime**| Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. | [optional]
**page_size** | **int**| The number of items in the response. | [optional] [default to 50]
**skip** | **int**| The number of items to skip when paging through large result sets. | [optional]
**awaits_activation** | **bool**| If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. | [optional]
@@ -11616,7 +10131,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11643,8 +10158,6 @@ List the loyalty programs of the account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11664,18 +10177,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11708,7 +10209,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11728,9 +10229,10 @@ This endpoint does not need any parameter.
Get loyalty program statistics
-⚠️ Deprecation notice: Support for requests to this endpoint will end soon.
-To retrieve statistics for a loyalty program, use the [Get statistics for
-loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics)
+> [warning] This endpoint is deprecated.
+
+To retrieve statistics for a loyalty program, use the
+[Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics)
endpoint.
Retrieve the statistics of the specified loyalty program, such as the
@@ -11739,8 +10241,6 @@ total active points, pending points, spent points, and expired points.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11760,18 +10260,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11808,7 +10296,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11832,8 +10320,6 @@ Retrieve all message log entries.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11853,18 +10339,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -11881,7 +10355,7 @@ with talon_one.ApiClient(configuration) as api_client:
notification_ids = 'notification_ids_example' # str | Filter results by notification ID (include up to 30 values, separated by a comma). (optional)
created_before = '2013-10-20T19:20:30+01:00' # datetime | Filter results where request and response times to return entries before parameter value, expected to be an RFC3339 timestamp string. Use UTC time. (optional)
created_after = '2013-10-20T19:20:30+01:00' # datetime | Filter results where request and response times to return entries after parameter value, expected to be an RFC3339 timestamp string. Use UTC time. (optional)
- cursor = None # bytearray | A specific unique value in the database. If this value is not given, the server fetches results starting with the first record. (optional)
+ cursor = None # bytes | A specific unique value in the database. If this value is not given, the server fetches results starting with the first record. (optional)
period = 'period_example' # str | Filter results by time period. Choose between the available relative time frames. (optional)
is_successful = True # bool | Indicates whether to return log entries with either successful or unsuccessful HTTP response codes. When set to`true`, only log entries with `2xx` response codes are returned. When set to `false`, only log entries with `4xx` and `5xx` response codes are returned. (optional)
application_id = 3.4 # float | Filter results by Application ID. (optional)
@@ -11912,7 +10386,7 @@ Name | Type | Description | Notes
**notification_ids** | **str**| Filter results by notification ID (include up to 30 values, separated by a comma). | [optional]
**created_before** | **datetime**| Filter results where request and response times to return entries before parameter value, expected to be an RFC3339 timestamp string. Use UTC time. | [optional]
**created_after** | **datetime**| Filter results where request and response times to return entries after parameter value, expected to be an RFC3339 timestamp string. Use UTC time. | [optional]
- **cursor** | **bytearray**| A specific unique value in the database. If this value is not given, the server fetches results starting with the first record. | [optional]
+ **cursor** | **bytes**| A specific unique value in the database. If this value is not given, the server fetches results starting with the first record. | [optional]
**period** | **str**| Filter results by time period. Choose between the available relative time frames. | [optional]
**is_successful** | **bool**| Indicates whether to return log entries with either successful or unsuccessful HTTP response codes. When set to`true`, only log entries with `2xx` response codes are returned. When set to `false`, only log entries with `4xx` and `5xx` response codes are returned. | [optional]
**application_id** | **float**| Filter results by Application ID. | [optional]
@@ -11927,7 +10401,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -11951,8 +10425,6 @@ List all referrals of the specified campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -11972,18 +10444,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12040,7 +10500,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12065,8 +10525,6 @@ Get the details of a specific role. To see all the roles, use the [List roles](/
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12086,18 +10544,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12134,7 +10580,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12158,8 +10604,6 @@ Retrieve the specified ruleset.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12179,18 +10623,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12231,7 +10663,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12258,8 +10690,6 @@ You should only consider the latest revision of the returned rulesets.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12279,18 +10709,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12335,7 +10753,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12359,8 +10777,6 @@ Get store details for a specific store ID.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12380,18 +10796,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12430,7 +10834,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12456,8 +10860,6 @@ Retrieve the data (including an invitation code) for a user. Non-admin users can
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12477,18 +10879,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12525,7 +10915,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12550,8 +10940,6 @@ Retrieve all users in your account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12571,18 +10959,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12623,7 +10999,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12647,8 +11023,6 @@ Returns a webhook by its id.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12668,18 +11042,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12716,7 +11078,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12740,8 +11102,6 @@ List all webhooks.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12761,18 +11121,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -12823,7 +11171,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12843,7 +11191,9 @@ Name | Type | Description | Notes
Import data into existing account-level collection
-Upload a CSV file containing the collection of string values that should be attached as payload for collection.
+Upload a CSV file containing the collection of string values that should be
+attached as payload for collection.
+
The file should be sent as multipart data.
The import **replaces** the initial content of the collection.
@@ -12854,22 +11204,21 @@ The CSV file **must** only contain the following column:
A collection is limited to 500,000 items.
-Example:
+## Example
```
item
-Addidas
+Adidas
Nike
Asics
```
-**Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+> [!note] Before sending a request to this endpoint, ensure the data in the
+> CSV to import is different from the data currently stored in the collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -12889,29 +11238,17 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
+# Configure API key authorization: api_key_v1
+configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
-# Configure API key authorization: api_key_v1
-configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['api_key_v1'] = 'Bearer'
+# configuration.api_key_prefix['api_key_v1'] = 'Bearer'
# Enter a context with an instance of the API client
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
up_file = 'up_file_example' # str | The file containing the data that is being imported. (optional)
try:
@@ -12930,7 +11267,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
**up_file** | **str**| The file containing the data that is being imported. | [optional]
### Return type
@@ -12939,7 +11276,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -12961,18 +11298,22 @@ Name | Type | Description | Notes
Import allowed values for attribute
-Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute.
+Upload a CSV file containing a list of [picklist
+values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values)
+for the specified attribute.
The file should be sent as multipart data.
-The import **replaces** the previous list of allowed values for this attribute, if any.
+The import **replaces** the previous list of allowed values for this
+attribute, if any.
The CSV file **must** only contain the following column:
-- `item` (required): the values in your allowed list, for example a list of SKU's.
+
+- `item`: The values in your allowed list, for example a list of SKUs.
An allowed list is limited to 500,000 items.
-Example:
+## Example
```text
item
@@ -12984,8 +11325,6 @@ CS-DG-02082021-UP-50G-07
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13005,18 +11344,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13055,7 +11382,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13078,16 +11405,19 @@ Name | Type | Description | Notes
Import audience members
-Upload a CSV file containing the integration IDs of the members you want to add to an audience.
+Upload a CSV file containing the integration IDs of the members you want to
+add to an audience.
+
+The file should be sent as multipart data and should contain only the
+following column (required):
-The file should be sent as multipart data and should contain only the following column (required):
- `profileintegrationid`: The integration ID of the customer profile.
The import **replaces** the previous list of audience members.
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500 MB.
-Example:
+## Example
```text
profileintegrationid
@@ -13098,8 +11428,6 @@ alexa
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13119,18 +11447,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13169,7 +11485,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13205,8 +11521,6 @@ The import **replaces** the previous list of store budgets.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13226,18 +11540,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13282,7 +11584,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13315,8 +11617,6 @@ The import **replaces** the previous list of stores linked to the campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13336,18 +11636,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13388,7 +11676,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13411,7 +11699,9 @@ Name | Type | Description | Notes
Import data into existing campaign-level collection
-Upload a CSV file containing the collection of string values that should be attached as payload for collection.
+Upload a CSV file containing the collection of string values that should be
+attached as payload for collection.
+
The file should be sent as multipart data.
The import **replaces** the initial content of the collection.
@@ -13422,22 +11712,21 @@ The CSV file **must** only contain the following column:
A collection is limited to 500,000 items.
-Example:
+## Example
```
item
-Addidas
+Adidas
Nike
Asics
```
-**Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+> [!note] Before sending a request to this endpoint, ensure the data in the
+> CSV to import is different from the data currently stored in the collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13457,18 +11746,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13481,7 +11758,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.
up_file = 'up_file_example' # str | The file containing the data that is being imported. (optional)
try:
@@ -13502,7 +11779,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. |
**up_file** | **str**| The file containing the data that is being imported. | [optional]
### Return type
@@ -13511,7 +11788,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13532,7 +11809,8 @@ Name | Type | Description | Notes
Import coupons
-Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data.
+Upload a CSV file containing the coupons that should be created. The file
+should be sent as multipart data.
The CSV file contains the following columns:
@@ -13540,37 +11818,33 @@ The CSV file contains the following columns:
There is no maximum length but limiting the code to 30 characters
ensures it is fully readable in the Campaign Manager.
The code should be unique unless you set `skipDuplicates` to `true`.
-
- `expirydate`: The end date in RFC3339 of the code redemption period.
- `startdate`: The start date in RFC3339 of the code redemption period.
- `recipientintegrationid`: The integration ID of the recipient of the coupon.
Only the customer with this integration ID can redeem this code. Available only for personal codes.
- `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided.
- `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value.
-- `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks.
-
+- `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes)
called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `"{"category": "10_off"}"`.
You can use the time zone of your choice. It is converted to UTC internally by Talon.One.
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500 MB.
-**Example:**
+## Example
```text
"value","expirydate","startdate","recipientintegrationid","limitval","attributes","discountlimit"
-COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,"{""Category"": ""10_off""}",2.4
+COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,"{""Category"":
+""10_off""}",2.4
```
-Once imported, you can find the `batchId` in the Campaign Manager or by
-using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
+Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13590,18 +11864,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13644,7 +11906,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13664,18 +11926,24 @@ Name | Type | Description | Notes
Import loyalty cards
-Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program.
+Upload a CSV file containing the loyalty cards that you want to use in your
+card-based loyalty program.
+
Send the file as multipart data.
It contains the following columns for each card:
-- `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`.
-- `state` (required): The state of the loyalty card. It can be `active` or `inactive`.
-- `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;).
+- `identifier` (required): The identifier of the loyalty card,
+which must match the regular expression `^[A-Za-z0-9._%+@-]+$`.
+- `state` (required): The state of the loyalty card. It can be `active` or
+`inactive`.
+- `customerprofileids` (optional): An array of strings representing the
+identifiers of the customer profiles linked to the loyalty card. The
+identifiers should be separated with a semicolon (;).
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500MB.
-**Example:**
+## Example
```csv
identifier,state,customerprofileids
@@ -13685,8 +11953,6 @@ identifier,state,customerprofileids
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13706,18 +11972,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13756,7 +12010,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13778,29 +12032,45 @@ Name | Type | Description | Notes
Import customers into loyalty tiers
-Upload a CSV file containing existing customers to be assigned to existing tiers.
+Upload a CSV file containing existing customers to be assigned to existing
+tiers.
+
Send the file as multipart data.
-**Important:** This endpoint only works with loyalty programs with advanced tiers (with expiration and downgrade policy) feature enabled.
+> [!important] This endpoint only works with loyalty programs with advanced
+> tiers (with expiration and downgrade policy) feature enabled.
The CSV file should contain the following columns:
-- `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used.
-- `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned.
+
+- `subledgerid` (optional): The ID of the subledger. If this field is empty,
+the main ledger will be used.
+- `customerprofileid`: The integration ID of the customer profile to whom
+the tier should be assigned.
- `tiername`: The name of an existing tier to assign to the customer.
-- `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date.
+- `expirydate`: The expiration date of the tier when the tier is
+reevaluated. It should be a future date.
About customer assignment to a tier:
-- If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import.
-- If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated.
-**Note:** We recommend not using this endpoint to update the tier of a customer.
-To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points.
+- If the customer isn't already in a tier, the customer is assigned to the
+specified tier during the tier import.
+- If the customer is already in the tier that's specified in the CSV file,
+only the expiration date is updated.
-You can use the time zone of your choice. It is converted to UTC internally by Talon.One.
+> [!note] We recommend not using this endpoint to update the tier of a customer.
+
+To update a customer's tier, you can
+[add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or
+[deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their
+loyalty points.
+
+You can use the time zone of your choice. It is converted to UTC internally
+by Talon.One.
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500 MB.
+
+## Example
-**Example:**
```csv
subledgerid,customerprofileid,tiername,expirydate
SUB1,alexa,Gold,2024-03-21T07:32:14Z
@@ -13811,8 +12081,6 @@ SUB2,avocado,Bronze,2026-05-03T11:47:01Z
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -13832,18 +12100,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -13882,7 +12138,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -13905,45 +12161,39 @@ Name | Type | Description | Notes
Import loyalty points
-Upload a CSV file containing the loyalty points you want to import into a given loyalty program.
+Upload a CSV file containing the loyalty points you want to import into a
+given loyalty program.
+
Send the file as multipart data.
-Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card.
+Depending on the type of loyalty program, you can import points into a given
+customer profile or loyalty card.
The CSV file contains the following columns:
-- `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported.
-
+- `customerprofileid` (optional): For profile-based loyalty programs, the
+ integration ID of the customer profile where the loyalty points are
+ imported.
**Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application
until a session or profile update is received for that profile.
- `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported.
- `amount`: The amount of points to award to the customer profile.
- `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date.
-
This parameter accepts one of the following values:
- - A timestamp string in RFC3339 format.
- - `immediate`
- - `on_action`
-
- **Note**:
- Empty or missing values default to `immediate`.
-- `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date.
-
+ - A timestamp string in RFC3339 format.
+ - `immediate`
+ - `on_action`
+ **Note**: Empty or missing values default to `immediate`.
+- `expirydate` (optional): The latest date when the points can be redeemed.
+ The points are `expired` after this date.
**Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`.
-
If passed, `validityDuration` should be omitted.
-- `validityDuration` (optional): The duration for which the points remain active, relative to the
- activation date.
-
- The time format is an **integer** followed by one letter indicating the time unit.
-
-
+- `validityDuration` (optional): The duration for which the points remain active, relative to the
+ activation date. The time format is an **integer** followed by one letter indicating the time unit.
Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`.
-
Available units:
-
- `s`: seconds
- `m`: minutes
- `h`: hours
@@ -13952,7 +12202,6 @@ The CSV file contains the following columns:
- `M`: months
- `Y`: years
-
You can round certain units up or down:
- `_D` for rounding down days only. Signifies the start of the day.
@@ -13965,20 +12214,22 @@ The CSV file contains the following columns:
You can use the time zone of your choice. It is converted to UTC internally by Talon.One.
-**Note:** For existing customer profiles and loyalty cards, the imported points are added to any previous active or pending points, depending on the
-value provided for `startdate`. If `startdate` matches the current date, the imported points are _active_. If it is later, the points are _pending_ until
-the date provided for `startdate` is reached.
+> [!note] For existing customer profiles and loyalty cards, the imported
+> points are added to any previous active or pending points, depending on the
+> value provided for `startdate`. If `startdate` matches the current date, the
+> imported points are _active_. If it is later, the points are _pending_ until
+> the date provided for `startdate` is reached.
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500 MB.
-**Example for profile-based programs:**
+## Example for profile-based programs
```text
customerprofileid,amount,startdate,expirydate,subledgerid,reason
URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement
```
-**Example for card-based programs:**
+## Example for card-based programs
```text
identifier,amount,startdate,expirydate,subledgerid,reason
@@ -13988,8 +12239,6 @@ summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14009,18 +12258,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14061,7 +12298,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14081,39 +12318,43 @@ Name | Type | Description | Notes
Import giveaway codes into a giveaway pool
-Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data.
+Upload a CSV file containing the giveaway codes that should be created. Send
+the file as multipart data.
The CSV file contains the following columns:
+
- `code` (required): The code of your giveaway, for instance, a gift card redemption code.
- `startdate`: The start date in RFC3339 of the code redemption period.
- `enddate`: The last date in RFC3339 of the code redemption period.
-- `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks.
-
+- `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes)
called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `"{"provider": "myPartnerCompany"}"`.
-The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not.
-You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One.
+The `startdate` and `enddate` have nothing to do with the _validity_ of the
+codes. They are only used by the Rule Engine to award the codes or not.
-**Note:**
+You can use the time zone setting of your choice. The values are converted
+to UTC internally by Talon.One.
-- We recommend limiting your file size to 500MB.
-- You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes.
+> [!note] **Note**
+> - We recommend limiting your file size to 500MB.
+> - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes.
-**Example:**
+## Example
```text
code,startdate,enddate,attributes
-GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"": ""Amazon""}"
-GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"": ""Amazon""}"
-GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"": ""Aliexpress""}"
+GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"":
+""Amazon""}"
+GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"":
+""Amazon""}"
+GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,"{""provider"":
+""Aliexpress""}"
```
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14133,18 +12374,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14183,7 +12412,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14204,6 +12433,7 @@ Name | Type | Description | Notes
Import referrals
Upload a CSV file containing the referrals that should be created.
+
The file should be sent as multipart data.
The CSV file contains the following columns:
@@ -14213,33 +12443,34 @@ The CSV file contains the following columns:
- `startdate`: The start date in RFC3339 of the code redemption period.
- `expirydate`: The end date in RFC3339 of the code redemption period.
- `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank.
-- `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks.
-
+- `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes)
called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `"{"category": "10_off"}"`.
You can use the time zone of your choice. It is converted to UTC internally by Talon.One.
-**Important:** When you import a CSV file with referrals, a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles)
-is **not** automatically created for each `advocateprofileintegrationid` column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2)
-endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2)
-endpoint to create the customer profiles.
+> [!important] When you import a CSV file with referrals,
+> a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles)
+> is **not** automatically created for each `advocateprofileintegrationid`
+> column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2)
+> endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2)
+> endpoint to create the customer profiles.
-**Note:** We recommend limiting your file size to 500MB.
+> [!note] We recommend limiting your file size to 500 MB.
-**Example:**
+## Example
```text
code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes
-REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,"{""my_attribute"": ""10_off""}"
-REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,"{""my_attribute"": ""20_off""}"
+REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,"{""my_attribute"":
+""10_off""}"
+REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,"{""my_attribute"":
+""20_off""}"
```
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14259,18 +12490,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14311,7 +12530,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14336,8 +12555,6 @@ Invite user from identity provider
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14357,18 +12574,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14403,7 +12608,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14427,8 +12632,6 @@ List account-level collections in the account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14448,18 +12651,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14504,7 +12695,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14531,8 +12722,6 @@ List all the achievements for a specific campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14552,18 +12741,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14608,7 +12785,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14632,8 +12809,6 @@ List all roles.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14653,18 +12828,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14697,7 +12860,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14721,8 +12884,6 @@ Return the store budget limits for a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14742,18 +12903,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14796,7 +12945,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14824,8 +12973,6 @@ Return a paginated list of cart items in the given catalog.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14845,18 +12992,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -14903,7 +13038,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -14927,8 +13062,6 @@ List collections in a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -14948,18 +13081,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15008,7 +13129,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15033,8 +13154,6 @@ List campaign-level collections from all campaigns in a given Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15054,18 +13173,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15112,7 +13219,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15137,8 +13244,6 @@ List all experiments of the specified Application that match your filter criteri
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15158,18 +13263,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15212,7 +13305,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15236,8 +13329,6 @@ List all stores for a specific Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15257,18 +13348,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15321,7 +13400,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15349,8 +13428,6 @@ for provisioning and deprovisioning of Talon.One users, and that only Talon.One
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15369,18 +13446,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15411,7 +13476,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15426,25 +13491,108 @@ void (empty response body)
[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
+# **price_history**
+> PriceHistoryResponse price_history(application_id, price_history_request)
+
+Get summary of price history
+
+Fetch the historical price data for a given SKU within a defined timeframe.
+
+
+### Example
+
+* Api Key Authentication (api_key_v1):
+
+```python
+import talon_one
+from talon_one.models.price_history_request import PriceHistoryRequest
+from talon_one.models.price_history_response import PriceHistoryResponse
+from talon_one.rest import ApiException
+from pprint import pprint
+
+# Defining the host is optional and defaults to https://yourbaseurl.talon.one
+# See configuration.py for a list of all supported configuration parameters.
+configuration = talon_one.Configuration(
+ host = "https://yourbaseurl.talon.one"
+)
+
+# The client must configure the authentication and authorization parameters
+# in accordance with the API server security policy.
+# Examples for each auth method are provided below, use the example that
+# satisfies your auth use case.
+
+# Configure API key authorization: api_key_v1
+configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
+
+# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
+# configuration.api_key_prefix['api_key_v1'] = 'Bearer'
+
+# Enter a context with an instance of the API client
+with talon_one.ApiClient(configuration) as api_client:
+ # Create an instance of the API class
+ api_instance = talon_one.ManagementApi(api_client)
+ application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
+ price_history_request = talon_one.PriceHistoryRequest() # PriceHistoryRequest | body
+
+ try:
+ # Get summary of price history
+ api_response = api_instance.price_history(application_id, price_history_request)
+ print("The response of ManagementApi->price_history:\n")
+ pprint(api_response)
+ except Exception as e:
+ print("Exception when calling ManagementApi->price_history: %s\n" % e)
+```
+
+
+
+### Parameters
+
+
+Name | Type | Description | Notes
+------------- | ------------- | ------------- | -------------
+ **application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
+ **price_history_request** | [**PriceHistoryRequest**](PriceHistoryRequest.md)| body |
+
+### Return type
+
+[**PriceHistoryResponse**](PriceHistoryResponse.md)
+
+### Authorization
+
+[api_key_v1](../README.md#api_key_v1)
+
+### HTTP request headers
+
+ - **Content-Type**: application/json
+ - **Accept**: application/json
+
+### HTTP response details
+
+| Status code | Description | Response headers |
+|-------------|-------------|------------------|
+**200** | Ok | - |
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
+
# **remove_loyalty_points**
> remove_loyalty_points(loyalty_program_id, integration_id, deduct_loyalty_points)
Deduct points from customer profile
-Deduct points from the specified loyalty program and specified customer profile.
+Deduct points from the specified loyalty program and specified customer
+profile.
-**Important:**
-- Only active points can be deducted.
-- Only pending points are rolled back when a session is cancelled or reopened.
+> [!note] **Note**
+> - Only active points can be deducted.
+> - Only pending points are rolled back when a session is cancelled or reopened.
To get the `integrationId` of the profile from a `sessionId`, use the
-[Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+[Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2)
+endpoint.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15464,18 +13612,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15514,7 +13650,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15543,8 +13679,6 @@ the associated account.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15564,18 +13698,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15612,7 +13734,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15637,8 +13759,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15659,18 +13779,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15707,7 +13815,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15731,8 +13839,6 @@ Create a new Talon.One user using the SCIM provisioning protocol with an identit
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15753,18 +13859,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15801,7 +13895,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15826,8 +13920,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15846,18 +13938,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15892,7 +13972,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -15916,8 +13996,6 @@ Delete a specific Talon.One user created using the SCIM provisioning protocol wi
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -15936,18 +14014,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -15982,7 +14048,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16007,8 +14073,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16028,18 +14092,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16076,7 +14128,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16101,8 +14153,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16122,18 +14172,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16166,7 +14204,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16193,8 +14231,6 @@ Resource types define the various kinds of resources that can be managed via the
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16214,18 +14250,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16258,7 +14282,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16285,8 +14309,6 @@ Schemas define the structure and attributes of the different resources that can
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16306,18 +14328,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16350,7 +14360,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16375,8 +14385,6 @@ Retrieve the configuration settings of the SCIM service provider. It provides de
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16396,18 +14404,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16440,7 +14436,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16464,8 +14460,6 @@ Retrieve data for a specific Talon.One user created using the SCIM provisioning
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16485,18 +14479,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16533,7 +14515,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16557,8 +14539,6 @@ Retrieve a paginated list of users that have been provisioned using the SCIM pro
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16578,18 +14558,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16622,7 +14590,7 @@ This endpoint does not need any parameter.
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16648,8 +14616,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16670,18 +14636,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16720,7 +14674,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16747,8 +14701,6 @@ This endpoint allows for selective adding, removing, or replacing specific attri
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16769,18 +14721,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16819,7 +14759,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16845,8 +14785,6 @@ In Talon.One, a `Group` corresponds to a [role](https://docs.talon.one/docs/prod
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16867,18 +14805,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -16917,7 +14843,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -16944,8 +14870,6 @@ This endpoint replaces all attributes of the specific user with the attributes p
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -16966,18 +14890,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17016,7 +14928,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17036,18 +14948,17 @@ Name | Type | Description | Notes
List coupons that match the given attributes (without total count)
-List the coupons whose attributes match the query criteria in all the campaigns of the given Application.
+List the coupons whose attributes match the query criteria in all the
+campaigns of the given Application.
-The match is successful if all the attributes of the request are found in a coupon,
-even if the coupon has more attributes that are not present on the request.
+The match is successful if all the attributes of the request are found in a
+coupon, even if the coupon has more attributes that are not present on the request.
-**Note:** The total count is not included in the response.
+> [!note] The total count is not included in the response.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17067,18 +14978,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17143,7 +15042,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17163,19 +15062,16 @@ Name | Type | Description | Notes
List coupons that match the given attributes in campaign (without total count)
-List the coupons whose attributes match the query criteria
-in the given campaign.
+List the coupons whose attributes match the query criteria in the given campaign.
-The match is successful if all the attributes of the request are found in a coupon,
-even if the coupon has more attributes that are not present on the request.
+The match is successful if all the attributes of the request are found in a
+coupon, even if the coupon has more attributes that are not present on the request.
-**Note:** The total count is not included in the response.
+> [!note] The total count is not included in the response.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17195,18 +15091,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17271,7 +15155,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17295,8 +15179,6 @@ Fetch a summary of all store budget information for a given campaign.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17316,18 +15198,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17366,7 +15236,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17389,18 +15259,18 @@ Name | Type | Description | Notes
Transfer card data
-Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card.
-
-**Important:**
+Transfer loyalty card data, such as linked customers, loyalty balances and
+transactions, from a given loyalty card to a new, automatically created
+loyalty card.
-- The original card is automatically blocked once the new card is created, and it cannot be activated again.
-- The default status of the new card is _active_.
+> [!important] **Note**
+> - The original card is automatically blocked once the new card is created,
+ and it cannot be activated again.
+> - The default status of the new card is _active_.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17420,18 +15290,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17470,7 +15328,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17497,8 +15355,6 @@ Edit the description of a given account-level collection and enable or disable t
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17519,18 +15375,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17541,7 +15385,7 @@ configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
with talon_one.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = talon_one.ManagementApi(api_client)
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.
update_collection = talon_one.UpdateCollection() # UpdateCollection | body
try:
@@ -17560,7 +15404,7 @@ with talon_one.ApiClient(configuration) as api_client:
Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. |
**update_collection** | [**UpdateCollection**](UpdateCollection.md)| body |
### Return type
@@ -17569,7 +15413,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17596,8 +15440,6 @@ Update the details of a specific achievement.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17618,18 +15460,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17672,7 +15502,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17700,8 +15530,6 @@ Updates an existing additional cost. Once created, the only property of an addit
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17722,18 +15550,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17772,7 +15588,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17801,8 +15617,6 @@ update any relevant integrations and rules to use the new attribute.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17823,18 +15637,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17873,7 +15675,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17895,13 +15697,13 @@ Update campaign
Update the given campaign.
-**Important:** You cannot use this endpoint to update campaigns if [campaign staging and revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) is enabled for your Application.
+> [!important] You cannot use this endpoint to update campaigns if [campaign staging and
+> revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions)
+> is enabled for your Application.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -17922,18 +15724,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -17974,7 +15764,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -17998,8 +15788,6 @@ Edit the description of a given campaign-level collection.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18020,18 +15808,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18044,7 +15820,7 @@ with talon_one.ApiClient(configuration) as api_client:
api_instance = talon_one.ManagementApi(api_client)
application_id = 56 # int | The ID of the Application. It is displayed in your Talon.One deployment URL.
campaign_id = 56 # int | The ID of the campaign. It is displayed in your Talon.One deployment URL.
- collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.
+ collection_id = 56 # int | The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.
update_campaign_collection = talon_one.UpdateCampaignCollection() # UpdateCampaignCollection | body
try:
@@ -18065,7 +15841,7 @@ Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
**application_id** | **int**| The ID of the Application. It is displayed in your Talon.One deployment URL. |
**campaign_id** | **int**| The ID of the campaign. It is displayed in your Talon.One deployment URL. |
- **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. |
+ **collection_id** | **int**| The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. |
**update_campaign_collection** | [**UpdateCampaignCollection**](UpdateCampaignCollection.md)| body |
### Return type
@@ -18074,7 +15850,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18097,18 +15873,13 @@ Update coupon
Update the specified coupon.
-
-
Important
-
-
With this PUT endpoint, if you do not explicitly set a value for the startDate, expiryDate, and recipientIntegrationId properties in your request, it is automatically set to null.
-
-
+> [!note]
+> With this `PUT` endpoint, if you do not explicitly set a value for the `startDate`, `expiryDate`,
+> and `recipientIntegrationId` properties in your request, it is automatically set to `null`.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18129,18 +15900,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18183,7 +15942,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18204,27 +15963,20 @@ Name | Type | Description | Notes
Update coupons
Update all coupons or a specific batch of coupons in the given campaign.
-You can find the `batchId` on the **Coupons** page of your campaign
-in the Campaign Manager, or you can use [List coupons](#operation/getCouponsWithoutTotalCount).
-
-
Important
+You can find the `batchId` on the **Coupons** page of your campaign in the
+Campaign Manager, or you can use [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
-
- - Only send sequential requests to this endpoint.
- - Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team.
- - With this
PUT endpoint, if you do not explicitly set a value for the startDate and expiryDate properties in your request, it is automatically set to null.
-
+> [!note] **Note**
+> - Only send sequential requests to this endpoint.
+> - Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team.
+> - With this `PUT` endpoint, if you do not explicitly set a value for the `startDate` and `expiryDate` properties in your request, it is automatically set to `null`.
-
-
-To update a specific coupon, use [Update coupon](#operation/updateCoupon).
+To update a specific coupon, use [Update coupon](#tag/Coupons/operation/updateCoupon).
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18244,18 +15996,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18294,7 +16034,7 @@ void (empty response body)
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18318,8 +16058,6 @@ Update the details of a specific loyalty card. You can set the card's status to
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18340,18 +16078,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18392,7 +16118,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18419,8 +16145,6 @@ Update the specified referral.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18441,18 +16165,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18495,7 +16207,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18519,8 +16231,6 @@ Update a specific role.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18541,18 +16251,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18591,7 +16289,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18615,8 +16313,6 @@ Update store details for a specific store ID.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18637,18 +16333,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18689,7 +16373,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
@@ -18715,8 +16399,6 @@ Update the details of a specific user.
### Example
-* Api Key Authentication (management_key):
-* Api Key Authentication (manager_auth):
* Api Key Authentication (api_key_v1):
```python
@@ -18737,18 +16419,6 @@ configuration = talon_one.Configuration(
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
-# Configure API key authorization: management_key
-configuration.api_key['management_key'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['management_key'] = 'Bearer'
-
-# Configure API key authorization: manager_auth
-configuration.api_key['manager_auth'] = os.environ["API_KEY"]
-
-# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
-# configuration.api_key_prefix['manager_auth'] = 'Bearer'
-
# Configure API key authorization: api_key_v1
configuration.api_key['api_key_v1'] = os.environ["API_KEY"]
@@ -18787,7 +16457,7 @@ Name | Type | Description | Notes
### Authorization
-[management_key](../README.md#management_key), [manager_auth](../README.md#manager_auth), [api_key_v1](../README.md#api_key_v1)
+[api_key_v1](../README.md#api_key_v1)
### HTTP request headers
diff --git a/docs/MessageLogEntries.md b/docs/MessageLogEntries.md
index abfb033..902544c 100644
--- a/docs/MessageLogEntries.md
+++ b/docs/MessageLogEntries.md
@@ -5,7 +5,7 @@
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**next_cursor** | **bytearray** | The next value in the database. **Note:** If this value is not present, it means that there are no more values in the database for this combination of request parameters. | [optional]
+**next_cursor** | **bytes** | The next value in the database. **Note:** If this value is not present, it means that there are no more values in the database for this combination of request parameters. | [optional]
**data** | [**List[MessageLogEntry]**](MessageLogEntry.md) | List of message logs. |
## Example
diff --git a/docs/MessageLogRequest.md b/docs/MessageLogRequest.md
index 6d9e9ef..249c7e0 100644
--- a/docs/MessageLogRequest.md
+++ b/docs/MessageLogRequest.md
@@ -7,7 +7,7 @@ Details of the request.
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**created_at** | **datetime** | Timestamp when the request was made. |
-**request** | **bytearray** | Raw request data. |
+**request** | **bytes** | Raw request data. |
## Example
diff --git a/docs/MessageLogResponse.md b/docs/MessageLogResponse.md
index 9066125..dba51f6 100644
--- a/docs/MessageLogResponse.md
+++ b/docs/MessageLogResponse.md
@@ -7,7 +7,7 @@ Details of the response.
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**created_at** | **datetime** | Timestamp when the response was received. | [optional]
-**response** | **bytearray** | Raw response data. | [optional]
+**response** | **bytes** | Raw response data. | [optional]
**status** | **int** | HTTP status code of the response. | [optional]
## Example
diff --git a/docs/MultipleCustomerProfileIntegrationRequestItem.md b/docs/MultipleCustomerProfileIntegrationRequestItem.md
index 32760b8..385dd16 100644
--- a/docs/MultipleCustomerProfileIntegrationRequestItem.md
+++ b/docs/MultipleCustomerProfileIntegrationRequestItem.md
@@ -5,8 +5,8 @@
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
-**integration_id** | **str** | The identifier of this profile, set by your integration layer. It must be unique within the account. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2). |
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
+**integration_id** | **str** | The identifier of this profile, set by your integration layer. It must be unique within the account. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). |
## Example
diff --git a/docs/NewCampaign.md b/docs/NewCampaign.md
index b160f17..a37a79b 100644
--- a/docs/NewCampaign.md
+++ b/docs/NewCampaign.md
@@ -11,7 +11,7 @@ Name | Type | Description | Notes
**end_time** | **datetime** | Timestamp when the campaign will become inactive. | [optional]
**attributes** | **object** | Arbitrary properties associated with this campaign. | [optional]
**state** | **str** | A disabled or archived campaign is not evaluated for rules or coupons. | [default to 'enabled']
-**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
+**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
**tags** | **List[str]** | A list of tags for the campaign. |
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. | [optional]
**features** | **List[str]** | The features enabled in this campaign. |
@@ -21,6 +21,7 @@ Name | Type | Description | Notes
**campaign_groups** | **List[int]** | The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. | [optional]
**type** | **str** | The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. | [optional] [default to 'advanced']
**linked_store_ids** | **List[int]** | A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
**evaluation_group_id** | **int** | The ID of the campaign evaluation group the campaign belongs to. | [optional]
## Example
diff --git a/docs/NewCoupons.md b/docs/NewCoupons.md
index ff99996..bb0c3ff 100644
--- a/docs/NewCoupons.md
+++ b/docs/NewCoupons.md
@@ -12,7 +12,7 @@ Name | Type | Description | Notes
**expiry_date** | **datetime** | Expiration date of the coupon. Coupon never expires if this is omitted. | [optional]
**limits** | [**List[LimitConfig]**](LimitConfig.md) | Limits configuration for a coupon. These limits will override the limits set from the campaign. **Note:** Only usable when creating a single coupon which is not tied to a specific recipient. Only per-profile limits are allowed to be configured. | [optional]
**number_of_coupons** | **int** | The number of new coupon codes to generate for the campaign. Must be at least 1. |
-**unique_prefix** | **str** | **DEPRECATED** To create more than 20,000 coupons in one request, use [Create coupons asynchronously](https://docs.talon.one/management-api#operation/createCouponsAsync) endpoint. | [optional]
+**unique_prefix** | **str** | **DEPRECATED** To create more than 20,000 coupons in one request, use [Create coupons asynchronously](https://docs.talon.one/management-api#tag/Coupons/operation/createCouponsAsync) endpoint. | [optional]
**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
**recipient_integration_id** | **str** | The integration ID for this coupon's beneficiary's profile. | [optional]
**valid_characters** | **List[str]** | List of characters used to generate the random parts of a code. By default, the list of characters is equivalent to the `[A-Z, 0-9]` regular expression. | [optional]
diff --git a/docs/NewCustomerProfile.md b/docs/NewCustomerProfile.md
index 69184b7..cc63876 100644
--- a/docs/NewCustomerProfile.md
+++ b/docs/NewCustomerProfile.md
@@ -5,7 +5,7 @@
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
-**attributes** | **object** | Arbitrary properties associated with this item. | [optional]
+**attributes** | **Dict[str, object]** | Arbitrary properties associated with this item. | [optional]
## Example
diff --git a/docs/NewCustomerSessionV2.md b/docs/NewCustomerSessionV2.md
index 6f79f35..0fdf708 100644
--- a/docs/NewCustomerSessionV2.md
+++ b/docs/NewCustomerSessionV2.md
@@ -17,7 +17,7 @@ Name | Type | Description | Notes
**experiment_variant_allocations** | [**List[ExperimentVariantAllocation]**](ExperimentVariantAllocation.md) | The experiment variant allocations to add to this session. | [optional]
**additional_costs** | [**Dict[str, AdditionalCost]**](AdditionalCost.md) | Use this property to set a value for the additional costs of this session, such as a shipping cost. They must be created in the Campaign Manager before you set them with this property. See [Managing additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs). | [optional]
**identifiers** | **List[str]** | Session custom identifiers that you can set limits on or use inside your rules. For example, you can use IP addresses as identifiers to potentially identify devices and limit discounts abuse in case of customers creating multiple accounts. See the [tutorial](https://docs.talon.one/docs/dev/tutorials/using-identifiers). **Important**: Ensure the session contains an identifier by the time you close it if: - You [create a unique identifier budget](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets/#budget-types) for your campaign. - Your campaign has [coupons](https://docs.talon.one/docs/product/campaigns/coupons/coupon-page-overview). - We recommend passing an anonymized (hashed) version of the identifier value. | [optional]
-**attributes** | **object** | Use this property to set a value for the attributes of your choice. Attributes represent any information to attach to your session, like the shipping city. You can use [built-in attributes](https://docs.talon.one/docs/dev/concepts/attributes#built-in-attributes) or [custom ones](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes). Custom attributes must be created in the Campaign Manager before you set them with this property. | [optional]
+**attributes** | **Dict[str, object]** | Use this property to set a value for the attributes of your choice. Attributes represent any information to attach to your session, like the shipping city. You can use [built-in attributes](https://docs.talon.one/docs/dev/concepts/attributes#built-in-attributes) or [custom ones](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes). Custom attributes must be created in the Campaign Manager before you set them with this property. | [optional]
## Example
diff --git a/docs/NewRevisionVersion.md b/docs/NewRevisionVersion.md
index 457b6c1..2d752bd 100644
--- a/docs/NewRevisionVersion.md
+++ b/docs/NewRevisionVersion.md
@@ -17,6 +17,7 @@ Name | Type | Description | Notes
**limits** | [**List[LimitConfig]**](LimitConfig.md) | The set of limits that will operate for this campaign version. | [optional]
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. | [optional]
**features** | **List[str]** | A list of features for the campaign. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
## Example
diff --git a/docs/RevisionVersion.md b/docs/RevisionVersion.md
index 8a3243b..e4efa85 100644
--- a/docs/RevisionVersion.md
+++ b/docs/RevisionVersion.md
@@ -18,6 +18,7 @@ Name | Type | Description | Notes
**limits** | [**List[LimitConfig]**](LimitConfig.md) | The set of limits that will operate for this campaign version. | [optional]
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. | [optional]
**features** | **List[str]** | A list of features for the campaign. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
**account_id** | **int** | |
**application_id** | **int** | |
**campaign_id** | **int** | |
diff --git a/docs/RoleV2ApplicationDetails.md b/docs/RoleV2ApplicationDetails.md
index 43c8c3f..fcfd503 100644
--- a/docs/RoleV2ApplicationDetails.md
+++ b/docs/RoleV2ApplicationDetails.md
@@ -9,6 +9,7 @@ Name | Type | Description | Notes
**campaign** | **str** | Name of the campaign-related permission set for the given Application. | [optional]
**draft_campaign** | **str** | Name of the draft campaign-related permission set for the given Application. | [optional]
**tools** | **str** | Name of the tools-related permission set. | [optional]
+**thresholds** | [**RolesV2Thresholds**](RolesV2Thresholds.md) | Support user limits for actions that require admin approval within the given application. | [optional]
## Example
diff --git a/docs/RolesV2Thresholds.md b/docs/RolesV2Thresholds.md
new file mode 100644
index 0000000..53531f9
--- /dev/null
+++ b/docs/RolesV2Thresholds.md
@@ -0,0 +1,29 @@
+# RolesV2Thresholds
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**loyalty_points_limit** | **int** | Maximum number of loyalty points a support user can award without approval. | [optional]
+
+## Example
+
+```python
+from talon_one.models.roles_v2_thresholds import RolesV2Thresholds
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of RolesV2Thresholds from a JSON string
+roles_v2_thresholds_instance = RolesV2Thresholds.from_json(json)
+# print the JSON string representation of the object
+print(RolesV2Thresholds.to_json())
+
+# convert the object into a dict
+roles_v2_thresholds_dict = roles_v2_thresholds_instance.to_dict()
+# create an instance of RolesV2Thresholds from a dict
+roles_v2_thresholds_from_dict = RolesV2Thresholds.from_dict(roles_v2_thresholds_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/RuleMetadata.md b/docs/RuleMetadata.md
new file mode 100644
index 0000000..f76f4c7
--- /dev/null
+++ b/docs/RuleMetadata.md
@@ -0,0 +1,32 @@
+# RuleMetadata
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**title** | **str** | A short description of the rule. |
+**display_name** | **str** | A customer-facing name used to identify the reward defined within the rule. | [optional]
+**display_description** | **str** | A customer-facing description of the reward defined in the rule. For example, this property can contain details about eligibility requirements, reward timelines, or terms and conditions. | [optional]
+**related_data** | **str** | Data related to the reward, such as a vendor name, an image URL, or a content management system (CMS) ID. | [optional]
+
+## Example
+
+```python
+from talon_one.models.rule_metadata import RuleMetadata
+
+# TODO update the JSON string below
+json = "{}"
+# create an instance of RuleMetadata from a JSON string
+rule_metadata_instance = RuleMetadata.from_json(json)
+# print the JSON string representation of the object
+print(RuleMetadata.to_json())
+
+# convert the object into a dict
+rule_metadata_dict = rule_metadata_instance.to_dict()
+# create an instance of RuleMetadata from a dict
+rule_metadata_from_dict = RuleMetadata.from_dict(rule_metadata_dict)
+```
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/docs/UpdateCampaign.md b/docs/UpdateCampaign.md
index 632467a..ac389d5 100644
--- a/docs/UpdateCampaign.md
+++ b/docs/UpdateCampaign.md
@@ -11,7 +11,7 @@ Name | Type | Description | Notes
**end_time** | **datetime** | Timestamp when the campaign will become inactive. | [optional]
**attributes** | **object** | Arbitrary properties associated with this campaign. | [optional]
**state** | **str** | A disabled or archived campaign is not evaluated for rules or coupons. | [optional] [default to 'enabled']
-**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
+**active_ruleset_id** | **int** | [ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. | [optional]
**tags** | **List[str]** | A list of tags for the campaign. |
**reevaluate_on_return** | **bool** | Indicates whether this campaign should be reevaluated when a customer returns an item. | [optional]
**features** | **List[str]** | A list of features for the campaign. |
@@ -21,7 +21,8 @@ Name | Type | Description | Notes
**campaign_groups** | **List[int]** | The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/account-settings/managing-campaign-groups) this campaign belongs to. | [optional]
**evaluation_group_id** | **int** | The ID of the campaign evaluation group the campaign belongs to. | [optional]
**type** | **str** | The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. | [optional] [default to 'advanced']
-**linked_store_ids** | **List[int]** | A list of store IDs that you want to link to the campaign. **Note:** - Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. - If you linked stores to the campaign by uploading a CSV file, you cannot use this property and it should be empty. - Use of this property is limited to 50 stores. To link more than 50 stores, upload them via a CSV file. | [optional]
+**linked_store_ids** | **List[int]** | A list of store IDs that you want to link to the campaign. > [!note] **Note** > - Campaigns with linked store IDs will only be evaluated when there is a > [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) > that references a linked store. > - If you linked stores to the campaign by uploading a CSV file, you cannot use this property and it should be empty. > - Use of this property is limited to 50 stores. To link more than 50 stores, upload them via a CSV file. | [optional]
+**coupon_attributes** | **object** | Arbitrary properties associated with coupons in this campaign. | [optional]
## Example
diff --git a/pyproject.toml b/pyproject.toml
index 02e5836..2158347 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
[project]
name = "talon-one-sdk"
-version = "26.06.0"
+version = "26.07.0"
description = "Talon.One API"
authors = [
{name = "OpenAPI Generator Community",email = "team@openapitools.org"},
diff --git a/requirements.txt b/requirements.txt
index 6cbb2b9..9e2d67a 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,4 +1,4 @@
urllib3 >= 2.1.0, < 3.0.0
python_dateutil >= 2.8.2
-pydantic >= 2
+pydantic >= 2.11
typing-extensions >= 4.7.1
diff --git a/setup.py b/setup.py
index 9f8db8f..5100753 100644
--- a/setup.py
+++ b/setup.py
@@ -11,7 +11,7 @@
# http://pypi.python.org/pypi/setuptools
NAME = "talon-one-sdk"
-VERSION = "26.06.0"
+VERSION = "26.07.0"
# Get the long description from the README.md file
here = pathlib.Path(__file__).parent.resolve()
diff --git a/talon_one/__init__.py b/talon_one/__init__.py
index addbba8..4284007 100644
--- a/talon_one/__init__.py
+++ b/talon_one/__init__.py
@@ -5,7 +5,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -14,7 +14,7 @@
""" # noqa: E501
-__version__ = "26.06.0"
+__version__ = "26.07.0"
# Define package exports
__all__ = [
@@ -241,6 +241,9 @@
"Effect",
"EffectEntity",
"EmailEntity",
+ "EmbeddedAnalyticsConfiguration",
+ "EmbeddedAnalyticsConfigurationDashboards",
+ "EmbeddedDashboardConfiguration",
"Endpoint",
"Entity",
"EntityWithTalangVisibleID",
@@ -259,6 +262,9 @@
"ExperimentCampaignCopy",
"ExperimentCopy",
"ExperimentCopyExperiment",
+ "ExperimentListResults",
+ "ExperimentListResultsRequest",
+ "ExperimentResult",
"ExperimentResults",
"ExperimentVariant",
"ExperimentVariantAllocation",
@@ -337,6 +343,8 @@
"GetUsers200Response",
"GetWebhooks200Response",
"Giveaway",
+ "GiveawayPoolNotification",
+ "GiveawayPoolNotificationData",
"GiveawaysPool",
"HiddenConditionsEffects",
"History",
@@ -578,6 +586,7 @@
"RoleV2Permissions",
"RoleV2Readonly",
"RoleV2RolesGroup",
+ "RolesV2Thresholds",
"RollbackAddedLoyaltyPointsEffectProps",
"RollbackCouponEffectProps",
"RollbackDeductedLoyaltyPointsEffectProps",
@@ -586,6 +595,7 @@
"RollbackReferralEffectProps",
"Rule",
"RuleFailureReason",
+ "RuleMetadata",
"Ruleset",
"SSOConfig",
"SamlConnection",
@@ -933,6 +943,9 @@
from talon_one.models.effect import Effect as Effect
from talon_one.models.effect_entity import EffectEntity as EffectEntity
from talon_one.models.email_entity import EmailEntity as EmailEntity
+from talon_one.models.embedded_analytics_configuration import EmbeddedAnalyticsConfiguration as EmbeddedAnalyticsConfiguration
+from talon_one.models.embedded_analytics_configuration_dashboards import EmbeddedAnalyticsConfigurationDashboards as EmbeddedAnalyticsConfigurationDashboards
+from talon_one.models.embedded_dashboard_configuration import EmbeddedDashboardConfiguration as EmbeddedDashboardConfiguration
from talon_one.models.endpoint import Endpoint as Endpoint
from talon_one.models.entity import Entity as Entity
from talon_one.models.entity_with_talang_visible_id import EntityWithTalangVisibleID as EntityWithTalangVisibleID
@@ -951,6 +964,9 @@
from talon_one.models.experiment_campaign_copy import ExperimentCampaignCopy as ExperimentCampaignCopy
from talon_one.models.experiment_copy import ExperimentCopy as ExperimentCopy
from talon_one.models.experiment_copy_experiment import ExperimentCopyExperiment as ExperimentCopyExperiment
+from talon_one.models.experiment_list_results import ExperimentListResults as ExperimentListResults
+from talon_one.models.experiment_list_results_request import ExperimentListResultsRequest as ExperimentListResultsRequest
+from talon_one.models.experiment_result import ExperimentResult as ExperimentResult
from talon_one.models.experiment_results import ExperimentResults as ExperimentResults
from talon_one.models.experiment_variant import ExperimentVariant as ExperimentVariant
from talon_one.models.experiment_variant_allocation import ExperimentVariantAllocation as ExperimentVariantAllocation
@@ -1029,6 +1045,8 @@
from talon_one.models.get_users200_response import GetUsers200Response as GetUsers200Response
from talon_one.models.get_webhooks200_response import GetWebhooks200Response as GetWebhooks200Response
from talon_one.models.giveaway import Giveaway as Giveaway
+from talon_one.models.giveaway_pool_notification import GiveawayPoolNotification as GiveawayPoolNotification
+from talon_one.models.giveaway_pool_notification_data import GiveawayPoolNotificationData as GiveawayPoolNotificationData
from talon_one.models.giveaways_pool import GiveawaysPool as GiveawaysPool
from talon_one.models.hidden_conditions_effects import HiddenConditionsEffects as HiddenConditionsEffects
from talon_one.models.history import History as History
@@ -1270,6 +1288,7 @@
from talon_one.models.role_v2_permissions import RoleV2Permissions as RoleV2Permissions
from talon_one.models.role_v2_readonly import RoleV2Readonly as RoleV2Readonly
from talon_one.models.role_v2_roles_group import RoleV2RolesGroup as RoleV2RolesGroup
+from talon_one.models.roles_v2_thresholds import RolesV2Thresholds as RolesV2Thresholds
from talon_one.models.rollback_added_loyalty_points_effect_props import RollbackAddedLoyaltyPointsEffectProps as RollbackAddedLoyaltyPointsEffectProps
from talon_one.models.rollback_coupon_effect_props import RollbackCouponEffectProps as RollbackCouponEffectProps
from talon_one.models.rollback_deducted_loyalty_points_effect_props import RollbackDeductedLoyaltyPointsEffectProps as RollbackDeductedLoyaltyPointsEffectProps
@@ -1278,6 +1297,7 @@
from talon_one.models.rollback_referral_effect_props import RollbackReferralEffectProps as RollbackReferralEffectProps
from talon_one.models.rule import Rule as Rule
from talon_one.models.rule_failure_reason import RuleFailureReason as RuleFailureReason
+from talon_one.models.rule_metadata import RuleMetadata as RuleMetadata
from talon_one.models.ruleset import Ruleset as Ruleset
from talon_one.models.sso_config import SSOConfig as SSOConfig
from talon_one.models.saml_connection import SamlConnection as SamlConnection
diff --git a/talon_one/api/integration_api.py b/talon_one/api/integration_api.py
index ec2f12e..915cc5d 100644
--- a/talon_one/api/integration_api.py
+++ b/talon_one/api/integration_api.py
@@ -1,7 +1,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -56,8 +56,6 @@
from talon_one.models.new_audience import NewAudience
from talon_one.models.new_referral import NewReferral
from talon_one.models.new_referrals_for_multiple_advocates import NewReferralsForMultipleAdvocates
-from talon_one.models.price_history_request import PriceHistoryRequest
-from talon_one.models.price_history_response import PriceHistoryResponse
from talon_one.models.referral import Referral
from talon_one.models.reopen_session_response import ReopenSessionResponse
from talon_one.models.return_integration_request import ReturnIntegrationRequest
@@ -632,8 +630,6 @@ def _best_prior_price_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -674,7 +670,7 @@ def create_audience_v2(
) -> Audience:
"""Create audience
- Create an audience. The audience can be created directly from scratch or can come from third party platforms. **Note:** Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch: 1. Only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
+ Create an audience. The audience can be created directly from scratch or can come from third party platforms. > [!note] Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch, only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
:param new_audience: body (required)
:type new_audience: NewAudience
@@ -744,7 +740,7 @@ def create_audience_v2_with_http_info(
) -> ApiResponse[Audience]:
"""Create audience
- Create an audience. The audience can be created directly from scratch or can come from third party platforms. **Note:** Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch: 1. Only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
+ Create an audience. The audience can be created directly from scratch or can come from third party platforms. > [!note] Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch, only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
:param new_audience: body (required)
:type new_audience: NewAudience
@@ -814,7 +810,7 @@ def create_audience_v2_without_preload_content(
) -> RESTResponseType:
"""Create audience
- Create an audience. The audience can be created directly from scratch or can come from third party platforms. **Note:** Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch: 1. Only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
+ Create an audience. The audience can be created directly from scratch or can come from third party platforms. > [!note] Audiences can also be created from scratch via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/creating-audiences). To create an audience from an existing audience from a [technology partner](https://docs.talon.one/docs/dev/technology-partners/overview): 1. Set the `integration` property to `mparticle`, `segment` etc., depending on a third-party platform. 1. Set `integrationId` to the ID of this audience in a third-party platform. To create an audience from an existing audience in another platform: 1. Do not use the `integration` property. 1. Set `integrationId` to the ID of this audience in the 3rd-party platform. To create an audience from scratch, only set the `name` property. Once you create your first audience, audience-specific rule conditions are enabled in the Rule Builder.
:param new_audience: body (required)
:type new_audience: NewAudience
@@ -941,7 +937,7 @@ def _create_audience_v2_serialize(
@validate_call
def create_coupon_reservation(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -958,9 +954,9 @@ def create_coupon_reservation(
) -> Coupon:
"""Create coupon reservation
- Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. **Note:** - If the **Reservation mandatory** option was selected when creating the specified coupon, the endpoint creates a **hard** reservation, meaning only users who have this coupon code reserved can redeem it. Otherwise, the endpoint creates a **soft** reservation, meaning the coupon is associated with the specified customer profiles (they show up when using the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint), but any user can redeem it. This can be useful, for example, to display a _coupon wallet_ for customers when they visit your store. - If the **Coupon visibility** option was selected when creating the specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code will be returned for all customer profiles in the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint. - This endpoint overrides the coupon reservation limit set when [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
+ Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. > [!note] **Note** > - If the **Reservation mandatory** option was selected when creating the > specified coupon, the endpoint creates a **hard** reservation, meaning only users who have > this coupon code reserved can redeem it. > > Otherwise, the endpoint creates a **soft** reservation, meaning the coupon > is associated with the specified customer profiles (they show up when using > the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) > endpoint), but any user can redeem it. > > This can be useful, for example, to display a _coupon wallet_ for customers > when they visit your store. > - If the **Coupon visibility** option was selected when creating the > specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code > will be returned for all customer profiles in the [List customer > data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) endpoint. > - This endpoint overrides the coupon reservation limit set when > [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -1015,7 +1011,7 @@ def create_coupon_reservation(
@validate_call
def create_coupon_reservation_with_http_info(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -1032,9 +1028,9 @@ def create_coupon_reservation_with_http_info(
) -> ApiResponse[Coupon]:
"""Create coupon reservation
- Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. **Note:** - If the **Reservation mandatory** option was selected when creating the specified coupon, the endpoint creates a **hard** reservation, meaning only users who have this coupon code reserved can redeem it. Otherwise, the endpoint creates a **soft** reservation, meaning the coupon is associated with the specified customer profiles (they show up when using the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint), but any user can redeem it. This can be useful, for example, to display a _coupon wallet_ for customers when they visit your store. - If the **Coupon visibility** option was selected when creating the specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code will be returned for all customer profiles in the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint. - This endpoint overrides the coupon reservation limit set when [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
+ Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. > [!note] **Note** > - If the **Reservation mandatory** option was selected when creating the > specified coupon, the endpoint creates a **hard** reservation, meaning only users who have > this coupon code reserved can redeem it. > > Otherwise, the endpoint creates a **soft** reservation, meaning the coupon > is associated with the specified customer profiles (they show up when using > the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) > endpoint), but any user can redeem it. > > This can be useful, for example, to display a _coupon wallet_ for customers > when they visit your store. > - If the **Coupon visibility** option was selected when creating the > specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code > will be returned for all customer profiles in the [List customer > data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) endpoint. > - This endpoint overrides the coupon reservation limit set when > [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -1089,7 +1085,7 @@ def create_coupon_reservation_with_http_info(
@validate_call
def create_coupon_reservation_without_preload_content(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -1106,9 +1102,9 @@ def create_coupon_reservation_without_preload_content(
) -> RESTResponseType:
"""Create coupon reservation
- Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. **Note:** - If the **Reservation mandatory** option was selected when creating the specified coupon, the endpoint creates a **hard** reservation, meaning only users who have this coupon code reserved can redeem it. Otherwise, the endpoint creates a **soft** reservation, meaning the coupon is associated with the specified customer profiles (they show up when using the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint), but any user can redeem it. This can be useful, for example, to display a _coupon wallet_ for customers when they visit your store. - If the **Coupon visibility** option was selected when creating the specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code will be returned for all customer profiles in the [List customer data](https://docs.talon.one/integration-api#operation/getCustomerInventory) endpoint. - This endpoint overrides the coupon reservation limit set when [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
+ Create a coupon reservation for the specified customer profiles on the specified coupon. You can also create a reservation via the Campaign Manager using the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect. > [!note] **Note** > - If the **Reservation mandatory** option was selected when creating the > specified coupon, the endpoint creates a **hard** reservation, meaning only users who have > this coupon code reserved can redeem it. > > Otherwise, the endpoint creates a **soft** reservation, meaning the coupon > is associated with the specified customer profiles (they show up when using > the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) > endpoint), but any user can redeem it. > > This can be useful, for example, to display a _coupon wallet_ for customers > when they visit your store. > - If the **Coupon visibility** option was selected when creating the > specified coupon, the coupon code is implicitly soft-reserved for all customers, and the code > will be returned for all customer profiles in the [List customer > data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory) endpoint. > - This endpoint overrides the coupon reservation limit set when > [the coupon is created](https://docs.talon.one/docs/product/campaigns/coupons/creating-coupons). To ensure that coupons cannot be reserved after the reservation limit is reached, use the [Create coupon code reservation](https://docs.talon.one/docs/product/rules/effects/using-effects#reserving-a-coupon-code) effect in the Rule Builder and the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. To delete a reservation, use the [Delete reservation](https://docs.talon.one/integration-api#tag/Coupons/operation/deleteCouponReservation) endpoint.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -1255,7 +1251,7 @@ def create_referral(
) -> Referral:
"""Create referral code for an advocate
- Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referral: body (required)
:type new_referral: NewReferral
@@ -1324,7 +1320,7 @@ def create_referral_with_http_info(
) -> ApiResponse[Referral]:
"""Create referral code for an advocate
- Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referral: body (required)
:type new_referral: NewReferral
@@ -1393,7 +1389,7 @@ def create_referral_without_preload_content(
) -> RESTResponseType:
"""Create referral code for an advocate
- Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates a referral code for an advocate. The code will be valid for the referral campaign for which is created, indicated in the `campaignId` parameter, and will be associated with the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referral: body (required)
:type new_referral: NewReferral
@@ -1536,7 +1532,7 @@ def create_referrals_for_multiple_advocates(
) -> CreateReferralsForMultipleAdvocates201Response:
"""Create referral codes for multiple advocates
- Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referrals_for_multiple_advocates: body (required)
:type new_referrals_for_multiple_advocates: NewReferralsForMultipleAdvocates
@@ -1610,7 +1606,7 @@ def create_referrals_for_multiple_advocates_with_http_info(
) -> ApiResponse[CreateReferralsForMultipleAdvocates201Response]:
"""Create referral codes for multiple advocates
- Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referrals_for_multiple_advocates: body (required)
:type new_referrals_for_multiple_advocates: NewReferralsForMultipleAdvocates
@@ -1684,7 +1680,7 @@ def create_referrals_for_multiple_advocates_without_preload_content(
) -> RESTResponseType:
"""Create referral codes for multiple advocates
- Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. **Note:** Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) set are ignored when you use this endpoint.
+ Creates unique referral codes for multiple advocates. The code will be valid for the referral campaign for which it is created, indicated in the `campaignId` parameter, and one referral code will be associated with one advocate using the profile specified in the `advocateProfileIntegrationId` parameter as the advocate's profile. > [!note] Any [referral limits](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets#referral-limits) > set are ignored when you use this endpoint.
:param new_referrals_for_multiple_advocates: body (required)
:type new_referrals_for_multiple_advocates: NewReferralsForMultipleAdvocates
@@ -2102,7 +2098,7 @@ def delete_audience_v2(
) -> None:
"""Delete audience
- Delete an audience created by a third-party integration. **Warning:** This endpoint also removes any associations recorded between a customer profile and this audience. **Note:** Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
+ Delete an audience created by a third-party integration. > [!warning] This endpoint also removes any associations recorded between a customer profile and this audience. > [!note] Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -2172,7 +2168,7 @@ def delete_audience_v2_with_http_info(
) -> ApiResponse[None]:
"""Delete audience
- Delete an audience created by a third-party integration. **Warning:** This endpoint also removes any associations recorded between a customer profile and this audience. **Note:** Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
+ Delete an audience created by a third-party integration. > [!warning] This endpoint also removes any associations recorded between a customer profile and this audience. > [!note] Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -2242,7 +2238,7 @@ def delete_audience_v2_without_preload_content(
) -> RESTResponseType:
"""Delete audience
- Delete an audience created by a third-party integration. **Warning:** This endpoint also removes any associations recorded between a customer profile and this audience. **Note:** Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
+ Delete an audience created by a third-party integration. > [!warning] This endpoint also removes any associations recorded between a customer profile and this audience. > [!note] Audiences can also be deleted via the Campaign Manager. See the [docs](https://docs.talon.one/docs/product/audiences/managing-audiences#deleting-an-audience).
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -2356,7 +2352,7 @@ def _delete_audience_v2_serialize(
@validate_call
def delete_coupon_reservation(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -2375,7 +2371,7 @@ def delete_coupon_reservation(
Remove all the coupon reservations from the provided customer profile integration IDs and the provided coupon code.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -2430,7 +2426,7 @@ def delete_coupon_reservation(
@validate_call
def delete_coupon_reservation_with_http_info(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -2449,7 +2445,7 @@ def delete_coupon_reservation_with_http_info(
Remove all the coupon reservations from the provided customer profile integration IDs and the provided coupon code.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -2504,7 +2500,7 @@ def delete_coupon_reservation_with_http_info(
@validate_call
def delete_coupon_reservation_without_preload_content(
self,
- coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
+ coupon_value: Annotated[StrictStr, Field(description="The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. ")],
coupon_reservations: Annotated[CouponReservations, Field(description="body")],
_request_timeout: Union[
None,
@@ -2523,7 +2519,7 @@ def delete_coupon_reservation_without_preload_content(
Remove all the coupon reservations from the provided customer profile integration IDs and the provided coupon code.
- :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
+ :param coupon_value: The code of the coupon. **Important:** The coupon code requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `SUMMER25%OFF` as `SUMMER25%25OFF`. (required)
:type coupon_value: str
:param coupon_reservations: body (required)
:type coupon_reservations: CouponReservations
@@ -2654,7 +2650,7 @@ def _delete_coupon_reservation_serialize(
@validate_call
def delete_customer_data(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -2670,9 +2666,9 @@ def delete_customer_data(
) -> None:
"""Delete customer's personal data
- Delete all attributes on the customer profile and on entities that reference this customer profile. **Important:** - Customer data is deleted from all Applications in the [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) that the API key belongs to. For example, if you use this endpoint with an API key that belongs to a sandbox Application, customer data will be deleted from all sandbox Applications. This is because customer data is shared between Applications from the same environment. - To preserve performance, we recommend avoiding deleting customer data during peak-traffic hours.
+ Delete all attributes on the customer profile and on entities that reference this customer profile. > [!warning] **Warning** > - Customer data is deleted from all Applications in the > [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) > that the API key belongs to. For example, if you use this endpoint with an API key that belongs > to a sandbox Application, customer data will be deleted from all sandbox Applications. > This is because customer data is shared between Applications from the same environment. > - To preserve performance, we recommend avoiding deleting customer data > during peak-traffic hours.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -2723,7 +2719,7 @@ def delete_customer_data(
@validate_call
def delete_customer_data_with_http_info(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -2739,9 +2735,9 @@ def delete_customer_data_with_http_info(
) -> ApiResponse[None]:
"""Delete customer's personal data
- Delete all attributes on the customer profile and on entities that reference this customer profile. **Important:** - Customer data is deleted from all Applications in the [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) that the API key belongs to. For example, if you use this endpoint with an API key that belongs to a sandbox Application, customer data will be deleted from all sandbox Applications. This is because customer data is shared between Applications from the same environment. - To preserve performance, we recommend avoiding deleting customer data during peak-traffic hours.
+ Delete all attributes on the customer profile and on entities that reference this customer profile. > [!warning] **Warning** > - Customer data is deleted from all Applications in the > [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) > that the API key belongs to. For example, if you use this endpoint with an API key that belongs > to a sandbox Application, customer data will be deleted from all sandbox Applications. > This is because customer data is shared between Applications from the same environment. > - To preserve performance, we recommend avoiding deleting customer data > during peak-traffic hours.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -2792,7 +2788,7 @@ def delete_customer_data_with_http_info(
@validate_call
def delete_customer_data_without_preload_content(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -2808,9 +2804,9 @@ def delete_customer_data_without_preload_content(
) -> RESTResponseType:
"""Delete customer's personal data
- Delete all attributes on the customer profile and on entities that reference this customer profile. **Important:** - Customer data is deleted from all Applications in the [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) that the API key belongs to. For example, if you use this endpoint with an API key that belongs to a sandbox Application, customer data will be deleted from all sandbox Applications. This is because customer data is shared between Applications from the same environment. - To preserve performance, we recommend avoiding deleting customer data during peak-traffic hours.
+ Delete all attributes on the customer profile and on entities that reference this customer profile. > [!warning] **Warning** > - Customer data is deleted from all Applications in the > [environment](https://docs.talon.one/docs/product/applications/overview#application-environments) > that the API key belongs to. For example, if you use this endpoint with an API key that belongs > to a sandbox Application, customer data will be deleted from all sandbox Applications. > This is because customer data is shared between Applications from the same environment. > - To preserve performance, we recommend avoiding deleting customer data > during peak-traffic hours.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -2922,7 +2918,7 @@ def _delete_customer_data_serialize(
def delete_loyalty_transactions_from_ledgers(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest,
_request_timeout: Union[
None,
@@ -2939,11 +2935,11 @@ def delete_loyalty_transactions_from_ledgers(
) -> None:
"""Delete customer's transactions from loyalty ledgers
- Delete a customer's transactions in all loyalty ledgers or a specified ledger. **Note:** To retrieve loyalty transaction logs for a specific customer in a given loyalty program, use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) endpoint.
+ Delete a customer's transactions in all loyalty ledgers or a specified ledger. > [!note] To retrieve loyalty transaction logs for a specific customer in a given loyalty program, > use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param delete_loyalty_transactions_request: (required)
:type delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest
@@ -3000,7 +2996,7 @@ def delete_loyalty_transactions_from_ledgers(
def delete_loyalty_transactions_from_ledgers_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest,
_request_timeout: Union[
None,
@@ -3017,11 +3013,11 @@ def delete_loyalty_transactions_from_ledgers_with_http_info(
) -> ApiResponse[None]:
"""Delete customer's transactions from loyalty ledgers
- Delete a customer's transactions in all loyalty ledgers or a specified ledger. **Note:** To retrieve loyalty transaction logs for a specific customer in a given loyalty program, use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) endpoint.
+ Delete a customer's transactions in all loyalty ledgers or a specified ledger. > [!note] To retrieve loyalty transaction logs for a specific customer in a given loyalty program, > use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param delete_loyalty_transactions_request: (required)
:type delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest
@@ -3078,7 +3074,7 @@ def delete_loyalty_transactions_from_ledgers_with_http_info(
def delete_loyalty_transactions_from_ledgers_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest,
_request_timeout: Union[
None,
@@ -3095,11 +3091,11 @@ def delete_loyalty_transactions_from_ledgers_without_preload_content(
) -> RESTResponseType:
"""Delete customer's transactions from loyalty ledgers
- Delete a customer's transactions in all loyalty ledgers or a specified ledger. **Note:** To retrieve loyalty transaction logs for a specific customer in a given loyalty program, use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) endpoint.
+ Delete a customer's transactions in all loyalty ledgers or a specified ledger. > [!note] To retrieve loyalty transaction logs for a specific customer in a given loyalty program, > use the [List customer's loyalty transactions](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param delete_loyalty_transactions_request: (required)
:type delete_loyalty_transactions_request: DeleteLoyaltyTransactionsRequest
@@ -3251,7 +3247,7 @@ def generate_loyalty_card(
) -> LoyaltyCard:
"""Generate loyalty card
- Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. **Note:** - The number of customer profiles linked to the loyalty card cannot exceed the loyalty program's `usersPerCardLimit`. To find the program's limit, use the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) endpoint. - If the loyalty program has a defined code format, it will be used for the loyalty card identifier.
+ Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. > [!note] **Note** > - The number of customer profiles linked to the loyalty card cannot exceed > the loyalty program's `usersPerCardLimit`. To find the program's limit, use > the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) > endpoint. > - If the loyalty program has a defined code format, it will be used for the > loyalty card identifier.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -3324,7 +3320,7 @@ def generate_loyalty_card_with_http_info(
) -> ApiResponse[LoyaltyCard]:
"""Generate loyalty card
- Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. **Note:** - The number of customer profiles linked to the loyalty card cannot exceed the loyalty program's `usersPerCardLimit`. To find the program's limit, use the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) endpoint. - If the loyalty program has a defined code format, it will be used for the loyalty card identifier.
+ Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. > [!note] **Note** > - The number of customer profiles linked to the loyalty card cannot exceed > the loyalty program's `usersPerCardLimit`. To find the program's limit, use > the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) > endpoint. > - If the loyalty program has a defined code format, it will be used for the > loyalty card identifier.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -3397,7 +3393,7 @@ def generate_loyalty_card_without_preload_content(
) -> RESTResponseType:
"""Generate loyalty card
- Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. **Note:** - The number of customer profiles linked to the loyalty card cannot exceed the loyalty program's `usersPerCardLimit`. To find the program's limit, use the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) endpoint. - If the loyalty program has a defined code format, it will be used for the loyalty card identifier.
+ Generate a loyalty card in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview). To link the card to one or more customer profiles, use the `customerProfileIds` parameter in the request body. > [!note] **Note** > - The number of customer profiles linked to the loyalty card cannot exceed > the loyalty program's `usersPerCardLimit`. To find the program's limit, use > the [Get loyalty program](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgram) > endpoint. > - If the loyalty program has a defined code format, it will be used for the > loyalty card identifier.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -4294,7 +4290,7 @@ def _get_customer_achievements_serialize(
@validate_call
def get_customer_inventory(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
profile: Annotated[Optional[StrictBool], Field(description="Set to `true` to include customer profile information in the response.")] = None,
referrals: Annotated[Optional[StrictBool], Field(description="Set to `true` to include referral information in the response.")] = None,
coupons: Annotated[Optional[StrictBool], Field(description="Set to `true` to include coupon information in the response.")] = None,
@@ -4318,7 +4314,7 @@ def get_customer_inventory(
Return the customer inventory regarding entities referencing this customer profile's `integrationId`. Typical entities returned are: customer profile information, referral codes, loyalty points, loyalty cards and reserved coupons. Reserved coupons also include redeemed coupons.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param profile: Set to `true` to include customer profile information in the response.
:type profile: bool
@@ -4387,7 +4383,7 @@ def get_customer_inventory(
@validate_call
def get_customer_inventory_with_http_info(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
profile: Annotated[Optional[StrictBool], Field(description="Set to `true` to include customer profile information in the response.")] = None,
referrals: Annotated[Optional[StrictBool], Field(description="Set to `true` to include referral information in the response.")] = None,
coupons: Annotated[Optional[StrictBool], Field(description="Set to `true` to include coupon information in the response.")] = None,
@@ -4411,7 +4407,7 @@ def get_customer_inventory_with_http_info(
Return the customer inventory regarding entities referencing this customer profile's `integrationId`. Typical entities returned are: customer profile information, referral codes, loyalty points, loyalty cards and reserved coupons. Reserved coupons also include redeemed coupons.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param profile: Set to `true` to include customer profile information in the response.
:type profile: bool
@@ -4480,7 +4476,7 @@ def get_customer_inventory_with_http_info(
@validate_call
def get_customer_inventory_without_preload_content(
self,
- integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ integration_id: Annotated[StrictStr, Field(description="The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
profile: Annotated[Optional[StrictBool], Field(description="Set to `true` to include customer profile information in the response.")] = None,
referrals: Annotated[Optional[StrictBool], Field(description="Set to `true` to include referral information in the response.")] = None,
coupons: Annotated[Optional[StrictBool], Field(description="Set to `true` to include coupon information in the response.")] = None,
@@ -4504,7 +4500,7 @@ def get_customer_inventory_without_preload_content(
Return the customer inventory regarding entities referencing this customer profile's `integrationId`. Typical entities returned are: customer profile information, referral codes, loyalty points, loyalty cards and reserved coupons. Reserved coupons also include redeemed coupons.
- :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param integration_id: The integration ID of the customer profile. You can get the `integrationId` of a profile using: - A customer session integration ID with the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. - The Management API with the [List application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type integration_id: str
:param profile: Set to `true` to include customer profile information in the response.
:type profile: bool
@@ -4663,7 +4659,7 @@ def _get_customer_inventory_serialize(
@validate_call
def get_customer_session(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -4681,7 +4677,7 @@ def get_customer_session(
Get the details of the given customer session. You can get the same data via other endpoints that also apply changes, which can help you save requests and increase performance. See: - [Update customer session](#tag/Customer-sessions/operation/updateCustomerSessionV2) - [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2)
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -4732,7 +4728,7 @@ def get_customer_session(
@validate_call
def get_customer_session_with_http_info(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -4750,7 +4746,7 @@ def get_customer_session_with_http_info(
Get the details of the given customer session. You can get the same data via other endpoints that also apply changes, which can help you save requests and increase performance. See: - [Update customer session](#tag/Customer-sessions/operation/updateCustomerSessionV2) - [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2)
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -4801,7 +4797,7 @@ def get_customer_session_with_http_info(
@validate_call
def get_customer_session_without_preload_content(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -4819,7 +4815,7 @@ def get_customer_session_without_preload_content(
Get the details of the given customer session. You can get the same data via other endpoints that also apply changes, which can help you save requests and increase performance. See: - [Update customer session](#tag/Customer-sessions/operation/updateCustomerSessionV2) - [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2)
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -4932,7 +4928,7 @@ def get_loyalty_balances(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -4951,13 +4947,13 @@ def get_loyalty_balances(
) -> LoyaltyBalancesWithTiers:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -5022,7 +5018,7 @@ def get_loyalty_balances_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -5041,13 +5037,13 @@ def get_loyalty_balances_with_http_info(
) -> ApiResponse[LoyaltyBalancesWithTiers]:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -5112,7 +5108,7 @@ def get_loyalty_balances_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -5131,13 +5127,13 @@ def get_loyalty_balances_without_preload_content(
) -> RESTResponseType:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -5294,7 +5290,7 @@ def get_loyalty_card_balances(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
_request_timeout: Union[
None,
@@ -5317,7 +5313,7 @@ def get_loyalty_card_balances(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: Filter results by one or more subledger IDs. Must be exact match.
:type subledger_id: List[str]
@@ -5376,7 +5372,7 @@ def get_loyalty_card_balances_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
_request_timeout: Union[
None,
@@ -5399,7 +5395,7 @@ def get_loyalty_card_balances_with_http_info(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: Filter results by one or more subledger IDs. Must be exact match.
:type subledger_id: List[str]
@@ -5458,7 +5454,7 @@ def get_loyalty_card_balances_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
_request_timeout: Union[
None,
@@ -5481,7 +5477,7 @@ def get_loyalty_card_balances_without_preload_content(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: Filter results by one or more subledger IDs. Must be exact match.
:type subledger_id: List[str]
@@ -6032,8 +6028,8 @@ def get_loyalty_card_transactions(
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
@@ -6064,9 +6060,9 @@ def get_loyalty_card_transactions(
:type subledger_id: List[str]
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
@@ -6142,8 +6138,8 @@ def get_loyalty_card_transactions_with_http_info(
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
@@ -6174,9 +6170,9 @@ def get_loyalty_card_transactions_with_http_info(
:type subledger_id: List[str]
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
@@ -6252,8 +6248,8 @@ def get_loyalty_card_transactions_without_preload_content(
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
subledger_id: Annotated[Optional[List[StrictStr]], Field(description="Filter results by one or more subledger IDs. Must be exact match.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
@@ -6284,9 +6280,9 @@ def get_loyalty_card_transactions_without_preload_content(
:type subledger_id: List[str]
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
@@ -6895,12 +6891,12 @@ def get_loyalty_program_profile_transactions(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -6919,23 +6915,23 @@ def get_loyalty_program_profile_transactions(
) -> GetLoyaltyProgramProfileTransactions200Response:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -7005,12 +7001,12 @@ def get_loyalty_program_profile_transactions_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -7029,23 +7025,23 @@ def get_loyalty_program_profile_transactions_with_http_info(
) -> ApiResponse[GetLoyaltyProgramProfileTransactions200Response]:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -7115,12 +7111,12 @@ def get_loyalty_program_profile_transactions_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -7139,23 +7135,23 @@ def get_loyalty_program_profile_transactions_without_preload_content(
) -> RESTResponseType:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date. If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -7639,7 +7635,7 @@ def link_loyalty_card_to_profile(
) -> LoyaltyCard:
"""Link customer profile to card
- [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). **Note:** You can link as many customer profiles to a given loyalty card as the [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) allows.
+ [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). > [!note] You can link as many customer profiles to a given loyalty card as the > [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) > allows.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -7717,7 +7713,7 @@ def link_loyalty_card_to_profile_with_http_info(
) -> ApiResponse[LoyaltyCard]:
"""Link customer profile to card
- [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). **Note:** You can link as many customer profiles to a given loyalty card as the [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) allows.
+ [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). > [!note] You can link as many customer profiles to a given loyalty card as the > [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) > allows.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -7795,7 +7791,7 @@ def link_loyalty_card_to_profile_without_preload_content(
) -> RESTResponseType:
"""Link customer profile to card
- [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). **Note:** You can link as many customer profiles to a given loyalty card as the [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) allows.
+ [Loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview) allow customers to collect and spend loyalty points within a [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). They are useful to gamify loyalty programs and can be used with or without customer profiles linked to them. Link a customer profile to a given loyalty card for the card to be set as **Registered**. This affects how it can be used. See the [docs](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card). > [!note] You can link as many customer profiles to a given loyalty card as the > [**card user limit**](https://docs.talon.one/docs/product/loyalty-programs/card-based/creating-cb-programs) > allows.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -7931,286 +7927,10 @@ def _link_loyalty_card_to_profile_serialize(
- @validate_call
- def price_history(
- self,
- price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
- _request_timeout: Union[
- None,
- Annotated[StrictFloat, Field(gt=0)],
- Tuple[
- Annotated[StrictFloat, Field(gt=0)],
- Annotated[StrictFloat, Field(gt=0)]
- ]
- ] = None,
- _request_auth: Optional[Dict[StrictStr, Any]] = None,
- _content_type: Optional[StrictStr] = None,
- _headers: Optional[Dict[StrictStr, Any]] = None,
- _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
- ) -> PriceHistoryResponse:
- """Get summary of price history
-
- Fetch the historical price data for a given SKU within a defined timeframe.
-
- :param price_history_request: body (required)
- :type price_history_request: PriceHistoryRequest
- :param _request_timeout: timeout setting for this request. If one
- number provided, it will be total request
- timeout. It can also be a pair (tuple) of
- (connection, read) timeouts.
- :type _request_timeout: int, tuple(int, int), optional
- :param _request_auth: set to override the auth_settings for an a single
- request; this effectively ignores the
- authentication in the spec for a single request.
- :type _request_auth: dict, optional
- :param _content_type: force content-type for the request.
- :type _content_type: str, Optional
- :param _headers: set to override the headers for a single
- request; this effectively ignores the headers
- in the spec for a single request.
- :type _headers: dict, optional
- :param _host_index: set to override the host_index for a single
- request; this effectively ignores the host_index
- in the spec for a single request.
- :type _host_index: int, optional
- :return: Returns the result object.
- """ # noqa: E501
-
- _param = self._price_history_serialize(
- price_history_request=price_history_request,
- _request_auth=_request_auth,
- _content_type=_content_type,
- _headers=_headers,
- _host_index=_host_index
- )
-
- _response_types_map: Dict[str, Optional[str]] = {
- '200': "PriceHistoryResponse",
- }
- response_data = self.api_client.call_api(
- *_param,
- _request_timeout=_request_timeout
- )
- response_data.read()
- return self.api_client.response_deserialize(
- response_data=response_data,
- response_types_map=_response_types_map,
- ).data
-
-
- @validate_call
- def price_history_with_http_info(
- self,
- price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
- _request_timeout: Union[
- None,
- Annotated[StrictFloat, Field(gt=0)],
- Tuple[
- Annotated[StrictFloat, Field(gt=0)],
- Annotated[StrictFloat, Field(gt=0)]
- ]
- ] = None,
- _request_auth: Optional[Dict[StrictStr, Any]] = None,
- _content_type: Optional[StrictStr] = None,
- _headers: Optional[Dict[StrictStr, Any]] = None,
- _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
- ) -> ApiResponse[PriceHistoryResponse]:
- """Get summary of price history
-
- Fetch the historical price data for a given SKU within a defined timeframe.
-
- :param price_history_request: body (required)
- :type price_history_request: PriceHistoryRequest
- :param _request_timeout: timeout setting for this request. If one
- number provided, it will be total request
- timeout. It can also be a pair (tuple) of
- (connection, read) timeouts.
- :type _request_timeout: int, tuple(int, int), optional
- :param _request_auth: set to override the auth_settings for an a single
- request; this effectively ignores the
- authentication in the spec for a single request.
- :type _request_auth: dict, optional
- :param _content_type: force content-type for the request.
- :type _content_type: str, Optional
- :param _headers: set to override the headers for a single
- request; this effectively ignores the headers
- in the spec for a single request.
- :type _headers: dict, optional
- :param _host_index: set to override the host_index for a single
- request; this effectively ignores the host_index
- in the spec for a single request.
- :type _host_index: int, optional
- :return: Returns the result object.
- """ # noqa: E501
-
- _param = self._price_history_serialize(
- price_history_request=price_history_request,
- _request_auth=_request_auth,
- _content_type=_content_type,
- _headers=_headers,
- _host_index=_host_index
- )
-
- _response_types_map: Dict[str, Optional[str]] = {
- '200': "PriceHistoryResponse",
- }
- response_data = self.api_client.call_api(
- *_param,
- _request_timeout=_request_timeout
- )
- response_data.read()
- return self.api_client.response_deserialize(
- response_data=response_data,
- response_types_map=_response_types_map,
- )
-
-
- @validate_call
- def price_history_without_preload_content(
- self,
- price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
- _request_timeout: Union[
- None,
- Annotated[StrictFloat, Field(gt=0)],
- Tuple[
- Annotated[StrictFloat, Field(gt=0)],
- Annotated[StrictFloat, Field(gt=0)]
- ]
- ] = None,
- _request_auth: Optional[Dict[StrictStr, Any]] = None,
- _content_type: Optional[StrictStr] = None,
- _headers: Optional[Dict[StrictStr, Any]] = None,
- _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
- ) -> RESTResponseType:
- """Get summary of price history
-
- Fetch the historical price data for a given SKU within a defined timeframe.
-
- :param price_history_request: body (required)
- :type price_history_request: PriceHistoryRequest
- :param _request_timeout: timeout setting for this request. If one
- number provided, it will be total request
- timeout. It can also be a pair (tuple) of
- (connection, read) timeouts.
- :type _request_timeout: int, tuple(int, int), optional
- :param _request_auth: set to override the auth_settings for an a single
- request; this effectively ignores the
- authentication in the spec for a single request.
- :type _request_auth: dict, optional
- :param _content_type: force content-type for the request.
- :type _content_type: str, Optional
- :param _headers: set to override the headers for a single
- request; this effectively ignores the headers
- in the spec for a single request.
- :type _headers: dict, optional
- :param _host_index: set to override the host_index for a single
- request; this effectively ignores the host_index
- in the spec for a single request.
- :type _host_index: int, optional
- :return: Returns the result object.
- """ # noqa: E501
-
- _param = self._price_history_serialize(
- price_history_request=price_history_request,
- _request_auth=_request_auth,
- _content_type=_content_type,
- _headers=_headers,
- _host_index=_host_index
- )
-
- _response_types_map: Dict[str, Optional[str]] = {
- '200': "PriceHistoryResponse",
- }
- response_data = self.api_client.call_api(
- *_param,
- _request_timeout=_request_timeout
- )
- return response_data.response
-
-
- def _price_history_serialize(
- self,
- price_history_request,
- _request_auth,
- _content_type,
- _headers,
- _host_index,
- ) -> RequestSerialized:
-
- _host = None
-
- _collection_formats: Dict[str, str] = {
- }
-
- _path_params: Dict[str, str] = {}
- _query_params: List[Tuple[str, str]] = []
- _header_params: Dict[str, Optional[str]] = _headers or {}
- _form_params: List[Tuple[str, str]] = []
- _files: Dict[
- str, Union[str, bytes, List[str], List[bytes], List[Tuple[str, bytes]]]
- ] = {}
- _body_params: Optional[bytes] = None
-
- # process the path parameters
- # process the query parameters
- # process the header parameters
- # process the form parameters
- # process the body parameter
- if price_history_request is not None:
- _body_params = price_history_request
-
-
- # set the HTTP header `Accept`
- if 'Accept' not in _header_params:
- _header_params['Accept'] = self.api_client.select_header_accept(
- [
- 'application/json'
- ]
- )
-
- # set the HTTP header `Content-Type`
- if _content_type:
- _header_params['Content-Type'] = _content_type
- else:
- _default_content_type = (
- self.api_client.select_header_content_type(
- [
- 'application/json'
- ]
- )
- )
- if _default_content_type is not None:
- _header_params['Content-Type'] = _default_content_type
-
- # authentication setting
- _auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
- 'api_key_v1'
- ]
-
- return self.api_client.param_serialize(
- method='POST',
- resource_path='/v1/best_prior_price_history',
- path_params=_path_params,
- query_params=_query_params,
- header_params=_header_params,
- body=_body_params,
- post_params=_form_params,
- files=_files,
- auth_settings=_auth_settings,
- collection_formats=_collection_formats,
- _host=_host,
- _request_auth=_request_auth
- )
-
-
-
-
@validate_call
def reopen_customer_session(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8226,9 +7946,9 @@ def reopen_customer_session(
) -> ReopenSessionResponse:
"""Reopen customer session
- Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the Cancelling a session with campaign budgets tutorial.
**Note:** If your order workflow requires you to create a new session instead of reopening a session, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint to cancel a closed session and create a new one.
+ Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the [Cancelling a session with campaign budgets](https://docs.talon.one/docs/dev/tutorials/rolling-back-effects) tutorial. > [!note] If your order workflow requires you to create a new session > instead of reopening a session, use the > [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) > endpoint to cancel a closed session and create a new one.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8279,7 +7999,7 @@ def reopen_customer_session(
@validate_call
def reopen_customer_session_with_http_info(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8295,9 +8015,9 @@ def reopen_customer_session_with_http_info(
) -> ApiResponse[ReopenSessionResponse]:
"""Reopen customer session
- Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the Cancelling a session with campaign budgets tutorial.
**Note:** If your order workflow requires you to create a new session instead of reopening a session, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint to cancel a closed session and create a new one.
+ Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the [Cancelling a session with campaign budgets](https://docs.talon.one/docs/dev/tutorials/rolling-back-effects) tutorial. > [!note] If your order workflow requires you to create a new session > instead of reopening a session, use the > [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) > endpoint to cancel a closed session and create a new one.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8348,7 +8068,7 @@ def reopen_customer_session_with_http_info(
@validate_call
def reopen_customer_session_without_preload_content(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8364,9 +8084,9 @@ def reopen_customer_session_without_preload_content(
) -> RESTResponseType:
"""Reopen customer session
- Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the Cancelling a session with campaign budgets tutorial.
**Note:** If your order workflow requires you to create a new session instead of reopening a session, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint to cancel a closed session and create a new one.
+ Reopen a closed [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). For example, if a session has been completed but still needs to be edited, you can reopen it with this endpoint. A reopen session is treated like a standard open session. When reopening a session: - The `talon_session_reopened` event is triggered. You can see it in the **Events** view in the Campaign Manager. - The session state is updated to `open`. - Any modified budgets and triggered effects are rolled back when the session closes. - Depending on the [return policy](https://docs.talon.one/docs/product/loyalty-programs/managing-loyalty-programs#return-policy) in your loyalty programs, points are rolled back in the following ways: - Pending points are rolled back automatically. - If **Active points deduction** setting is enabled, any points that were earned and activated when the session closed are rolled back. - If **Negative balance** is enabled, the rollback can create a negative points balance. Effects and budgets unimpacted by a session reopening
The following effects and budgets remain in the state they were in when the session closed:
- Add free item effect
- Award giveaway
- Coupon and referral creation
- Coupon reservation
- Custom effect
- Update attribute value
- Update cart item attribute value
To see an example of a rollback, see the [Cancelling a session with campaign budgets](https://docs.talon.one/docs/dev/tutorials/rolling-back-effects) tutorial. > [!note] If your order workflow requires you to create a new session > instead of reopening a session, use the > [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) > endpoint to cancel a closed session and create a new one.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8477,7 +8197,7 @@ def _reopen_customer_session_serialize(
@validate_call
def return_cart_items(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
return_integration_request: Annotated[ReturnIntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. ")] = None,
_request_timeout: Union[
@@ -8495,9 +8215,9 @@ def return_cart_items(
) -> IntegrationStateV2:
"""Return cart items
- Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. **Note:** This will roll back any effects associated with these cart items. For more information, see [our documentation on session states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session).
+ Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. > [!note] This will roll back any effects associated with these cart items. > For more information, see [our documentation on session > states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) > and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session). > [!note] To make request processing idempotent for this endpoint, include the `Idempotency-Key` header with an idempotency key in requests. Also: > - Requests with the `Idempotency-Key` header are logged in the Talon.One access logs. > - Responses for idempotent requests are stored in the database and expire 24 hours after the request is sent. > - Idempotency keys are typically UUID keys and should not exceed 255 characters in length.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param return_integration_request: body (required)
:type return_integration_request: ReturnIntegrationRequest
@@ -8554,7 +8274,7 @@ def return_cart_items(
@validate_call
def return_cart_items_with_http_info(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
return_integration_request: Annotated[ReturnIntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. ")] = None,
_request_timeout: Union[
@@ -8572,9 +8292,9 @@ def return_cart_items_with_http_info(
) -> ApiResponse[IntegrationStateV2]:
"""Return cart items
- Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. **Note:** This will roll back any effects associated with these cart items. For more information, see [our documentation on session states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session).
+ Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. > [!note] This will roll back any effects associated with these cart items. > For more information, see [our documentation on session > states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) > and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session). > [!note] To make request processing idempotent for this endpoint, include the `Idempotency-Key` header with an idempotency key in requests. Also: > - Requests with the `Idempotency-Key` header are logged in the Talon.One access logs. > - Responses for idempotent requests are stored in the database and expire 24 hours after the request is sent. > - Idempotency keys are typically UUID keys and should not exceed 255 characters in length.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param return_integration_request: body (required)
:type return_integration_request: ReturnIntegrationRequest
@@ -8631,7 +8351,7 @@ def return_cart_items_with_http_info(
@validate_call
def return_cart_items_without_preload_content(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
return_integration_request: Annotated[ReturnIntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. ")] = None,
_request_timeout: Union[
@@ -8649,9 +8369,9 @@ def return_cart_items_without_preload_content(
) -> RESTResponseType:
"""Return cart items
- Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. **Note:** This will roll back any effects associated with these cart items. For more information, see [our documentation on session states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session).
+ Create a new return request for the specified cart items. This endpoint automatically changes the session state from `closed` to `partially_returned`. > [!note] This will roll back any effects associated with these cart items. > For more information, see [our documentation on session > states](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) > and [this tutorial](https://docs.talon.one/docs/dev/tutorials/partially-returning-a-session). > [!note] To make request processing idempotent for this endpoint, include the `Idempotency-Key` header with an idempotency key in requests. Also: > - Requests with the `Idempotency-Key` header are logged in the Talon.One access logs. > - Responses for idempotent requests are stored in the database and expire 24 hours after the request is sent. > - Idempotency keys are typically UUID keys and should not exceed 255 characters in length.
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param return_integration_request: body (required)
:type return_integration_request: ReturnIntegrationRequest
@@ -8806,7 +8526,7 @@ def sync_catalog(
) -> Catalog:
"""Sync cart item catalog
- Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. **Important**: You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
+ Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. > [!important] You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
:param catalog_id: The ID of the catalog. You can find the ID in the Campaign Manager in **Account** > **Tools** > **Cart item catalogs**. (required)
:type catalog_id: int
@@ -8880,7 +8600,7 @@ def sync_catalog_with_http_info(
) -> ApiResponse[Catalog]:
"""Sync cart item catalog
- Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. **Important**: You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
+ Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. > [!important] You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
:param catalog_id: The ID of the catalog. You can find the ID in the Campaign Manager in **Account** > **Tools** > **Cart item catalogs**. (required)
:type catalog_id: int
@@ -8954,7 +8674,7 @@ def sync_catalog_without_preload_content(
) -> RESTResponseType:
"""Sync cart item catalog
- Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. **Important**: You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
+ Perform the following actions for a given cart item catalog: - Add an item to the catalog. - Add multiple items to the catalog. - Update the attributes of an item in the catalog. - Update the attributes of multiple items in the catalog. - Remove an item from the catalog. - Remove multiple items from the catalog. You can either add, update, or delete up to 1000 cart items in a single request. Each item synced to a catalog must have a unique `SKU`. > [!important] You can perform only one type of action in a single sync request. Syncing items with duplicate `SKU` values in a single request returns an error message with a `400` status code. For more information, read [managing cart item catalogs](https://docs.talon.one/docs/product/account/dev-tools/managing-cart-item-catalogs). ### Filtering cart items Use [cart item attributes](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) to filter items and select the ones you want to edit or delete when editing or deleting more than one item at a time. The `filters` array contains an object with the following properties: - `attr`: A [cart item attribute](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes) connected to the catalog. It is applied to all items in the catalog. - `op`: The filtering operator indicating the relationship between the value of each cart item in the catalog and the value of the `value` property for the attribute selected in `attr`. The value of `op` can be one of the following: - `EQ`: Equal to `value` - `LT`: Less than `value` - `LE`: Less than or equal to `value` - `GT`: Greater than `value` - `GE`: Greater than or equal to `value` - `IN`: One of the comma-separated values that `value` is set to. **Note:** `GE`, `LE`, `GT`, `LT` are for numeric values only. - `value`: The value of the attribute selected in `attr`. ### Payload examples Synchronization actions are sent as `PUT` requests. See the structure for each action: Adding an item to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Adding multiple items to the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241027\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" }, { \"payload\": { \"attributes\": { \"color\": \"Navy blue\", \"type\": \"shoes\" }, \"replaceIfExists\": true, \"sku\": \"SKU1241028\", \"price\": 100, \"product\": { \"name\": \"sneakers\" } }, \"type\": \"ADD\" } ] } ```
Updating the attributes of an item in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"age\": 11, \"origin\": \"germany\" }, \"createIfNotExists\": false, \"sku\": \"SKU1241028\", \"product\": { \"name\": \"sneakers\" } }, \"type\": \"PATCH\" } ] } ```
Updating the attributes of multiple items in the catalog
```json { \"actions\": [ { \"payload\": { \"attributes\": { \"color\": \"red\" }, \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"PATCH_MANY\" } ] } ```
Removing an item from the catalog
```json { \"actions\": [ { \"payload\": { \"sku\": \"SKU1241028\" }, \"type\": \"REMOVE\" } ] } ```
Removing multiple items from the catalog
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"color\", \"op\": \"EQ\", \"value\": \"blue\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
Removing shoes of sizes above 45 from the catalog
Let's imagine that we have a shoe store and we have decided to stop selling shoes larger than size 45. We can remove from the catalog all the shoes of sizes above 45 with a single action:
```json { \"actions\": [ { \"payload\": { \"filters\": [ { \"attr\": \"size\", \"op\": \"GT\", \"value\": \"45\" } ] }, \"type\": \"REMOVE_MANY\" } ] } ```
:param catalog_id: The ID of the catalog. You can find the ID in the Campaign Manager in **Account** > **Tools** > **Cart item catalogs**. (required)
:type catalog_id: int
@@ -9106,7 +8826,7 @@ def track_event_v2(
) -> IntegrationEventV2Response:
"""Track event
- Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). Important
1. `profileId` is required even though the schema does not specify it. 1. If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. 1. We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). 1. [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
+ Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). > [!note] **Note** > - `profileId` is required even though the schema does not specify it. > - If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
:param integration_event_v2_request: body (required)
:type integration_event_v2_request: IntegrationEventV2Request
@@ -9188,7 +8908,7 @@ def track_event_v2_with_http_info(
) -> ApiResponse[IntegrationEventV2Response]:
"""Track event
- Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). Important
1. `profileId` is required even though the schema does not specify it. 1. If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. 1. We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). 1. [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
+ Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). > [!note] **Note** > - `profileId` is required even though the schema does not specify it. > - If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
:param integration_event_v2_request: body (required)
:type integration_event_v2_request: IntegrationEventV2Request
@@ -9270,7 +8990,7 @@ def track_event_v2_without_preload_content(
) -> RESTResponseType:
"""Track event
- Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). Important
1. `profileId` is required even though the schema does not specify it. 1. If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. 1. We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). 1. [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
+ Triggers a custom event. To use this endpoint: 1. Define a [custom event](https://docs.talon.one/docs/dev/concepts/entities/events#creating-a-custom-event) in the Campaign Manager. 1. Update or create a rule to check for this event. 1. Trigger the event with this endpoint. After you have successfully sent an event to Talon.One, you can list the received events in the **Events** view in the Campaign Manager. Talon.One also offers a set of [built-in events](https://docs.talon.one/docs/dev/concepts/entities/events). Ensure you do not create a custom event when you can use a built-in event. For example, use this endpoint to trigger an event when a customer shares a link to a product. See the [tutorial](https://docs.talon.one/docs/product/tutorials/referrals/incentivizing-product-link-sharing). > [!note] **Note** > - `profileId` is required even though the schema does not specify it. > - If the customer profile ID is new, a new profile is automatically created but the `customer_profile_created` [built-in event ](https://docs.talon.one/docs/dev/concepts/entities/events) is **not** triggered. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation.
:param integration_event_v2_request: body (required)
:type integration_event_v2_request: IntegrationEventV2Request
@@ -9439,7 +9159,7 @@ def unlink_loyalty_card_from_profile(
) -> LoyaltyCard:
"""Unlink customer profile from a loyalty card
- Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier of the card-based loyalty program containing the loyalty card. You can get this ID using the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -9517,7 +9237,7 @@ def unlink_loyalty_card_from_profile_with_http_info(
) -> ApiResponse[LoyaltyCard]:
"""Unlink customer profile from a loyalty card
- Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier of the card-based loyalty program containing the loyalty card. You can get this ID using the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -9595,7 +9315,7 @@ def unlink_loyalty_card_from_profile_without_preload_content(
) -> RESTResponseType:
"""Unlink customer profile from a loyalty card
- Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Unlink a customer profile from a [registered](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards#linking-customer-profiles-to-a-loyalty-card) loyalty card. To get the `integrationId` of a customer profile, you can use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier of the card-based loyalty program containing the loyalty card. You can get this ID using the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -10340,7 +10060,7 @@ def update_customer_profile_audiences(
) -> None:
"""Update multiple customer profiles' audiences
- Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. **Note:** You can also do this using the [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) effect.
+ Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. > [!note] You can also do this using the > [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) > effect.
:param customer_profile_audience_request: body (required)
:type customer_profile_audience_request: CustomerProfileAudienceRequest
@@ -10410,7 +10130,7 @@ def update_customer_profile_audiences_with_http_info(
) -> ApiResponse[None]:
"""Update multiple customer profiles' audiences
- Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. **Note:** You can also do this using the [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) effect.
+ Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. > [!note] You can also do this using the > [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) > effect.
:param customer_profile_audience_request: body (required)
:type customer_profile_audience_request: CustomerProfileAudienceRequest
@@ -10480,7 +10200,7 @@ def update_customer_profile_audiences_without_preload_content(
) -> RESTResponseType:
"""Update multiple customer profiles' audiences
- Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. **Note:** You can also do this using the [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) effect.
+ Add customer profiles to or remove them from an audience. The endpoint supports 1000 audience actions (`add` or `remove`) per request. > [!note] You can also do this using the > [Update audience](https://docs.talon.one/docs/product/rules/effects/using-effects#updating-an-audience) > effect.
:param customer_profile_audience_request: body (required)
:type customer_profile_audience_request: CustomerProfileAudienceRequest
@@ -10626,7 +10346,7 @@ def update_customer_profile_v2(
) -> CustomerProfileIntegrationResponseV2:
"""Update customer profile
- Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. **Note:** [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`. Performance tips
- Updating a customer profile returns a response with the requested integration state. - You can use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
+ Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. > [!note] **Note** > - Updating a customer profile returns a response with the requested integration state. > - You can use the `responseContent` property to save yourself extra API calls. For example, you can get > the customer profile details directly without extra requests. > - We recommend sending requests sequentially. > See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`.
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
@@ -10708,7 +10428,7 @@ def update_customer_profile_v2_with_http_info(
) -> ApiResponse[CustomerProfileIntegrationResponseV2]:
"""Update customer profile
- Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. **Note:** [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`. Performance tips
- Updating a customer profile returns a response with the requested integration state. - You can use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
+ Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. > [!note] **Note** > - Updating a customer profile returns a response with the requested integration state. > - You can use the `responseContent` property to save yourself extra API calls. For example, you can get > the customer profile details directly without extra requests. > - We recommend sending requests sequentially. > See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`.
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
@@ -10790,7 +10510,7 @@ def update_customer_profile_v2_without_preload_content(
) -> RESTResponseType:
"""Update customer profile
- Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. **Note:** [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`. Performance tips
- Updating a customer profile returns a response with the requested integration state. - You can use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
+ Update or create a [Customer Profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles). This endpoint triggers the Rule Builder. You can use this endpoint to: - Set attributes on the given customer profile. Ensure you create the attributes in the Campaign Manager, first. - Modify the audience the customer profile is a member of. > [!note] **Note** > - Updating a customer profile returns a response with the requested integration state. > - You can use the `responseContent` property to save yourself extra API calls. For example, you can get > the customer profile details directly without extra requests. > - We recommend sending requests sequentially. > See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered in rule evaluation when `runRuleEngine` is `true`.
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
@@ -10956,7 +10676,7 @@ def update_customer_profiles_v2(
) -> MultipleCustomerProfileIntegrationResponseV2:
"""Update multiple customer profiles
- Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). **Note:** This endpoint does not trigger the Rule Engine. To trigger the Rule Engine for customer profile updates, use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
+ Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). > [!note] This endpoint does not trigger the Rule Engine. > To trigger the Rule Engine for customer profile updates, > use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
:param multiple_customer_profile_integration_request: body (required)
:type multiple_customer_profile_integration_request: MultipleCustomerProfileIntegrationRequest
@@ -11029,7 +10749,7 @@ def update_customer_profiles_v2_with_http_info(
) -> ApiResponse[MultipleCustomerProfileIntegrationResponseV2]:
"""Update multiple customer profiles
- Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). **Note:** This endpoint does not trigger the Rule Engine. To trigger the Rule Engine for customer profile updates, use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
+ Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). > [!note] This endpoint does not trigger the Rule Engine. > To trigger the Rule Engine for customer profile updates, > use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
:param multiple_customer_profile_integration_request: body (required)
:type multiple_customer_profile_integration_request: MultipleCustomerProfileIntegrationRequest
@@ -11102,7 +10822,7 @@ def update_customer_profiles_v2_without_preload_content(
) -> RESTResponseType:
"""Update multiple customer profiles
- Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). **Note:** This endpoint does not trigger the Rule Engine. To trigger the Rule Engine for customer profile updates, use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
+ Update (or create) up to 1000 [customer profiles](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) in 1 request. The `integrationId` must be any identifier that remains stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. A customer profile [can be linked to one or more sessions](https://docs.talon.one/integration-api#tag/Customer-sessions). > [!note] This endpoint does not trigger the Rule Engine. > To trigger the Rule Engine for customer profile updates, > use the [Update customer profile](#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint.
:param multiple_customer_profile_integration_request: body (required)
:type multiple_customer_profile_integration_request: MultipleCustomerProfileIntegrationRequest
@@ -11236,10 +10956,10 @@ def _update_customer_profiles_v2_serialize(
@validate_call
def update_customer_session_v2(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
integration_request: Annotated[IntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests). ")] = None,
- now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
+ now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11255,15 +10975,15 @@ def update_customer_session_v2(
) -> IntegrationStateV2:
"""Update customer session
- Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. **Note:** - The currency for the session and the cart items in it is the currency set for the Application linked to this session. - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. **Note:** If the specified profile does not exist, an empty profile is **created automatically**. You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). Performance tips
- Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
+ Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. > [!note] **Note** > - The currency for the session and the cart items in it is the currency set for the Application linked to this session. > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. > [!note] **Note** > - If the specified profile does not exist, an empty profile is **created automatically**. > You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). > - Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. > For example, you can get the customer profile details directly without extra requests. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param integration_request: body (required)
:type integration_request: IntegrationRequest
:param dry: Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests).
:type dry: bool
- :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`.
+ :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`.
:type now: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -11318,10 +11038,10 @@ def update_customer_session_v2(
@validate_call
def update_customer_session_v2_with_http_info(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
integration_request: Annotated[IntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests). ")] = None,
- now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
+ now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11337,15 +11057,15 @@ def update_customer_session_v2_with_http_info(
) -> ApiResponse[IntegrationStateV2]:
"""Update customer session
- Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. **Note:** - The currency for the session and the cart items in it is the currency set for the Application linked to this session. - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. **Note:** If the specified profile does not exist, an empty profile is **created automatically**. You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). Performance tips
- Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
+ Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. > [!note] **Note** > - The currency for the session and the cart items in it is the currency set for the Application linked to this session. > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. > [!note] **Note** > - If the specified profile does not exist, an empty profile is **created automatically**. > You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). > - Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. > For example, you can get the customer profile details directly without extra requests. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param integration_request: body (required)
:type integration_request: IntegrationRequest
:param dry: Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests).
:type dry: bool
- :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`.
+ :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`.
:type now: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -11400,10 +11120,10 @@ def update_customer_session_v2_with_http_info(
@validate_call
def update_customer_session_v2_without_preload_content(
self,
- customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. ")],
+ customer_session_id: Annotated[StrictStr, Field(description="The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. ")],
integration_request: Annotated[IntegrationRequest, Field(description="body")],
dry: Annotated[Optional[StrictBool], Field(description="Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests). ")] = None,
- now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
+ now: Annotated[Optional[datetime], Field(description="A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11419,15 +11139,15 @@ def update_customer_session_v2_without_preload_content(
) -> RESTResponseType:
"""Update customer session
- Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. **Note:** - The currency for the session and the cart items in it is the currency set for the Application linked to this session. - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. **Note:** If the specified profile does not exist, an empty profile is **created automatically**. You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). Performance tips
- Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. For example, you can get the customer profile details directly without extra requests. - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests).
For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
+ Update or create a [customer session](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions). The endpoint responds with the potential promotion rule [effects](https://docs.talon.one/docs/dev/integration-api/api-effects) that match the current cart. For example, use this endpoint to share the contents of a customer's cart with Talon.One. > [!note] **Note** > - The currency for the session and the cart items in it is the currency set for the Application linked to this session. > - [Archived campaigns](https://docs.talon.one/docs/product/campaigns/managing-campaigns#archiving-a-campaign) are not considered for rule evaluation. ### Session management To use this endpoint, start by learning about [customer sessions](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions) and their states and refer to the `state` parameter documentation the request body schema docs below. ### Sessions and customer profiles - To link a session to a customer profile, set the `profileId` parameter in the request body to a customer profile's `integrationId`. - While you can create an anonymous session with `profileId=\"\"`, we recommend you use a guest ID instead. - A profile can be linked to simultaneous sessions in different Applications. Either: - Use unique session integration IDs or, - Use the same session integration ID across all of the Applications. > [!note] **Note** > - If the specified profile does not exist, an empty profile is **created automatically**. > You can update it with [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2). > - Updating a customer session returns a response with the new integration state. Use the `responseContent` property to save yourself extra API calls. > For example, you can get the customer profile details directly without extra requests. > - We recommend sending requests sequentially. See [Managing parallel requests](https://docs.talon.one/docs/dev/getting-started/integration-tutorial#managing-parallel-requests). For more information, see: - The introductory video in [Getting started](https://docs.talon.one/docs/dev/getting-started/overview). - The [integration tutorial](https://docs.talon.one/docs/dev/tutorials/integrating-talon-one).
- :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#operation/getApplicationSessions) endpoint. (required)
+ :param customer_session_id: The `integration ID` of the customer session. You set this ID when you create a customer session. You can see existing customer session integration IDs in the Campaign Manager's **Sessions** menu, or via the [List Application session](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationSessions) endpoint. (required)
:type customer_session_id: str
:param integration_request: body (required)
:type integration_request: IntegrationRequest
:param dry: Indicates whether to persist the changes. Changes are ignored when `dry=true`. When set to `true`: - The endpoint considers **only** the payload that you pass when **closing** the session. When you do not use the `dry` parameter, the endpoint behaves as a typical PUT endpoint. Each update builds upon the previous ones. - You can use the `evaluableCampaignIds` body property to select specific campaigns to run. [See the docs](https://docs.talon.one/docs/dev/integration-api/dry-requests).
:type dry: bool
- :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). **Note:** - It must be an RFC3339 timestamp string. - It can **only** be a date in the future. - It can **only** be used if the `dry` parameter in the query is set to `true`.
+ :param now: A timestamp value of a future date that acts as a current date when included in the query. Use this parameter, for example, to test campaigns that would be evaluated for this customer session in the future (say, [scheduled campaigns](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-schedule)). > [!note] **Note** > - It must be an RFC3339 timestamp string. > - It can **only** be a date in the future. > - It can **only** be used if the `dry` parameter in the query is set to `true`.
:type now: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
diff --git a/talon_one/api/management_api.py b/talon_one/api/management_api.py
index 00acafa..54dd33e 100644
--- a/talon_one/api/management_api.py
+++ b/talon_one/api/management_api.py
@@ -1,7 +1,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -119,6 +119,8 @@
from talon_one.models.new_password import NewPassword
from talon_one.models.new_password_email import NewPasswordEmail
from talon_one.models.new_store import NewStore
+from talon_one.models.price_history_request import PriceHistoryRequest
+from talon_one.models.price_history_response import PriceHistoryResponse
from talon_one.models.referral import Referral
from talon_one.models.role_v2 import RoleV2
from talon_one.models.role_v2_base import RoleV2Base
@@ -413,8 +415,6 @@ def _activate_user_by_email_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -728,8 +728,6 @@ def _add_loyalty_card_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -772,7 +770,7 @@ def add_loyalty_points(
) -> None:
"""Add points to customer profile
- Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -850,7 +848,7 @@ def add_loyalty_points_with_http_info(
) -> ApiResponse[None]:
"""Add points to customer profile
- Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -928,7 +926,7 @@ def add_loyalty_points_without_preload_content(
) -> RESTResponseType:
"""Add points to customer profile
- Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Add points in the specified loyalty program for the given customer. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -1043,8 +1041,6 @@ def _add_loyalty_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -1349,8 +1345,6 @@ def _copy_campaign_to_applications_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -1634,8 +1628,6 @@ def _create_account_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -1949,8 +1941,6 @@ def _create_achievement_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -2225,8 +2215,6 @@ def _create_additional_cost_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -2501,8 +2489,6 @@ def _create_attribute_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -2544,7 +2530,7 @@ def create_batch_loyalty_cards(
) -> LoyaltyCardBatchResponse:
"""Create loyalty cards
- Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. **Important:** - The specified card-based loyalty program must have a defined card code format that is used to generate the loyalty card codes. - Trying to create more than 20,000 loyalty cards in a single request returns an error message with a `400` status code.
+ Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. > [!important] **Note** > - The specified card-based loyalty program must have a defined card code > format that is used to generate the loyalty card codes. > - Trying to create more than 20,000 loyalty cards in a single request > returns an error message with a `400` status code.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -2618,7 +2604,7 @@ def create_batch_loyalty_cards_with_http_info(
) -> ApiResponse[LoyaltyCardBatchResponse]:
"""Create loyalty cards
- Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. **Important:** - The specified card-based loyalty program must have a defined card code format that is used to generate the loyalty card codes. - Trying to create more than 20,000 loyalty cards in a single request returns an error message with a `400` status code.
+ Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. > [!important] **Note** > - The specified card-based loyalty program must have a defined card code > format that is used to generate the loyalty card codes. > - Trying to create more than 20,000 loyalty cards in a single request > returns an error message with a `400` status code.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -2692,7 +2678,7 @@ def create_batch_loyalty_cards_without_preload_content(
) -> RESTResponseType:
"""Create loyalty cards
- Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. **Important:** - The specified card-based loyalty program must have a defined card code format that is used to generate the loyalty card codes. - Trying to create more than 20,000 loyalty cards in a single request returns an error message with a `400` status code.
+ Create a batch of loyalty cards in a specified [card-based loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview#loyalty-program-types). Customers can use loyalty cards to collect and spend loyalty points. > [!important] **Note** > - The specified card-based loyalty program must have a defined card code > format that is used to generate the loyalty card codes. > - Trying to create more than 20,000 loyalty cards in a single request > returns an error message with a `400` status code.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -2801,8 +2787,6 @@ def _create_batch_loyalty_cards_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -3092,8 +3076,6 @@ def _create_campaign_from_template_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -3404,8 +3386,6 @@ def _create_campaign_store_budget_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -3710,8 +3690,6 @@ def _create_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -4036,8 +4014,6 @@ def _create_coupons_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -4342,8 +4318,6 @@ def _create_coupons_async_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -4648,8 +4622,6 @@ def _create_coupons_deletion_job_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -4974,8 +4946,6 @@ def _create_coupons_for_multiple_recipients_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -5016,7 +4986,7 @@ def create_invite_email(
) -> NewInviteEmail:
"""Resend invitation email
- Resend an email invitation to an existing user. **Note:** The invitation token is valid for 24 hours after the email has been sent.
+ Resend an email invitation to an existing user. > [!note] The invitation token is valid for 24 hours after the email has been sent.
:param new_invite_email: body (required)
:type new_invite_email: NewInviteEmail
@@ -5083,7 +5053,7 @@ def create_invite_email_with_http_info(
) -> ApiResponse[NewInviteEmail]:
"""Resend invitation email
- Resend an email invitation to an existing user. **Note:** The invitation token is valid for 24 hours after the email has been sent.
+ Resend an email invitation to an existing user. > [!note] The invitation token is valid for 24 hours after the email has been sent.
:param new_invite_email: body (required)
:type new_invite_email: NewInviteEmail
@@ -5150,7 +5120,7 @@ def create_invite_email_without_preload_content(
) -> RESTResponseType:
"""Resend invitation email
- Resend an email invitation to an existing user. **Note:** The invitation token is valid for 24 hours after the email has been sent.
+ Resend an email invitation to an existing user. > [!note] The invitation token is valid for 24 hours after the email has been sent.
:param new_invite_email: body (required)
:type new_invite_email: NewInviteEmail
@@ -5250,8 +5220,6 @@ def _create_invite_email_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -5292,7 +5260,7 @@ def create_invite_v2(
) -> User:
"""Invite user
- Create a new user in the account and send an invitation to their email address. **Note**: The invitation token is valid for 24 hours after the email has been sent. You can resend an invitation to a user with the [Resend invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) endpoint.
+ Create a new user in the account and send an invitation to their email address. > [!note] The invitation token is valid for 24 hours after the email has > been sent. You can resend an invitation to a user with the [Resend > invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) > endpoint.
:param new_invitation: body (required)
:type new_invitation: NewInvitation
@@ -5359,7 +5327,7 @@ def create_invite_v2_with_http_info(
) -> ApiResponse[User]:
"""Invite user
- Create a new user in the account and send an invitation to their email address. **Note**: The invitation token is valid for 24 hours after the email has been sent. You can resend an invitation to a user with the [Resend invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) endpoint.
+ Create a new user in the account and send an invitation to their email address. > [!note] The invitation token is valid for 24 hours after the email has > been sent. You can resend an invitation to a user with the [Resend > invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) > endpoint.
:param new_invitation: body (required)
:type new_invitation: NewInvitation
@@ -5426,7 +5394,7 @@ def create_invite_v2_without_preload_content(
) -> RESTResponseType:
"""Invite user
- Create a new user in the account and send an invitation to their email address. **Note**: The invitation token is valid for 24 hours after the email has been sent. You can resend an invitation to a user with the [Resend invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) endpoint.
+ Create a new user in the account and send an invitation to their email address. > [!note] The invitation token is valid for 24 hours after the email has > been sent. You can resend an invitation to a user with the [Resend > invitation email](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/createInviteEmail) > endpoint.
:param new_invitation: body (required)
:type new_invitation: NewInvitation
@@ -5526,8 +5494,6 @@ def _create_invite_v2_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -5568,7 +5534,7 @@ def create_password_recovery_email(
) -> NewPasswordEmail:
"""Request a password reset
- Send an email with a password recovery link to the email address of an existing account. **Note:** The password recovery link expires 30 minutes after this endpoint is triggered.
+ Send an email with a password recovery link to the email address of an existing account. > [!note] The password recovery link expires 30 minutes after this endpoint is triggered.
:param new_password_email: body (required)
:type new_password_email: NewPasswordEmail
@@ -5635,7 +5601,7 @@ def create_password_recovery_email_with_http_info(
) -> ApiResponse[NewPasswordEmail]:
"""Request a password reset
- Send an email with a password recovery link to the email address of an existing account. **Note:** The password recovery link expires 30 minutes after this endpoint is triggered.
+ Send an email with a password recovery link to the email address of an existing account. > [!note] The password recovery link expires 30 minutes after this endpoint is triggered.
:param new_password_email: body (required)
:type new_password_email: NewPasswordEmail
@@ -5702,7 +5668,7 @@ def create_password_recovery_email_without_preload_content(
) -> RESTResponseType:
"""Request a password reset
- Send an email with a password recovery link to the email address of an existing account. **Note:** The password recovery link expires 30 minutes after this endpoint is triggered.
+ Send an email with a password recovery link to the email address of an existing account. > [!note] The password recovery link expires 30 minutes after this endpoint is triggered.
:param new_password_email: body (required)
:type new_password_email: NewPasswordEmail
@@ -5802,8 +5768,6 @@ def _create_password_recovery_email_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -5844,7 +5808,7 @@ def create_session(
) -> Session:
"""Create session
- Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. Granular API key
Instead of using a session, you can also use the
Management API key feature in the Campaign Manager to decide which endpoints can be used with a given key.
+ Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. > [!note] > Instead of using a session, you can also use the Management API key feature > in the Campaign Manager to decide which endpoints can be used with a given key.
:param login_params: body (required)
:type login_params: LoginParams
@@ -5911,7 +5875,7 @@ def create_session_with_http_info(
) -> ApiResponse[Session]:
"""Create session
- Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. Granular API key
Instead of using a session, you can also use the
Management API key feature in the Campaign Manager to decide which endpoints can be used with a given key.
+ Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. > [!note] > Instead of using a session, you can also use the Management API key feature > in the Campaign Manager to decide which endpoints can be used with a given key.
:param login_params: body (required)
:type login_params: LoginParams
@@ -5978,7 +5942,7 @@ def create_session_without_preload_content(
) -> RESTResponseType:
"""Create session
- Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. Granular API key
Instead of using a session, you can also use the
Management API key feature in the Campaign Manager to decide which endpoints can be used with a given key.
+ Create a session to use the Management API endpoints. Use the value of the `token` property provided in the response as bearer token in other API calls. A token is valid for 3 months. In accordance with best pratices, use your generated token for all your API requests. Do **not** regenerate a token for each request. This endpoint has a rate limit of 3 to 6 requests per second per account, depending on your setup. > [!note] > Instead of using a session, you can also use the Management API key feature > in the Campaign Manager to decide which endpoints can be used with a given key.
:param login_params: body (required)
:type login_params: LoginParams
@@ -6078,8 +6042,6 @@ def _create_session_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -6375,8 +6337,6 @@ def _create_store_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -6644,8 +6604,6 @@ def _deactivate_user_by_email_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -6959,8 +6917,6 @@ def _deduct_loyalty_card_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -6985,7 +6941,7 @@ def _deduct_loyalty_card_points_serialize(
@validate_call
def delete_account_collection(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -7003,7 +6959,7 @@ def delete_account_collection(
Delete a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -7053,7 +7009,7 @@ def delete_account_collection(
@validate_call
def delete_account_collection_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -7071,7 +7027,7 @@ def delete_account_collection_with_http_info(
Delete a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -7121,7 +7077,7 @@ def delete_account_collection_with_http_info(
@validate_call
def delete_account_collection_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -7139,7 +7095,7 @@ def delete_account_collection_without_preload_content(
Delete a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -7225,8 +7181,6 @@ def _delete_account_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -7524,8 +7478,6 @@ def _delete_achievement_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -7795,8 +7747,6 @@ def _delete_campaign_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -8110,8 +8060,6 @@ def _delete_campaign_store_budgets_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -8138,7 +8086,7 @@ def delete_collection(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8160,7 +8108,7 @@ def delete_collection(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8214,7 +8162,7 @@ def delete_collection_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8236,7 +8184,7 @@ def delete_collection_with_http_info(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8290,7 +8238,7 @@ def delete_collection_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -8312,7 +8260,7 @@ def delete_collection_without_preload_content(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -8406,8 +8354,6 @@ def _delete_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -8692,8 +8638,6 @@ def _delete_coupon_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -9238,8 +9182,6 @@ def _delete_coupons_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -9522,8 +9464,6 @@ def _delete_loyalty_card_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -9808,8 +9748,6 @@ def _delete_referral_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -10089,8 +10027,6 @@ def _delete_store_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -10345,8 +10281,6 @@ def _delete_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -10614,8 +10548,6 @@ def _delete_user_by_email_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -10855,8 +10787,6 @@ def _destroy_session_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -11142,8 +11072,6 @@ def _disconnect_campaign_stores_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -11168,7 +11096,7 @@ def _disconnect_campaign_stores_serialize(
@validate_call
def export_account_collection_items(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11184,9 +11112,9 @@ def export_account_collection_items(
) -> str:
"""Export account-level collection's items
- Download a CSV file containing items from a given account-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given account-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -11237,7 +11165,7 @@ def export_account_collection_items(
@validate_call
def export_account_collection_items_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11253,9 +11181,9 @@ def export_account_collection_items_with_http_info(
) -> ApiResponse[str]:
"""Export account-level collection's items
- Download a CSV file containing items from a given account-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given account-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -11306,7 +11234,7 @@ def export_account_collection_items_with_http_info(
@validate_call
def export_account_collection_items_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -11322,9 +11250,9 @@ def export_account_collection_items_without_preload_content(
) -> RESTResponseType:
"""Export account-level collection's items
- Download a CSV file containing items from a given account-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given account-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -11411,8 +11339,6 @@ def _export_account_collection_items_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -11713,8 +11639,6 @@ def _export_achievements_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -11740,8 +11664,8 @@ def _export_achievements_serialize(
def export_application_campaign_analytics(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
campaign_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned. ")] = None,
_request_timeout: Union[
None,
@@ -11758,13 +11682,13 @@ def export_application_campaign_analytics(
) -> str:
"""Export Application analytics aggregated by campaign
- Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
+ Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param campaign_ids: Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned.
:type campaign_ids: List[str]
@@ -11819,8 +11743,8 @@ def export_application_campaign_analytics(
def export_application_campaign_analytics_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
campaign_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned. ")] = None,
_request_timeout: Union[
None,
@@ -11837,13 +11761,13 @@ def export_application_campaign_analytics_with_http_info(
) -> ApiResponse[str]:
"""Export Application analytics aggregated by campaign
- Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
+ Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param campaign_ids: Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned.
:type campaign_ids: List[str]
@@ -11898,8 +11822,8 @@ def export_application_campaign_analytics_with_http_info(
def export_application_campaign_analytics_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
campaign_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned. ")] = None,
_request_timeout: Union[
None,
@@ -11916,13 +11840,13 @@ def export_application_campaign_analytics_without_preload_content(
) -> RESTResponseType:
"""Export Application analytics aggregated by campaign
- Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
+ Download a CSV file containing analytics data aggregated by campaign for the campaigns of an Application. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `campaign_id`: The ID of the campaign. This column also contains labels for the [total and influenced values](https://docs.talon.one/docs/product/campaigns/analytics/application-dashboard#display-the-analytics-data). - `start_date`: The start of the aggregation time frame in UTC. - `end_date`: The end of the aggregation time frame in UTC. - `revenue`: The total, pre-discount value of all items purchased in a customer session. - `sessions`: The number of all closed sessions. - `average_session_value`: The average customer session value, calculated by dividing the revenue value by the number of sessions. - `average_items_per_session`: The number of items from sessions divided by the number of sessions. - `coupons`: The number of times a coupon was successfully redeemed in sessions. - `discounts`: The total value of discounts given for cart items in sessions.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param campaign_ids: Filter by one or more Campaign IDs, separated by a comma. **Note:** If no campaigns are specified, data for all the campaigns in the Application is returned.
:type campaign_ids: List[str]
@@ -12046,8 +11970,6 @@ def _export_application_campaign_analytics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -12088,7 +12010,7 @@ def export_audiences_memberships(
) -> str:
"""Export audience members
- Download a CSV file containing the integration IDs of the members of an audience. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
+ Download a CSV file containing the integration IDs of the members of an audience. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -12158,7 +12080,7 @@ def export_audiences_memberships_with_http_info(
) -> ApiResponse[str]:
"""Export audience members
- Download a CSV file containing the integration IDs of the members of an audience. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
+ Download a CSV file containing the integration IDs of the members of an audience. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -12228,7 +12150,7 @@ def export_audiences_memberships_without_preload_content(
) -> RESTResponseType:
"""Export audience members
- Download a CSV file containing the integration IDs of the members of an audience. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
+ Download a CSV file containing the integration IDs of the members of an audience. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The file contains the following column: - `profileintegrationid`: The integration ID of the customer profile.
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -12318,8 +12240,6 @@ def _export_audiences_memberships_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -12363,7 +12283,7 @@ def export_campaign_store_budgets(
) -> str:
"""Export campaign store budgets
- Download a CSV file containing the store budgets for a given campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
+ Download a CSV file containing the store budgets for a given campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12445,7 +12365,7 @@ def export_campaign_store_budgets_with_http_info(
) -> ApiResponse[str]:
"""Export campaign store budgets
- Download a CSV file containing the store budgets for a given campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
+ Download a CSV file containing the store budgets for a given campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12527,7 +12447,7 @@ def export_campaign_store_budgets_without_preload_content(
) -> RESTResponseType:
"""Export campaign store budgets
- Download a CSV file containing the store budgets for a given campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
+ Download a CSV file containing the store budgets for a given campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `store_integration_id`: The identifier of the store. - `limit`: The budget limit for the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12639,8 +12559,6 @@ def _export_campaign_store_budgets_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -12682,7 +12600,7 @@ def export_campaign_stores(
) -> str:
"""Export stores
- Download a CSV file containing the stores linked to a specific campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
+ Download a CSV file containing the stores linked to a specific campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12756,7 +12674,7 @@ def export_campaign_stores_with_http_info(
) -> ApiResponse[str]:
"""Export stores
- Download a CSV file containing the stores linked to a specific campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
+ Download a CSV file containing the stores linked to a specific campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12830,7 +12748,7 @@ def export_campaign_stores_without_preload_content(
) -> RESTResponseType:
"""Export stores
- Download a CSV file containing the stores linked to a specific campaign. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
+ Download a CSV file containing the stores linked to a specific campaign. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following column: - `store_integration_id`: The identifier of the store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -12926,8 +12844,6 @@ def _export_campaign_stores_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -12954,7 +12870,7 @@ def export_collection_items(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -12970,13 +12886,13 @@ def export_collection_items(
) -> str:
"""Export campaign-level collection's items
- Download a CSV file containing items from a given campaign-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given campaign-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -13031,7 +12947,7 @@ def export_collection_items_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -13047,13 +12963,13 @@ def export_collection_items_with_http_info(
) -> ApiResponse[str]:
"""Export campaign-level collection's items
- Download a CSV file containing items from a given campaign-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given campaign-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -13108,7 +13024,7 @@ def export_collection_items_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -13124,13 +13040,13 @@ def export_collection_items_without_preload_content(
) -> RESTResponseType:
"""Export campaign-level collection's items
- Download a CSV file containing items from a given campaign-level collection. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing items from a given campaign-level collection. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -13225,8 +13141,6 @@ def _export_collection_items_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -13281,7 +13195,7 @@ def export_coupons(
) -> str:
"""Export coupons
- Download a CSV file containing the coupons that match the given properties. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
+ Download a CSV file containing the coupons that match the given properties. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -13404,7 +13318,7 @@ def export_coupons_with_http_info(
) -> ApiResponse[str]:
"""Export coupons
- Download a CSV file containing the coupons that match the given properties. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
+ Download a CSV file containing the coupons that match the given properties. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -13527,7 +13441,7 @@ def export_coupons_without_preload_content(
) -> RESTResponseType:
"""Export coupons
- Download a CSV file containing the coupons that match the given properties. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
+ Download a CSV file containing the coupons that match the given properties. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file can contain the following columns: - `accountid`: The ID of your deployment. - `applicationid`: The ID of the Application this coupon is related to. - `attributes`: A json object describing _custom_ referral attribute names and their values. - `batchid`: The ID of the batch this coupon is part of. - `campaignid`: The ID of the campaign this coupon is related to. - `counter`: The number of times this coupon has been redeemed. - `created`: The creation date in RFC3339 of the coupon code. - `deleted`: Whether the coupon code is deleted. - `deleted_changelogid`: The ID of the delete event in the logs. - `discount_counter`: The amount of discount given by this coupon. - `discount_limitval`: The maximum discount amount that can be given be this coupon. - `expirydate`: The end date in RFC3339 of the code redemption period. - `id`: The internal ID of the coupon code. - `importid`: The ID of the import job that created this coupon. - `is_reservation_mandatory`: Whether this coupon requires a reservation to be redeemed. - `limits`: The limits set on this coupon. - `limitval`: The maximum number of redemptions of this code. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `referralid`: The ID of the referral code that triggered the creation of this coupon (create coupon effect). - `reservation`: Whether the coupon can be reserved for multiple customers. - `reservation_counter`: How many times this coupon has been reserved. - `reservation_limitval`: The maximum of number of reservations this coupon can have. - `startdate`: The start date in RFC3339 of the code redemption period. - `value`: The coupon code.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -13744,8 +13658,6 @@ def _export_coupons_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -13791,7 +13703,7 @@ def export_customer_sessions(
) -> str:
"""Export customer sessions
- Download a CSV file containing the customer sessions that match the request. **Important:** Archived sessions cannot be exported. See the [retention policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
+ Download a CSV file containing the customer sessions that match the request. > [!important] Archived sessions cannot be exported. See the [retention > policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -13878,7 +13790,7 @@ def export_customer_sessions_with_http_info(
) -> ApiResponse[str]:
"""Export customer sessions
- Download a CSV file containing the customer sessions that match the request. **Important:** Archived sessions cannot be exported. See the [retention policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
+ Download a CSV file containing the customer sessions that match the request. > [!important] Archived sessions cannot be exported. See the [retention > policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -13965,7 +13877,7 @@ def export_customer_sessions_without_preload_content(
) -> RESTResponseType:
"""Export customer sessions
- Download a CSV file containing the customer sessions that match the request. **Important:** Archived sessions cannot be exported. See the [retention policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
+ Download a CSV file containing the customer sessions that match the request. > [!important] Archived sessions cannot be exported. See the [retention > policy](https://docs.talon.one/docs/dev/server-infrastructure-and-data-retention). > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). - `id`: The internal ID of the session. - `firstsession`: Whether this is a first session. - `integrationid`: The integration ID of the session. - `applicationid`: The ID of the Application. - `profileid`: The internal ID of the customer profile. - `profileintegrationid`: The integration ID of the customer profile. - `created`: The timestamp when the session was created. - `state`: The [state](https://docs.talon.one/docs/dev/concepts/entities/customer-sessions#customer-session-states) of the session. - `cartitems`: The cart items in the session. - `discounts`: The discounts in the session. - `total`: The total value of cart items and additional costs in the session, before any discounts are applied. - `attributes`: The attributes set in the session. - `closedat`: Timestamp when the session was closed. - `cancelledat`: Timestamp when the session was cancelled. - `referral`: The referral code in the session. - `identifiers`: The identifiers in the session. - `additional_costs`: The [additional costs](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs) in the session. - `updated`: Timestamp of the last session update. - `store_integration_id`: The integration ID of the store. - `coupons`: Coupon codes in the session.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -14110,8 +14022,6 @@ def _export_customer_sessions_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -14409,8 +14319,6 @@ def _export_customers_tiers_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -14455,7 +14363,7 @@ def export_effects(
) -> str:
"""Export triggered effects
- Download a CSV file containing the triggered effects that match the given attributes. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
+ Download a CSV file containing the triggered effects that match the given attributes. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -14538,7 +14446,7 @@ def export_effects_with_http_info(
) -> ApiResponse[str]:
"""Export triggered effects
- Download a CSV file containing the triggered effects that match the given attributes. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
+ Download a CSV file containing the triggered effects that match the given attributes. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -14621,7 +14529,7 @@ def export_effects_without_preload_content(
) -> RESTResponseType:
"""Export triggered effects
- Download a CSV file containing the triggered effects that match the given attributes. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
+ Download a CSV file containing the triggered effects that match the given attributes. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `applicationid`: The ID of the Application. - `campaignid`: The ID of the campaign. - `couponid`: The ID of the coupon, when applicable to the effect. - `created`: The timestamp of the effect. - `event_type`: The name of the event. See the [docs](https://docs.talon.one/docs/dev/concepts/entities/events). - `eventid`: The internal ID of the effect. - `name`: The effect name. See the [docs](https://docs.talon.one/docs/dev/integration-api/api-effects). - `profileintegrationid`: The ID of the customer profile, when applicable. - `props`: The [properties](https://docs.talon.one/docs/dev/integration-api/api-effects) of the effect. - `ruleindex`: The index of the rule. - `rulesetid`: The ID of the rule set. - `sessionid`: The internal ID of the session that triggered the effect. - `profileid`: The internal ID of the customer profile. - `sessionintegrationid`: The integration ID of the session. - `total_revenue`: The total revenue. - `store_integration_id`: The integration ID of the store. You choose this ID when you create a store.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -14758,8 +14666,6 @@ def _export_effects_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -14785,7 +14691,7 @@ def _export_effects_serialize(
def export_loyalty_balance(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -14801,11 +14707,11 @@ def export_loyalty_balance(
) -> str:
"""(Deprecated) Export customer loyalty balance to CSV
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -14859,7 +14765,7 @@ def export_loyalty_balance(
def export_loyalty_balance_with_http_info(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -14875,11 +14781,11 @@ def export_loyalty_balance_with_http_info(
) -> ApiResponse[str]:
"""(Deprecated) Export customer loyalty balance to CSV
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -14933,7 +14839,7 @@ def export_loyalty_balance_with_http_info(
def export_loyalty_balance_without_preload_content(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -14949,11 +14855,11 @@ def export_loyalty_balance_without_preload_content(
) -> RESTResponseType:
"""(Deprecated) Export customer loyalty balance to CSV
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ To export customer loyalty balances to CSV, use the [Export customer loyalty balances to CSV](/management-api#tag/Loyalty/operation/exportLoyaltyBalances) endpoint. Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15056,8 +14962,6 @@ def _export_loyalty_balance_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -15083,7 +14987,7 @@ def _export_loyalty_balance_serialize(
def export_loyalty_balances(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15099,11 +15003,11 @@ def export_loyalty_balances(
) -> str:
"""Export customer loyalty balances
- Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
+ Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subledger, when applicable. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15156,7 +15060,7 @@ def export_loyalty_balances(
def export_loyalty_balances_with_http_info(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15172,11 +15076,11 @@ def export_loyalty_balances_with_http_info(
) -> ApiResponse[str]:
"""Export customer loyalty balances
- Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
+ Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subledger, when applicable. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15229,7 +15133,7 @@ def export_loyalty_balances_with_http_info(
def export_loyalty_balances_without_preload_content(
self,
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15245,11 +15149,11 @@ def export_loyalty_balances_without_preload_content(
) -> RESTResponseType:
"""Export customer loyalty balances
- Download a CSV file containing the balance of each customer in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
+ Download a CSV file containing the balance of each customer in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subledger, when applicable. - `profileIntegrationID`: The integration ID of the customer profile. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points. - `currentTier`: The tier that the customer is in at the time of the export.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. > - This parameter does not affect the `currentTier` field in the CSV file, which shows the customer's tier at the time of export.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15351,8 +15255,6 @@ def _export_loyalty_balances_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -15378,7 +15280,7 @@ def _export_loyalty_balances_serialize(
def export_loyalty_card_balances(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15394,11 +15296,11 @@ def export_loyalty_card_balances(
) -> str:
"""Export all card transaction logs
- Download a CSV file containing the balances of all cards in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
+ Download a CSV file containing the balances of all cards in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15451,7 +15353,7 @@ def export_loyalty_card_balances(
def export_loyalty_card_balances_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15467,11 +15369,11 @@ def export_loyalty_card_balances_with_http_info(
) -> ApiResponse[str]:
"""Export all card transaction logs
- Download a CSV file containing the balances of all cards in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
+ Download a CSV file containing the balances of all cards in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15524,7 +15426,7 @@ def export_loyalty_card_balances_with_http_info(
def export_loyalty_card_balances_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -15540,11 +15442,11 @@ def export_loyalty_card_balances_without_preload_content(
) -> RESTResponseType:
"""Export all card transaction logs
- Download a CSV file containing the balances of all cards in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
+ Download a CSV file containing the balances of all cards in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `loyaltySubledger`: The name of the subdleger, when applicatble. - `cardIdentifier`: The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `cardState`:The state of the loyalty card. It can be `active` or `inactive`. - `currentBalance`: The current point balance. - `pendingBalance`: The number of pending points. - `expiredBalance`: The number of expired points. - `spentBalance`: The number of spent points.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -15646,8 +15548,6 @@ def _export_loyalty_card_balances_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -15674,8 +15574,8 @@ def export_loyalty_card_ledger(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -15692,15 +15592,15 @@ def export_loyalty_card_ledger(
) -> str:
"""Export card's ledger log
- Download a CSV file containing a loyalty card ledger log of the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing a loyalty card ledger log of the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -15759,8 +15659,8 @@ def export_loyalty_card_ledger_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -15777,15 +15677,15 @@ def export_loyalty_card_ledger_with_http_info(
) -> ApiResponse[str]:
"""Export card's ledger log
- Download a CSV file containing a loyalty card ledger log of the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing a loyalty card ledger log of the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -15844,8 +15744,8 @@ def export_loyalty_card_ledger_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -15862,15 +15762,15 @@ def export_loyalty_card_ledger_without_preload_content(
) -> RESTResponseType:
"""Export card's ledger log
- Download a CSV file containing a loyalty card ledger log of the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/).
+ Download a CSV file containing a loyalty card ledger log of the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files).
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -15999,8 +15899,6 @@ def _export_loyalty_card_ledger_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -16027,8 +15925,8 @@ def export_loyalty_cards(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
batch_id: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty card batch ID.")] = None,
- created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
- created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
+ created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
+ created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -16045,15 +15943,15 @@ def export_loyalty_cards(
) -> str:
"""Export loyalty cards
- Download a CSV file containing the loyalty cards from a specified loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in.
+ Download a CSV file containing the loyalty cards from a specified loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in. - `attributes`: The custom attributes of this loyalty card. Currently, this feature is only available upon request.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param batch_id: Filter results by loyalty card batch ID.
:type batch_id: str
- :param created_before: Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_before: Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_before: datetime
- :param created_after: Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_after: Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_after: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -16112,8 +16010,8 @@ def export_loyalty_cards_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
batch_id: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty card batch ID.")] = None,
- created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
- created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
+ created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
+ created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -16130,15 +16028,15 @@ def export_loyalty_cards_with_http_info(
) -> ApiResponse[str]:
"""Export loyalty cards
- Download a CSV file containing the loyalty cards from a specified loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in.
+ Download a CSV file containing the loyalty cards from a specified loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in. - `attributes`: The custom attributes of this loyalty card. Currently, this feature is only available upon request.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param batch_id: Filter results by loyalty card batch ID.
:type batch_id: str
- :param created_before: Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_before: Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_before: datetime
- :param created_after: Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_after: Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_after: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -16197,8 +16095,8 @@ def export_loyalty_cards_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
batch_id: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty card batch ID.")] = None,
- created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
- created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string. ")] = None,
+ created_before: Annotated[Optional[datetime], Field(description="Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
+ created_after: Annotated[Optional[datetime], Field(description="Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string. ")] = None,
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
_request_timeout: Union[
None,
@@ -16215,15 +16113,15 @@ def export_loyalty_cards_without_preload_content(
) -> RESTResponseType:
"""Export loyalty cards
- Download a CSV file containing the loyalty cards from a specified loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in.
+ Download a CSV file containing the loyalty cards from a specified loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `identifier`: The unique identifier of the loyalty card. - `created`: The date and time the loyalty card was created. - `status`: The status of the loyalty card. - `userpercardlimit`: The maximum number of customer profiles that can be linked to the card. - `customerprofileids`: Integration IDs of the customer profiles linked to the card. - `blockreason`: The reason for transferring and blocking the loyalty card. - `generated`: An indicator of whether the loyalty card was generated. - `batchid`: The ID of the batch the loyalty card is in. - `attributes`: The custom attributes of this loyalty card. Currently, this feature is only available upon request.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param batch_id: Filter results by loyalty card batch ID.
:type batch_id: str
- :param created_before: Only return loyalty cards created before this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_before: Only return loyalty cards created before this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_before: datetime
- :param created_after: Only return loyalty cards created after this timestamp. **Note:** - This must be an RFC3339 timestamp string.
+ :param created_after: Only return loyalty cards created after this timestamp. **Note:** This must be an RFC3339 timestamp string.
:type created_after: datetime
:param date_format: Determines the format of dates in the export document.
:type date_format: str
@@ -16354,8 +16252,6 @@ def _export_loyalty_cards_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -16396,7 +16292,7 @@ def export_loyalty_join_dates(
) -> str:
"""Export customers' loyalty program join dates
- Download a CSV file containing the join dates of all customers in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
+ Download a CSV file containing the join dates of all customers in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
:param loyalty_program_id: The identifier of the loyalty program. (required)
:type loyalty_program_id: str
@@ -16465,7 +16361,7 @@ def export_loyalty_join_dates_with_http_info(
) -> ApiResponse[str]:
"""Export customers' loyalty program join dates
- Download a CSV file containing the join dates of all customers in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
+ Download a CSV file containing the join dates of all customers in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
:param loyalty_program_id: The identifier of the loyalty program. (required)
:type loyalty_program_id: str
@@ -16534,7 +16430,7 @@ def export_loyalty_join_dates_without_preload_content(
) -> RESTResponseType:
"""Export customers' loyalty program join dates
- Download a CSV file containing the join dates of all customers in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
+ Download a CSV file containing the join dates of all customers in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `loyaltyProgramID`: The ID of the loyalty program. - `profileIntegrationID`: The integration ID of the customer profile. - `joinDate`: The customer's loyalty program join date in RFC3339 format.
:param loyalty_program_id: The identifier of the loyalty program. (required)
:type loyalty_program_id: str
@@ -16623,8 +16519,6 @@ def _export_loyalty_join_dates_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -16649,8 +16543,8 @@ def _export_loyalty_join_dates_serialize(
@validate_call
def export_loyalty_ledger(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
@@ -16669,11 +16563,11 @@ def export_loyalty_ledger(
) -> str:
"""Export customer's transaction logs
- Download a CSV file containing a customer's transaction logs in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
+ Download a CSV file containing a customer's transaction logs in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -16732,8 +16626,8 @@ def export_loyalty_ledger(
@validate_call
def export_loyalty_ledger_with_http_info(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
@@ -16752,11 +16646,11 @@ def export_loyalty_ledger_with_http_info(
) -> ApiResponse[str]:
"""Export customer's transaction logs
- Download a CSV file containing a customer's transaction logs in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
+ Download a CSV file containing a customer's transaction logs in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -16815,8 +16709,8 @@ def export_loyalty_ledger_with_http_info(
@validate_call
def export_loyalty_ledger_without_preload_content(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
loyalty_program_id: Annotated[StrictStr, Field(description="The identifier for the loyalty program.")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
date_format: Annotated[Optional[StrictStr], Field(description="Determines the format of dates in the export document.")] = None,
@@ -16835,11 +16729,11 @@ def export_loyalty_ledger_without_preload_content(
) -> RESTResponseType:
"""Export customer's transaction logs
- Download a CSV file containing a customer's transaction logs in the loyalty program. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
+ Download a CSV file containing a customer's transaction logs in the loyalty program. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The generated file can contain the following columns: - `customerprofileid`: The ID of the profile. - `customersessionid`: The ID of the customer session. - `rulesetid`: The ID of the rule set. - `rulename`: The name of the rule. - `programid`: The ID of the loyalty program. - `type`: The transaction type, such as `addition` or `subtraction`. - `name`: The reason for the transaction. - `subledgerid`: The ID of the subledger, when applicable. - `startdate`: The start date of the program. - `expirydate`: The expiration date of the program. - `id`: The ID of the transaction. - `created`: The timestamp of the creation of the loyalty program. - `amount`: The number of points in that transaction. - `archived`: Whether the session related to the transaction is archived. - `campaignid`: The ID of the campaign. - `flags`: The flags of the transaction, when applicable. The `createsNegativeBalance` flag indicates whether the transaction results in a negative balance. - `transactionUUID`: Unique identifier of the transaction in the UUID format.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -16970,8 +16864,6 @@ def _export_loyalty_ledger_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -17014,7 +16906,7 @@ def export_pool_giveaways(
) -> str:
"""Export giveaway codes of a giveaway pool
- Download a CSV file containing the giveaway codes of a specific giveaway pool. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
+ Download a CSV file containing the giveaway codes of a specific giveaway pool. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -17090,7 +16982,7 @@ def export_pool_giveaways_with_http_info(
) -> ApiResponse[str]:
"""Export giveaway codes of a giveaway pool
- Download a CSV file containing the giveaway codes of a specific giveaway pool. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
+ Download a CSV file containing the giveaway codes of a specific giveaway pool. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -17166,7 +17058,7 @@ def export_pool_giveaways_without_preload_content(
) -> RESTResponseType:
"""Export giveaway codes of a giveaway pool
- Download a CSV file containing the giveaway codes of a specific giveaway pool. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
+ Download a CSV file containing the giveaway codes of a specific giveaway pool. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `id`: The internal ID of the giveaway. - `poolid`: The internal ID of the giveaway pool. - `code`: The giveaway code. - `startdate`: The validity start date in RFC3339 of the giveaway (can be empty). - `enddate`: The validity end date in RFC3339 of the giveaway (can be empty). - `attributes`: Any custom attributes associated with the giveaway code (can be empty). - `used`: An indication of whether the giveaway is already awarded. - `importid`: The ID of the import which created the giveaway. - `created`: The creation time of the giveaway code. - `profileintegrationid`: The third-party integration ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded. - `profileid`: The internal ID of the customer profile that was awarded the giveaway. Can be empty if the giveaway was not awarded or an internal ID does not exist.
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -17288,8 +17180,6 @@ def _export_pool_giveaways_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -17337,7 +17227,7 @@ def export_referrals(
) -> str:
"""Export referrals
- Download a CSV file containing the referrals that match the given parameters. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
+ Download a CSV file containing the referrals that match the given parameters. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -17432,7 +17322,7 @@ def export_referrals_with_http_info(
) -> ApiResponse[str]:
"""Export referrals
- Download a CSV file containing the referrals that match the given parameters. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
+ Download a CSV file containing the referrals that match the given parameters. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -17527,7 +17417,7 @@ def export_referrals_without_preload_content(
) -> RESTResponseType:
"""Export referrals
- Download a CSV file containing the referrals that match the given parameters. **Tip:** If the exported CSV file is too large to view, you can [split it into multiple files](https://www.makeuseof.com/tag/how-to-split-a-huge-csv-excel-workbook-into-seperate-files/). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
+ Download a CSV file containing the referrals that match the given parameters. > [!tip] If the exported CSV file is too large to view, you can > [split it into multiple files](https://www.google.com/search?q=split+CSV+into+multiple+files). The CSV file contains the following columns: - `code`: The referral code. - `advocateprofileintegrationid`: The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A json object describing _custom_ referral attribute names and their values.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -17688,8 +17578,6 @@ def _export_referrals_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -18004,8 +17892,6 @@ def _generate_coupon_rejections_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -18031,8 +17917,8 @@ def _generate_coupon_rejections_serialize(
def get_access_logs_without_total_count(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
path: Annotated[Optional[StrictStr], Field(description="Only return results where the request path matches the given regular expression.")] = None,
method: Annotated[Optional[StrictStr], Field(description="Only return results where the request method matches the given regular expression.")] = None,
status: Annotated[Optional[StrictStr], Field(description="Filter results by HTTP status codes.")] = None,
@@ -18058,9 +17944,9 @@ def get_access_logs_without_total_count(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param path: Only return results where the request path matches the given regular expression.
:type path: str
@@ -18130,8 +18016,8 @@ def get_access_logs_without_total_count(
def get_access_logs_without_total_count_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
path: Annotated[Optional[StrictStr], Field(description="Only return results where the request path matches the given regular expression.")] = None,
method: Annotated[Optional[StrictStr], Field(description="Only return results where the request method matches the given regular expression.")] = None,
status: Annotated[Optional[StrictStr], Field(description="Filter results by HTTP status codes.")] = None,
@@ -18157,9 +18043,9 @@ def get_access_logs_without_total_count_with_http_info(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param path: Only return results where the request path matches the given regular expression.
:type path: str
@@ -18229,8 +18115,8 @@ def get_access_logs_without_total_count_with_http_info(
def get_access_logs_without_total_count_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
path: Annotated[Optional[StrictStr], Field(description="Only return results where the request path matches the given regular expression.")] = None,
method: Annotated[Optional[StrictStr], Field(description="Only return results where the request method matches the given regular expression.")] = None,
status: Annotated[Optional[StrictStr], Field(description="Filter results by HTTP status codes.")] = None,
@@ -18256,9 +18142,9 @@ def get_access_logs_without_total_count_without_preload_content(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param path: Only return results where the request path matches the given regular expression.
:type path: str
@@ -18421,8 +18307,6 @@ def _get_access_logs_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -18447,7 +18331,7 @@ def _get_access_logs_without_total_count_serialize(
@validate_call
def get_account(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18465,7 +18349,7 @@ def get_account(
Return the details of your companies Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18514,7 +18398,7 @@ def get_account(
@validate_call
def get_account_with_http_info(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18532,7 +18416,7 @@ def get_account_with_http_info(
Return the details of your companies Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18581,7 +18465,7 @@ def get_account_with_http_info(
@validate_call
def get_account_without_preload_content(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18599,7 +18483,7 @@ def get_account_without_preload_content(
Return the details of your companies Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18684,8 +18568,6 @@ def _get_account_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -18710,7 +18592,7 @@ def _get_account_serialize(
@validate_call
def get_account_analytics(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18728,7 +18610,7 @@ def get_account_analytics(
Return the analytics of your Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18777,7 +18659,7 @@ def get_account_analytics(
@validate_call
def get_account_analytics_with_http_info(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18795,7 +18677,7 @@ def get_account_analytics_with_http_info(
Return the analytics of your Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18844,7 +18726,7 @@ def get_account_analytics_with_http_info(
@validate_call
def get_account_analytics_without_preload_content(
self,
- account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. ")],
+ account_id: Annotated[StrictInt, Field(description="The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18862,7 +18744,7 @@ def get_account_analytics_without_preload_content(
Return the analytics of your Talon.One account.
- :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#operation/getUsers) endpoint in the `accountId` property. (required)
+ :param account_id: The identifier of the account. Retrieve it via the [List users in account](https://docs.talon.one/management-api#tag/Accounts-and-users/operation/getUsers) endpoint in the `accountId` property. (required)
:type account_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -18947,8 +18829,6 @@ def _get_account_analytics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -18973,7 +18853,7 @@ def _get_account_analytics_serialize(
@validate_call
def get_account_collection(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -18991,7 +18871,7 @@ def get_account_collection(
Retrieve a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -19041,7 +18921,7 @@ def get_account_collection(
@validate_call
def get_account_collection_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -19059,7 +18939,7 @@ def get_account_collection_with_http_info(
Retrieve a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -19109,7 +18989,7 @@ def get_account_collection_with_http_info(
@validate_call
def get_account_collection_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -19127,7 +19007,7 @@ def get_account_collection_without_preload_content(
Retrieve a given account-level collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -19213,8 +19093,6 @@ def _get_account_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -19512,8 +19390,6 @@ def _get_achievement_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -19775,8 +19651,6 @@ def _get_additional_cost_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -20074,8 +19948,6 @@ def _get_additional_costs_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -20337,8 +20209,6 @@ def _get_application_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -20600,8 +20470,6 @@ def _get_application_api_health_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -20627,7 +20495,7 @@ def _get_application_api_health_serialize(
def get_application_customer(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -20647,7 +20515,7 @@ def get_application_customer(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -20698,7 +20566,7 @@ def get_application_customer(
def get_application_customer_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -20718,7 +20586,7 @@ def get_application_customer_with_http_info(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -20769,7 +20637,7 @@ def get_application_customer_with_http_info(
def get_application_customer_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -20789,7 +20657,7 @@ def get_application_customer_without_preload_content(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -20878,8 +20746,6 @@ def _get_application_customer_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -21224,8 +21090,6 @@ def _get_application_customer_friends_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -21555,8 +21419,6 @@ def _get_application_customers_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -21897,8 +21759,6 @@ def _get_application_customers_by_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -22211,8 +22071,6 @@ def _get_application_event_types_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -22747,8 +22605,6 @@ def _get_application_events_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -23025,8 +22881,6 @@ def _get_application_session_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -23510,8 +23364,6 @@ def _get_application_sessions_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -23809,8 +23661,6 @@ def _get_applications_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -24072,8 +23922,6 @@ def _get_attribute_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -24456,8 +24304,6 @@ def _get_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -24790,8 +24636,6 @@ def _get_audience_memberships_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -25106,8 +24950,6 @@ def _get_audiences_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -25388,8 +25230,6 @@ def _get_audiences_analytics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -25666,8 +25506,6 @@ def _get_campaign_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -25694,8 +25532,8 @@ def get_campaign_analytics(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
granularity: Annotated[Optional[StrictStr], Field(description="The time interval between the results in the returned time-series.")] = None,
_request_timeout: Union[
None,
@@ -25718,9 +25556,9 @@ def get_campaign_analytics(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param granularity: The time interval between the results in the returned time-series.
:type granularity: str
@@ -25777,8 +25615,8 @@ def get_campaign_analytics_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
granularity: Annotated[Optional[StrictStr], Field(description="The time interval between the results in the returned time-series.")] = None,
_request_timeout: Union[
None,
@@ -25801,9 +25639,9 @@ def get_campaign_analytics_with_http_info(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param granularity: The time interval between the results in the returned time-series.
:type granularity: str
@@ -25860,8 +25698,8 @@ def get_campaign_analytics_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
granularity: Annotated[Optional[StrictStr], Field(description="The time interval between the results in the returned time-series.")] = None,
_request_timeout: Union[
None,
@@ -25884,9 +25722,9 @@ def get_campaign_analytics_without_preload_content(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param granularity: The time interval between the results in the returned time-series.
:type granularity: str
@@ -26013,8 +25851,6 @@ def _get_campaign_analytics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -26372,8 +26208,6 @@ def _get_campaign_by_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -26635,8 +26469,6 @@ def _get_campaign_group_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -26934,8 +26766,6 @@ def _get_campaign_groups_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -27301,8 +27131,6 @@ def _get_campaign_templates_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -27876,8 +27704,6 @@ def _get_campaigns_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -28329,8 +28155,6 @@ def _get_changes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -28357,7 +28181,7 @@ def get_collection(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -28379,7 +28203,7 @@ def get_collection(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -28433,7 +28257,7 @@ def get_collection_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -28455,7 +28279,7 @@ def get_collection_with_http_info(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -28509,7 +28333,7 @@ def get_collection_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -28531,7 +28355,7 @@ def get_collection_without_preload_content(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -28625,8 +28449,6 @@ def _get_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -28651,7 +28473,7 @@ def _get_collection_serialize(
@validate_call
def get_collection_items(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -28671,7 +28493,7 @@ def get_collection_items(
Retrieve items from a given collection. You can retrieve items from both account-level collections and campaign-level collections using this endpoint.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -28727,7 +28549,7 @@ def get_collection_items(
@validate_call
def get_collection_items_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -28747,7 +28569,7 @@ def get_collection_items_with_http_info(
Retrieve items from a given collection. You can retrieve items from both account-level collections and campaign-level collections using this endpoint.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -28803,7 +28625,7 @@ def get_collection_items_with_http_info(
@validate_call
def get_collection_items_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -28823,7 +28645,7 @@ def get_collection_items_without_preload_content(
Retrieve items from a given collection. You can retrieve items from both account-level collections and campaign-level collections using this endpoint.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -28925,8 +28747,6 @@ def _get_collection_items_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -29563,8 +29383,6 @@ def _get_coupons_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -29589,10 +29407,10 @@ def _get_coupons_without_total_count_serialize(
@validate_call
def get_customer_activity_report(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -29612,13 +29430,13 @@ def get_customer_activity_report(
Fetch the summary report of a given customer in the given application, in a time range.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -29676,10 +29494,10 @@ def get_customer_activity_report(
@validate_call
def get_customer_activity_report_with_http_info(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -29699,13 +29517,13 @@ def get_customer_activity_report_with_http_info(
Fetch the summary report of a given customer in the given application, in a time range.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -29763,10 +29581,10 @@ def get_customer_activity_report_with_http_info(
@validate_call
def get_customer_activity_report_without_preload_content(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
_request_timeout: Union[
@@ -29786,13 +29604,13 @@ def get_customer_activity_report_without_preload_content(
Fetch the summary report of a given customer in the given application, in a time range.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -29927,8 +29745,6 @@ def _get_customer_activity_report_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -29953,8 +29769,8 @@ def _get_customer_activity_report_serialize(
@validate_call
def get_customer_activity_reports_without_total_count(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
@@ -29980,9 +29796,9 @@ def get_customer_activity_reports_without_total_count(
Fetch summary reports for all application customers based on a time range. Instead of having the total number of results in the response, this endpoint only mentions whether there are more results.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -30056,8 +29872,8 @@ def get_customer_activity_reports_without_total_count(
@validate_call
def get_customer_activity_reports_without_total_count_with_http_info(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
@@ -30083,9 +29899,9 @@ def get_customer_activity_reports_without_total_count_with_http_info(
Fetch summary reports for all application customers based on a time range. Instead of having the total number of results in the response, this endpoint only mentions whether there are more results.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -30159,8 +29975,8 @@ def get_customer_activity_reports_without_total_count_with_http_info(
@validate_call
def get_customer_activity_reports_without_total_count_without_preload_content(
self,
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
@@ -30186,9 +30002,9 @@ def get_customer_activity_reports_without_total_count_without_preload_content(
Fetch summary reports for all application customers based on a time range. Instead of having the total number of results in the response, this endpoint only mentions whether there are more results.
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -30361,8 +30177,6 @@ def _get_customer_activity_reports_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -30388,7 +30202,7 @@ def _get_customer_activity_reports_without_total_count_serialize(
def get_customer_analytics(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
sort: Annotated[Optional[StrictStr], Field(description="The field by which results should be sorted. By default, results are sorted in ascending order. To sort them in descending order, prefix the field name with `-`. **Note:** You may not be able to use all fields for sorting. This is due to performance limitations. ")] = None,
@@ -30411,7 +30225,7 @@ def get_customer_analytics(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -30471,7 +30285,7 @@ def get_customer_analytics(
def get_customer_analytics_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
sort: Annotated[Optional[StrictStr], Field(description="The field by which results should be sorted. By default, results are sorted in ascending order. To sort them in descending order, prefix the field name with `-`. **Note:** You may not be able to use all fields for sorting. This is due to performance limitations. ")] = None,
@@ -30494,7 +30308,7 @@ def get_customer_analytics_with_http_info(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -30554,7 +30368,7 @@ def get_customer_analytics_with_http_info(
def get_customer_analytics_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
sort: Annotated[Optional[StrictStr], Field(description="The field by which results should be sorted. By default, results are sorted in ascending order. To sort them in descending order, prefix the field name with `-`. **Note:** You may not be able to use all fields for sorting. This is due to performance limitations. ")] = None,
@@ -30577,7 +30391,7 @@ def get_customer_analytics_without_preload_content(
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param page_size: The number of items in the response.
:type page_size: int
@@ -30690,8 +30504,6 @@ def _get_customer_analytics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -30716,7 +30528,7 @@ def _get_customer_analytics_serialize(
@validate_call
def get_customer_profile(
self,
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -30732,9 +30544,9 @@ def get_customer_profile(
) -> CustomerProfile:
"""Get customer profile
- Return the details of the specified customer profile. Performance tips
You can retrieve the same information via the Integration API, which can save you extra API requests. consider these options: - Request the customer profile to be part of the response content using [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
+ Return the details of the specified customer profile. > [!note] > You can retrieve the same information via the Integration API, which can save you extra API requests. Consider these options: > - Request the customer profile to be part of the response content using > [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). > - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -30783,7 +30595,7 @@ def get_customer_profile(
@validate_call
def get_customer_profile_with_http_info(
self,
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -30799,9 +30611,9 @@ def get_customer_profile_with_http_info(
) -> ApiResponse[CustomerProfile]:
"""Get customer profile
- Return the details of the specified customer profile. Performance tips
You can retrieve the same information via the Integration API, which can save you extra API requests. consider these options: - Request the customer profile to be part of the response content using [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
+ Return the details of the specified customer profile. > [!note] > You can retrieve the same information via the Integration API, which can save you extra API requests. Consider these options: > - Request the customer profile to be part of the response content using > [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). > - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -30850,7 +30662,7 @@ def get_customer_profile_with_http_info(
@validate_call
def get_customer_profile_without_preload_content(
self,
- customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. ")],
+ customer_id: Annotated[StrictInt, Field(description="The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. ")],
_request_timeout: Union[
None,
Annotated[StrictFloat, Field(gt=0)],
@@ -30866,9 +30678,9 @@ def get_customer_profile_without_preload_content(
) -> RESTResponseType:
"""Get customer profile
- Return the details of the specified customer profile. Performance tips
You can retrieve the same information via the Integration API, which can save you extra API requests. consider these options: - Request the customer profile to be part of the response content using [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
+ Return the details of the specified customer profile. > [!note] > You can retrieve the same information via the Integration API, which can save you extra API requests. Consider these options: > - Request the customer profile to be part of the response content using > [Update Customer Session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). > - Send an empty update with the [Update Customer Profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint with `runRuleEngine=false`.
- :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#operation/getApplicationCustomers) endpoint. (required)
+ :param customer_id: The value of the `id` property of a customer profile. Get it with the [List Application's customers](https://docs.talon.one/management-api#tag/Customer-data/operation/getApplicationCustomers) endpoint. (required)
:type customer_id: int
:param _request_timeout: timeout setting for this request. If one
number provided, it will be total request
@@ -30953,8 +30765,6 @@ def _get_customer_profile_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -31305,8 +31115,6 @@ def _get_customer_profile_achievement_progress_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -31604,8 +31412,6 @@ def _get_customer_profiles_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -31931,8 +31737,6 @@ def _get_customers_by_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -31958,8 +31762,8 @@ def _get_customers_by_attributes_serialize(
def get_dashboard_statistics(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
_request_timeout: Union[
None,
@@ -31976,13 +31780,13 @@ def get_dashboard_statistics(
) -> GetDashboardStatistics200Response:
"""Get statistics for loyalty dashboard
- Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. **Important:** The returned data does not include the current day. All statistics are updated daily at 11:59 PM in the loyalty program time zone.
+ Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. > [!important] The returned data does not include the current day. All statistics > are updated daily at 11:59 PM in the loyalty program time zone.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -32037,8 +31841,8 @@ def get_dashboard_statistics(
def get_dashboard_statistics_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
_request_timeout: Union[
None,
@@ -32055,13 +31859,13 @@ def get_dashboard_statistics_with_http_info(
) -> ApiResponse[GetDashboardStatistics200Response]:
"""Get statistics for loyalty dashboard
- Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. **Important:** The returned data does not include the current day. All statistics are updated daily at 11:59 PM in the loyalty program time zone.
+ Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. > [!important] The returned data does not include the current day. All statistics > are updated daily at 11:59 PM in the loyalty program time zone.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -32116,8 +31920,8 @@ def get_dashboard_statistics_with_http_info(
def get_dashboard_statistics_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
- range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
- range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_start: Annotated[datetime, Field(description="Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
+ range_end: Annotated[datetime, Field(description="Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")],
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
_request_timeout: Union[
None,
@@ -32134,13 +31938,13 @@ def get_dashboard_statistics_without_preload_content(
) -> RESTResponseType:
"""Get statistics for loyalty dashboard
- Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. **Important:** The returned data does not include the current day. All statistics are updated daily at 11:59 PM in the loyalty program time zone.
+ Retrieve the statistics displayed on the specified loyalty program's dashboard, such as the total active points, pending points, spent points, and expired points. > [!important] The returned data does not include the current day. All statistics > are updated daily at 11:59 PM in the loyalty program time zone.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
- :param range_start: Only return results from after this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_start: Only return results from after this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_start: datetime
- :param range_end: Only return results from before this timestamp. **Note:** - This must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
+ :param range_end: Only return results from before this timestamp. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. (required)
:type range_end: datetime
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
@@ -32263,8 +32067,6 @@ def _get_dashboard_statistics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -32596,8 +32398,6 @@ def _get_event_types_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -32874,8 +32674,6 @@ def _get_experiment_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -33207,8 +33005,6 @@ def _get_exports_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -33494,8 +33290,6 @@ def _get_loyalty_card_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -33522,8 +33316,8 @@ def get_loyalty_card_transaction_logs(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
@@ -33550,9 +33344,9 @@ def get_loyalty_card_transaction_logs(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -33623,8 +33417,8 @@ def get_loyalty_card_transaction_logs_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
@@ -33651,9 +33445,9 @@ def get_loyalty_card_transaction_logs_with_http_info(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -33724,8 +33518,8 @@ def get_loyalty_card_transaction_logs_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_card_id: Annotated[str, Field(min_length=4, strict=True, max_length=108, description="Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. ")],
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
@@ -33752,9 +33546,9 @@ def get_loyalty_card_transaction_logs_without_preload_content(
:type loyalty_program_id: int
:param loyalty_card_id: Identifier of the loyalty card. You can get the identifier with the [List loyalty cards](https://docs.talon.one/management-api#tag/Loyalty-cards/operation/getLoyaltyCards) endpoint. **Important**: The loyalty card ID requires [URL encoding](https://www.w3schools.com/tags//ref_urlencode.asp) if it contains special characters. For example, you must encode `NewCard2026%` as `NewCard2026%25`. (required)
:type loyalty_card_id: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -33917,8 +33711,6 @@ def _get_loyalty_card_transaction_logs_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -34288,8 +34080,6 @@ def _get_loyalty_cards_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -34316,7 +34106,7 @@ def get_loyalty_ledger_balances(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -34335,13 +34125,13 @@ def get_loyalty_ledger_balances(
) -> LoyaltyBalancesWithTiers:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
@@ -34406,7 +34196,7 @@ def get_loyalty_ledger_balances_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -34425,13 +34215,13 @@ def get_loyalty_ledger_balances_with_http_info(
) -> ApiResponse[LoyaltyBalancesWithTiers]:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
@@ -34496,7 +34286,7 @@ def get_loyalty_ledger_balances_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
include_tiers: Annotated[Optional[StrictBool], Field(description="Indicates whether tier information is included in the response. When set to `true`, the response includes information about the current tier and the number of points required to move to next tier. ")] = None,
include_projected_tier: Annotated[Optional[StrictBool], Field(description="Indicates whether the customer's projected tier information is included in the response. When set to `true`, the response includes information about the customer's active points and the name of the projected tier. **Note** We recommend filtering by `subledgerId` for better performance. ")] = None,
@@ -34515,13 +34305,13 @@ def get_loyalty_ledger_balances_without_preload_content(
) -> RESTResponseType:
"""Get customer's loyalty balances
- Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. **Note**: If no filtering options are applied, you retrieve all loyalty balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
+ Retrieve loyalty ledger balances for the given Integration ID in the specified loyalty program. You can filter balances by date and subledger ID, and include tier-related information in the response. > [!note] If no filtering options are applied, you retrieve all loyalty > balances on the current date for the given integration ID. Loyalty balances are calculated when Talon.One receives your request using the points stored in our database, so retrieving a large number of balances at once can impact performance. For more information, see: - [Managing card-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/card-based/managing-loyalty-cards) - [Managing profile-based loyalty program data](https://docs.talon.one/docs/product/loyalty-programs/profile-based/managing-pb-lp-data)
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Used to return expired, active, and pending loyalty balances before this timestamp. You can enter any past, present, or future timestamp value. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
@@ -34652,8 +34442,6 @@ def _get_loyalty_ledger_balances_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -34695,7 +34483,7 @@ def get_loyalty_points(
) -> LoyaltyLedger:
"""(Deprecated) Get customer's full loyalty ledger
- Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -34767,7 +34555,7 @@ def get_loyalty_points_with_http_info(
) -> ApiResponse[LoyaltyLedger]:
"""(Deprecated) Get customer's full loyalty ledger
- Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -34839,7 +34627,7 @@ def get_loyalty_points_without_preload_content(
) -> RESTResponseType:
"""(Deprecated) Get customer's full loyalty ledger
- Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Get the loyalty ledger for this profile integration ID. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -34933,8 +34721,6 @@ def _get_loyalty_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -34975,7 +34761,7 @@ def get_loyalty_program(
) -> LoyaltyProgram:
"""Get loyalty program
- Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory)
+ Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#tag/Loyalty/operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35042,7 +34828,7 @@ def get_loyalty_program_with_http_info(
) -> ApiResponse[LoyaltyProgram]:
"""Get loyalty program
- Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory)
+ Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#tag/Loyalty/operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35109,7 +34895,7 @@ def get_loyalty_program_without_preload_content(
) -> RESTResponseType:
"""Get loyalty program
- Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use the [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory)
+ Get the specified [loyalty program](https://docs.talon.one/docs/product/loyalty-programs/overview). To list all loyalty programs in your Application, use [List loyalty programs](#tag/Loyalty/operation/getLoyaltyPrograms). To list the loyalty programs that a customer profile is part of, use [List customer data](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/getCustomerInventory).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35196,8 +34982,6 @@ def _get_loyalty_program_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -35224,12 +35008,12 @@ def get_loyalty_program_profile_ledger_transactions(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35248,23 +35032,23 @@ def get_loyalty_program_profile_ledger_transactions(
) -> GetLoyaltyProgramProfileTransactions200Response:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -35334,12 +35118,12 @@ def get_loyalty_program_profile_ledger_transactions_with_http_info(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35358,23 +35142,23 @@ def get_loyalty_program_profile_ledger_transactions_with_http_info(
) -> ApiResponse[GetLoyaltyProgramProfileTransactions200Response]:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -35444,12 +35228,12 @@ def get_loyalty_program_profile_ledger_transactions_without_preload_content(
self,
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
integration_id: Annotated[StrictStr, Field(description="The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. ")],
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.")] = None,
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35468,23 +35252,23 @@ def get_loyalty_program_profile_ledger_transactions_without_preload_content(
) -> RESTResponseType:
"""List customer's loyalty transactions
- Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. **Note:** To retrieve all loyalty program transaction logs in a given loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) endpoint.
+ Retrieve paginated results of loyalty transaction logs for the given Integration ID in the specified loyalty program. You can filter transactions by date or by ledger (subledger or main ledger). If no filters are applied, the last 50 loyalty transactions for the given integration ID are returned. > [!note] To retrieve all loyalty program transaction logs in a given > loyalty program, use the [List loyalty program transactions](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyProgramTransactions) > endpoint.
:param loyalty_program_id: Identifier of the profile-based loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
:param integration_id: The integration identifier for this customer profile. Must be: - Unique within the deployment. - Stable for the customer. Do not use an ID that the customer can update themselves. For example, you can use a database ID. Once set, you cannot update this identifier. (required)
:type integration_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
:param subledger_id: The ID of the subledger used to filter the data. Leave this value empty (\"\") to query the main ledger.
:type subledger_id: str
:param loyalty_transaction_type: Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file.
:type loyalty_transaction_type: str
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -35656,8 +35440,6 @@ def _get_loyalty_program_profile_ledger_transactions_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -35685,10 +35467,10 @@ def get_loyalty_program_transactions(
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35707,7 +35489,7 @@ def get_loyalty_program_transactions(
) -> GetLoyaltyProgramTransactions200Response:
"""List loyalty program transactions
- Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. **Note:** If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. > [!note] **Note** > - If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. > - To get loyalty transaction logs for a given Integration ID in > a loyalty program, we recommend using the Integration API's [Get customer's loyalty > logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35715,13 +35497,13 @@ def get_loyalty_program_transactions(
:type loyalty_transaction_type: str
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -35791,10 +35573,10 @@ def get_loyalty_program_transactions_with_http_info(
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35813,7 +35595,7 @@ def get_loyalty_program_transactions_with_http_info(
) -> ApiResponse[GetLoyaltyProgramTransactions200Response]:
"""List loyalty program transactions
- Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. **Note:** If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. > [!note] **Note** > - If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. > - To get loyalty transaction logs for a given Integration ID in > a loyalty program, we recommend using the Integration API's [Get customer's loyalty > logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35821,13 +35603,13 @@ def get_loyalty_program_transactions_with_http_info(
:type loyalty_transaction_type: str
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -35897,10 +35679,10 @@ def get_loyalty_program_transactions_without_preload_content(
loyalty_program_id: Annotated[StrictInt, Field(description="Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. ")],
loyalty_transaction_type: Annotated[Optional[StrictStr], Field(description="Filter results by loyalty transaction type: - `manual`: Loyalty transaction that was done manually. - `session`: Loyalty transaction that resulted from a customer session. - `import`: Loyalty transaction that was imported from a CSV file. ")] = None,
subledger_id: Annotated[Optional[StrictStr], Field(description="The ID of the subledger by which we filter the data.")] = None,
- customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
- transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
- start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
- end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ customer_session_ids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions. ")] = None,
+ transaction_uuids: Annotated[Optional[List[StrictStr]], Field(description="Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions. ")] = None,
+ start_date: Annotated[Optional[datetime], Field(description="Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
+ end_date: Annotated[Optional[datetime], Field(description="Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered. ")] = None,
page_size: Annotated[Optional[Annotated[int, Field(le=1000, strict=True, ge=1)]], Field(description="The number of items in the response.")] = None,
skip: Annotated[Optional[StrictInt], Field(description="The number of items to skip when paging through large result sets.")] = None,
awaits_activation: Annotated[Optional[StrictBool], Field(description="If `true`: Filters results to include only point transactions that have action-based activation and have not expired. If `false`: Returns a `400` response. ")] = None,
@@ -35919,7 +35701,7 @@ def get_loyalty_program_transactions_without_preload_content(
) -> RESTResponseType:
"""List loyalty program transactions
- Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. **Note:** If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. **Important:** To get loyalty transaction logs for a given Integration ID in a loyalty program, we recommend using the Integration API's [Get customer's loyalty logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
+ Retrieve loyalty program transaction logs in a given loyalty program with filtering options applied. Manual and imported transactions are also included. > [!note] **Note** > - If no filters are applied, the last 50 loyalty transactions for the given loyalty program are returned. > - To get loyalty transaction logs for a given Integration ID in > a loyalty program, we recommend using the Integration API's [Get customer's loyalty > logs](https://docs.talon.one/integration-api#tag/Loyalty/operation/getLoyaltyProgramProfileTransactions).
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -35927,13 +35709,13 @@ def get_loyalty_program_transactions_without_preload_content(
:type loyalty_transaction_type: str
:param subledger_id: The ID of the subledger by which we filter the data.
:type subledger_id: str
- :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
+ :param customer_session_ids: Filter the results by a list of customer session IDs. To include multiple IDs, repeat the parameter for each one, for example, `?customerSessionIDs=id1&customerSessionIDs=id2`. The response contains only data associated with the specified sessions.
:type customer_session_ids: List[str]
- :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
+ :param transaction_uuids: Filter the results by a list of transaction UUIDs. To include multiple IDs, repeat the parameter for each one, for example, `?transactionUUIDs=uuid1&transactionUUIDs=uuid2`. The response contains only data associated with the specified transactions.
:type transaction_uuids: List[str]
- :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param start_date: Date and time from which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type start_date: datetime
- :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. **Note:** - It must be an RFC3339 timestamp string. - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
+ :param end_date: Date and time by which results are returned. Results are filtered by transaction creation date. > [!note] **Note** > - This must be an RFC3339 timestamp string. > - You can include a time component in your string, for example, `T23:59:59` to specify the end of the day. The time zone setting > considered is `UTC`. If you do not include a time component, a default time value of `T00:00:00` (midnight) in `UTC` is considered.
:type end_date: datetime
:param page_size: The number of items in the response.
:type page_size: int
@@ -36101,8 +35883,6 @@ def _get_loyalty_program_transactions_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -36349,8 +36129,6 @@ def _get_loyalty_programs_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -36391,7 +36169,7 @@ def get_loyalty_statistics(
) -> LoyaltyDashboardData:
"""(Deprecated) Get loyalty program statistics
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
+ > [warning] This endpoint is deprecated. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -36459,7 +36237,7 @@ def get_loyalty_statistics_with_http_info(
) -> ApiResponse[LoyaltyDashboardData]:
"""(Deprecated) Get loyalty program statistics
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
+ > [warning] This endpoint is deprecated. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -36527,7 +36305,7 @@ def get_loyalty_statistics_without_preload_content(
) -> RESTResponseType:
"""(Deprecated) Get loyalty program statistics
- ⚠️ Deprecation notice: Support for requests to this endpoint will end soon. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
+ > [warning] This endpoint is deprecated. To retrieve statistics for a loyalty program, use the [Get statistics for loyalty dashboard](/management-api#tag/Loyalty/operation/getDashboardStatistics) endpoint. Retrieve the statistics of the specified loyalty program, such as the total active points, pending points, spent points, and expired points.
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -36615,8 +36393,6 @@ def _get_loyalty_statistics_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -36685,7 +36461,7 @@ def get_message_logs(
:param created_after: Filter results where request and response times to return entries after parameter value, expected to be an RFC3339 timestamp string. Use UTC time.
:type created_after: datetime
:param cursor: A specific unique value in the database. If this value is not given, the server fetches results starting with the first record.
- :type cursor: bytearray
+ :type cursor: bytes
:param period: Filter results by time period. Choose between the available relative time frames.
:type period: str
:param is_successful: Indicates whether to return log entries with either successful or unsuccessful HTTP response codes. When set to`true`, only log entries with `2xx` response codes are returned. When set to `false`, only log entries with `4xx` and `5xx` response codes are returned.
@@ -36804,7 +36580,7 @@ def get_message_logs_with_http_info(
:param created_after: Filter results where request and response times to return entries after parameter value, expected to be an RFC3339 timestamp string. Use UTC time.
:type created_after: datetime
:param cursor: A specific unique value in the database. If this value is not given, the server fetches results starting with the first record.
- :type cursor: bytearray
+ :type cursor: bytes
:param period: Filter results by time period. Choose between the available relative time frames.
:type period: str
:param is_successful: Indicates whether to return log entries with either successful or unsuccessful HTTP response codes. When set to`true`, only log entries with `2xx` response codes are returned. When set to `false`, only log entries with `4xx` and `5xx` response codes are returned.
@@ -36923,7 +36699,7 @@ def get_message_logs_without_preload_content(
:param created_after: Filter results where request and response times to return entries after parameter value, expected to be an RFC3339 timestamp string. Use UTC time.
:type created_after: datetime
:param cursor: A specific unique value in the database. If this value is not given, the server fetches results starting with the first record.
- :type cursor: bytearray
+ :type cursor: bytes
:param period: Filter results by time period. Choose between the available relative time frames.
:type period: str
:param is_successful: Indicates whether to return log entries with either successful or unsuccessful HTTP response codes. When set to`true`, only log entries with `2xx` response codes are returned. When set to `false`, only log entries with `4xx` and `5xx` response codes are returned.
@@ -37119,8 +36895,6 @@ def _get_message_logs_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -37568,8 +37342,6 @@ def _get_referrals_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -37831,8 +37603,6 @@ def _get_role_v2_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -38124,8 +37894,6 @@ def _get_ruleset_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -38453,8 +38221,6 @@ def _get_rulesets_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -38734,8 +38500,6 @@ def _get_store_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -38997,8 +38761,6 @@ def _get_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -39296,8 +39058,6 @@ def _get_users_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -39559,8 +39319,6 @@ def _get_webhook_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -39943,8 +39701,6 @@ def _get_webhooks_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -39969,7 +39725,7 @@ def _get_webhooks_serialize(
@validate_call
def import_account_collection(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -39986,9 +39742,9 @@ def import_account_collection(
) -> ModelImport:
"""Import data into existing account-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -40042,7 +39798,7 @@ def import_account_collection(
@validate_call
def import_account_collection_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -40059,9 +39815,9 @@ def import_account_collection_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import data into existing account-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -40115,7 +39871,7 @@ def import_account_collection_with_http_info(
@validate_call
def import_account_collection_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -40132,9 +39888,9 @@ def import_account_collection_without_preload_content(
) -> RESTResponseType:
"""Import data into existing account-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -40240,8 +39996,6 @@ def _import_account_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -40283,7 +40037,7 @@ def import_allowed_list(
) -> ModelImport:
"""Import allowed values for attribute
- Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item` (required): the values in your allowed list, for example a list of SKU's. An allowed list is limited to 500,000 items. Example: ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
+ Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item`: The values in your allowed list, for example a list of SKUs. An allowed list is limited to 500,000 items. ## Example ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
:param attribute_id: The ID of the attribute. You can find the ID in the Campaign Manager's URL when you display the details of an attribute in **Account** > **Tools** > **Attributes**. (required)
:type attribute_id: int
@@ -40357,7 +40111,7 @@ def import_allowed_list_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import allowed values for attribute
- Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item` (required): the values in your allowed list, for example a list of SKU's. An allowed list is limited to 500,000 items. Example: ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
+ Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item`: The values in your allowed list, for example a list of SKUs. An allowed list is limited to 500,000 items. ## Example ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
:param attribute_id: The ID of the attribute. You can find the ID in the Campaign Manager's URL when you display the details of an attribute in **Account** > **Tools** > **Attributes**. (required)
:type attribute_id: int
@@ -40431,7 +40185,7 @@ def import_allowed_list_without_preload_content(
) -> RESTResponseType:
"""Import allowed values for attribute
- Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item` (required): the values in your allowed list, for example a list of SKU's. An allowed list is limited to 500,000 items. Example: ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
+ Upload a CSV file containing a list of [picklist values](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#picklist-values) for the specified attribute. The file should be sent as multipart data. The import **replaces** the previous list of allowed values for this attribute, if any. The CSV file **must** only contain the following column: - `item`: The values in your allowed list, for example a list of SKUs. An allowed list is limited to 500,000 items. ## Example ```text item CS-VG-04032021-UP-50D-10 CS-DV-04042021-UP-49D-12 CS-DG-02082021-UP-50G-07 ```
:param attribute_id: The ID of the attribute. You can find the ID in the Campaign Manager's URL when you display the details of an attribute in **Account** > **Tools** > **Attributes**. (required)
:type attribute_id: int
@@ -40540,8 +40294,6 @@ def _import_allowed_list_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -40583,7 +40335,7 @@ def import_audiences_memberships(
) -> ModelImport:
"""Import audience members
- Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. **Note:** We recommend limiting your file size to 500MB. Example: ```text profileintegrationid charles alexa ```
+ Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text profileintegrationid charles alexa ```
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -40657,7 +40409,7 @@ def import_audiences_memberships_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import audience members
- Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. **Note:** We recommend limiting your file size to 500MB. Example: ```text profileintegrationid charles alexa ```
+ Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text profileintegrationid charles alexa ```
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -40731,7 +40483,7 @@ def import_audiences_memberships_without_preload_content(
) -> RESTResponseType:
"""Import audience members
- Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. **Note:** We recommend limiting your file size to 500MB. Example: ```text profileintegrationid charles alexa ```
+ Upload a CSV file containing the integration IDs of the members you want to add to an audience. The file should be sent as multipart data and should contain only the following column (required): - `profileintegrationid`: The integration ID of the customer profile. The import **replaces** the previous list of audience members. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text profileintegrationid charles alexa ```
:param audience_id: The ID of the audience. (required)
:type audience_id: int
@@ -40840,8 +40592,6 @@ def _import_audiences_memberships_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -41183,8 +40933,6 @@ def _import_campaign_store_budget_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -41498,8 +41246,6 @@ def _import_campaign_stores_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -41526,7 +41272,7 @@ def import_collection(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -41543,13 +41289,13 @@ def import_collection(
) -> ModelImport:
"""Import data into existing campaign-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -41606,7 +41352,7 @@ def import_collection_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -41623,13 +41369,13 @@ def import_collection_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import data into existing campaign-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -41686,7 +41432,7 @@ def import_collection_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
up_file: Annotated[Optional[StrictStr], Field(description="The file containing the data that is being imported.")] = None,
_request_timeout: Union[
None,
@@ -41703,13 +41449,13 @@ def import_collection_without_preload_content(
) -> RESTResponseType:
"""Import data into existing campaign-level collection
- Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. Example: ``` item Addidas Nike Asics ``` **Note:** Before sending a request to this endpoint, ensure the data in the CSV to import is different from the data currently stored in the collection.
+ Upload a CSV file containing the collection of string values that should be attached as payload for collection. The file should be sent as multipart data. The import **replaces** the initial content of the collection. The CSV file **must** only contain the following column: - `item`: the values in your collection. A collection is limited to 500,000 items. ## Example ``` item Adidas Nike Asics ``` > [!note] Before sending a request to this endpoint, ensure the data in the > CSV to import is different from the data currently stored in the collection.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param up_file: The file containing the data that is being imported.
:type up_file: str
@@ -41822,8 +41568,6 @@ def _import_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -41867,7 +41611,7 @@ def import_coupons(
) -> ModelImport:
"""Import coupons
- Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
+ Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -41946,7 +41690,7 @@ def import_coupons_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import coupons
- Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
+ Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -42025,7 +41769,7 @@ def import_coupons_without_preload_content(
) -> RESTResponseType:
"""Import coupons
- Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
+ Upload a CSV file containing the coupons that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `value` (required): The coupon code. Must be at least 3 characters long. We recommend using alphanumeric characters. There is no maximum length but limiting the code to 30 characters ensures it is fully readable in the Campaign Manager. The code should be unique unless you set `skipDuplicates` to `true`. - `expirydate`: The end date in RFC3339 of the code redemption period. - `startdate`: The start date in RFC3339 of the code redemption period. - `recipientintegrationid`: The integration ID of the recipient of the coupon. Only the customer with this integration ID can redeem this code. Available only for personal codes. - `limitval`: The maximum number of redemptions of this code. For unlimited redemptions, use `0`. Defaults to `1` when not provided. - `discountlimit`: The total discount value that the code can give. This is typically used to represent a gift card value. - `attributes`: A JSON object describing _custom_ coupon attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the coupon entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text \"value\",\"expirydate\",\"startdate\",\"recipientintegrationid\",\"limitval\",\"attributes\",\"discountlimit\" COUP1,2018-07-01T04:00:00Z,2018-05-01T04:00:00Z,cust123,1,\"{\"\"Category\"\": \"\"10_off\"\"}\",2.4 ``` Once imported, you can find the `batchId` in the Campaign Manager or by using [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -42145,8 +41889,6 @@ def _import_coupons_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -42188,7 +41930,7 @@ def import_loyalty_cards(
) -> ModelImport:
"""Import loyalty cards
- Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
+ Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). > [!note] We recommend limiting your file size to 500MB. ## Example ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42261,7 +42003,7 @@ def import_loyalty_cards_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import loyalty cards
- Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
+ Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). > [!note] We recommend limiting your file size to 500MB. ## Example ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42334,7 +42076,7 @@ def import_loyalty_cards_without_preload_content(
) -> RESTResponseType:
"""Import loyalty cards
- Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
+ Upload a CSV file containing the loyalty cards that you want to use in your card-based loyalty program. Send the file as multipart data. It contains the following columns for each card: - `identifier` (required): The identifier of the loyalty card, which must match the regular expression `^[A-Za-z0-9._%+@-]+$`. - `state` (required): The state of the loyalty card. It can be `active` or `inactive`. - `customerprofileids` (optional): An array of strings representing the identifiers of the customer profiles linked to the loyalty card. The identifiers should be separated with a semicolon (;). > [!note] We recommend limiting your file size to 500MB. ## Example ```csv identifier,state,customerprofileids 123-456-789AT,active,Alexa001;UserA ```
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42442,8 +42184,6 @@ def _import_loyalty_cards_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -42485,7 +42225,7 @@ def import_loyalty_customers_tiers(
) -> ModelImport:
"""Import customers into loyalty tiers
- Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. **Important:** This endpoint only works with loyalty programs with advanced tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. **Note:** We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
+ Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. > [!important] This endpoint only works with loyalty programs with advanced > tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. > [!note] We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42559,7 +42299,7 @@ def import_loyalty_customers_tiers_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import customers into loyalty tiers
- Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. **Important:** This endpoint only works with loyalty programs with advanced tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. **Note:** We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
+ Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. > [!important] This endpoint only works with loyalty programs with advanced > tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. > [!note] We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42633,7 +42373,7 @@ def import_loyalty_customers_tiers_without_preload_content(
) -> RESTResponseType:
"""Import customers into loyalty tiers
- Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. **Important:** This endpoint only works with loyalty programs with advanced tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. **Note:** We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** We recommend limiting your file size to 500MB. **Example:** ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
+ Upload a CSV file containing existing customers to be assigned to existing tiers. Send the file as multipart data. > [!important] This endpoint only works with loyalty programs with advanced > tiers (with expiration and downgrade policy) feature enabled. The CSV file should contain the following columns: - `subledgerid` (optional): The ID of the subledger. If this field is empty, the main ledger will be used. - `customerprofileid`: The integration ID of the customer profile to whom the tier should be assigned. - `tiername`: The name of an existing tier to assign to the customer. - `expirydate`: The expiration date of the tier when the tier is reevaluated. It should be a future date. About customer assignment to a tier: - If the customer isn't already in a tier, the customer is assigned to the specified tier during the tier import. - If the customer is already in the tier that's specified in the CSV file, only the expiration date is updated. > [!note] We recommend not using this endpoint to update the tier of a customer. To update a customer's tier, you can [add](/management-api#tag/Loyalty/operation/addLoyaltyPoints) or [deduct](/management-api#tag/Loyalty/operation/removeLoyaltyPoints) their loyalty points. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] We recommend limiting your file size to 500 MB. ## Example ```csv subledgerid,customerprofileid,tiername,expirydate SUB1,alexa,Gold,2024-03-21T07:32:14Z ,george,Silver,2025-04-16T21:12:37Z SUB2,avocado,Bronze,2026-05-03T11:47:01Z ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42742,8 +42482,6 @@ def _import_loyalty_customers_tiers_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -42786,7 +42524,7 @@ def import_loyalty_points(
) -> ModelImport:
"""Import loyalty points
- Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit. Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** For existing customer profiles and loyalty cards, the imported points are added to any previous active or pending points, depending on the value provided for `startdate`. If `startdate` matches the current date, the imported points are _active_. If it is later, the points are _pending_ until the date provided for `startdate` is reached. **Note:** We recommend limiting your file size to 500MB. **Example for profile-based programs:** ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` **Example for card-based programs:** ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
+ Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit.
Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] For existing customer profiles and loyalty cards, the imported > points are added to any previous active or pending points, depending on the > value provided for `startdate`. If `startdate` matches the current date, the > imported points are _active_. If it is later, the points are _pending_ until > the date provided for `startdate` is reached. > [!note] We recommend limiting your file size to 500 MB. ## Example for profile-based programs ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` ## Example for card-based programs ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42861,7 +42599,7 @@ def import_loyalty_points_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import loyalty points
- Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit. Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** For existing customer profiles and loyalty cards, the imported points are added to any previous active or pending points, depending on the value provided for `startdate`. If `startdate` matches the current date, the imported points are _active_. If it is later, the points are _pending_ until the date provided for `startdate` is reached. **Note:** We recommend limiting your file size to 500MB. **Example for profile-based programs:** ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` **Example for card-based programs:** ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
+ Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit.
Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] For existing customer profiles and loyalty cards, the imported > points are added to any previous active or pending points, depending on the > value provided for `startdate`. If `startdate` matches the current date, the > imported points are _active_. If it is later, the points are _pending_ until > the date provided for `startdate` is reached. > [!note] We recommend limiting your file size to 500 MB. ## Example for profile-based programs ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` ## Example for card-based programs ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -42936,7 +42674,7 @@ def import_loyalty_points_without_preload_content(
) -> RESTResponseType:
"""Import loyalty points
- Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit. Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Note:** For existing customer profiles and loyalty cards, the imported points are added to any previous active or pending points, depending on the value provided for `startdate`. If `startdate` matches the current date, the imported points are _active_. If it is later, the points are _pending_ until the date provided for `startdate` is reached. **Note:** We recommend limiting your file size to 500MB. **Example for profile-based programs:** ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` **Example for card-based programs:** ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
+ Upload a CSV file containing the loyalty points you want to import into a given loyalty program. Send the file as multipart data. Depending on the type of loyalty program, you can import points into a given customer profile or loyalty card. The CSV file contains the following columns: - `customerprofileid` (optional): For profile-based loyalty programs, the integration ID of the customer profile where the loyalty points are imported. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `identifier` (optional): For card-based loyalty programs, the identifier of the loyalty card where the loyalty points are imported. - `amount`: The amount of points to award to the customer profile. - `startdate` (optional): The earliest date when the points can be redeemed. The points are `active` from this date until the expiration date. This parameter accepts one of the following values: - A timestamp string in RFC3339 format. - `immediate` - `on_action` **Note**: Empty or missing values default to `immediate`. - `expirydate` (optional): The latest date when the points can be redeemed. The points are `expired` after this date. **Note**: It must be an RFC3339 timestamp string or string `unlimited`. Empty or missing values are considered `unlimited`. If passed, `validityDuration` should be omitted. - `validityDuration` (optional): The duration for which the points remain active, relative to the activation date. The time format is an **integer** followed by one letter indicating the time unit.
Examples: `30s`, `40m`, `1h`, `5D`, `7W`, `10M`, `15Y`. Available units: - `s`: seconds - `m`: minutes - `h`: hours - `D`: days - `W`: weeks - `M`: months - `Y`: years You can round certain units up or down: - `_D` for rounding down days only. Signifies the start of the day. - `_U` for rounding up days, weeks, months and years. Signifies the end of the day, week, month or year. If passed, `expirydate` should be omitted. - `subledgerid` (optional): The ID of the subledger that should received the points. - `reason` (optional): The reason why these points are awarded. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!note] For existing customer profiles and loyalty cards, the imported > points are added to any previous active or pending points, depending on the > value provided for `startdate`. If `startdate` matches the current date, the > imported points are _active_. If it is later, the points are _pending_ until > the date provided for `startdate` is reached. > [!note] We recommend limiting your file size to 500 MB. ## Example for profile-based programs ```text customerprofileid,amount,startdate,expirydate,subledgerid,reason URNGV8294NV,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ``` ## Example for card-based programs ```text identifier,amount,startdate,expirydate,subledgerid,reason summer-loyalty-card-0543,100,2009-11-10T23:00:00Z,2009-11-11T23:00:00Z,subledger1,appeasement ```
:param loyalty_program_id: Identifier of the loyalty program. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -43050,8 +42788,6 @@ def _import_loyalty_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -43093,7 +42829,7 @@ def import_pool_giveaways(
) -> ModelImport:
"""Import giveaway codes into a giveaway pool
- Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. **Note:** - We recommend limiting your file size to 500MB. - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. **Example:** ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
+ Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. > [!note] **Note** > - We recommend limiting your file size to 500MB. > - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. ## Example ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -43164,7 +42900,7 @@ def import_pool_giveaways_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import giveaway codes into a giveaway pool
- Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. **Note:** - We recommend limiting your file size to 500MB. - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. **Example:** ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
+ Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. > [!note] **Note** > - We recommend limiting your file size to 500MB. > - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. ## Example ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -43235,7 +42971,7 @@ def import_pool_giveaways_without_preload_content(
) -> RESTResponseType:
"""Import giveaway codes into a giveaway pool
- Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. **Note:** - We recommend limiting your file size to 500MB. - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. **Example:** ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
+ Upload a CSV file containing the giveaway codes that should be created. Send the file as multipart data. The CSV file contains the following columns: - `code` (required): The code of your giveaway, for instance, a gift card redemption code. - `startdate`: The start date in RFC3339 of the code redemption period. - `enddate`: The last date in RFC3339 of the code redemption period. - `attributes`: A JSON object describing _custom_ giveaway attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `provider` associated with the giveaway entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"provider\": \"myPartnerCompany\"}\"`. The `startdate` and `enddate` have nothing to do with the _validity_ of the codes. They are only used by the Rule Engine to award the codes or not. You can use the time zone setting of your choice. The values are converted to UTC internally by Talon.One. > [!note] **Note** > - We recommend limiting your file size to 500MB. > - You can import the same code multiple times. Duplicate codes are treated and distributed to customers as unique codes. ## Example ```text code,startdate,enddate,attributes GIVEAWAY1,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY2,2020-11-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Amazon\"\"}\" GIVEAWAY3,2021-01-10T23:00:00Z,2022-11-11T23:00:00Z,\"{\"\"provider\"\": \"\"Aliexpress\"\"}\" ```
:param pool_id: The ID of the pool. You can find it in the Campaign Manager, in the **Giveaways** section. (required)
:type pool_id: int
@@ -43341,8 +43077,6 @@ def _import_pool_giveaways_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -43385,7 +43119,7 @@ def import_referrals(
) -> ModelImport:
"""Import referrals
- Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Important:** When you import a CSV file with referrals, a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) is **not** automatically created for each `advocateprofileintegrationid` column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) endpoint to create the customer profiles. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
+ Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!important] When you import a CSV file with referrals, > a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) > is **not** automatically created for each `advocateprofileintegrationid` > column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) > endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) > endpoint to create the customer profiles. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -43460,7 +43194,7 @@ def import_referrals_with_http_info(
) -> ApiResponse[ModelImport]:
"""Import referrals
- Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Important:** When you import a CSV file with referrals, a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) is **not** automatically created for each `advocateprofileintegrationid` column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) endpoint to create the customer profiles. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
+ Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!important] When you import a CSV file with referrals, > a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) > is **not** automatically created for each `advocateprofileintegrationid` > column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) > endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) > endpoint to create the customer profiles. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -43535,7 +43269,7 @@ def import_referrals_without_preload_content(
) -> RESTResponseType:
"""Import referrals
- Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks. For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. **Important:** When you import a CSV file with referrals, a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) is **not** automatically created for each `advocateprofileintegrationid` column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) endpoint to create the customer profiles. **Note:** We recommend limiting your file size to 500MB. **Example:** ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
+ Upload a CSV file containing the referrals that should be created. The file should be sent as multipart data. The CSV file contains the following columns: - `code` (required): The referral code. - `advocateprofileintegrationid` (required): The profile ID of the advocate. - `startdate`: The start date in RFC3339 of the code redemption period. - `expirydate`: The end date in RFC3339 of the code redemption period. - `limitval`: The maximum number of redemptions of this code. Defaults to `1` when left blank. - `attributes`: A JSON object describing _custom_ referral attribute names and their values, enclosed with double quotation marks.
For example, if you created a [custom attribute](https://docs.talon.one/docs/dev/concepts/attributes#custom-attributes) called `category` associated with the referral entity, the object in the CSV file, when opened in a text editor, must be: `\"{\"category\": \"10_off\"}\"`. You can use the time zone of your choice. It is converted to UTC internally by Talon.One. > [!important] When you import a CSV file with referrals, > a [customer profile](https://docs.talon.one/docs/dev/concepts/entities/customer-profiles) > is **not** automatically created for each `advocateprofileintegrationid` > column value. Use the [Update customer profile](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfileV2) > endpoint or the [Update multiple customer profiles](https://docs.talon.one/integration-api#tag/Customer-profiles/operation/updateCustomerProfilesV2) > endpoint to create the customer profiles. > [!note] We recommend limiting your file size to 500 MB. ## Example ```text code,startdate,expirydate,advocateprofileintegrationid,limitval,attributes REFERRAL_CODE1,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid_4,1,\"{\"\"my_attribute\"\": \"\"10_off\"\"}\" REFERRAL_CODE2,2020-11-10T23:00:00Z,2021-11-11T23:00:00Z,integid1,1,\"{\"\"my_attribute\"\": \"\"20_off\"\"}\" ```
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -43647,8 +43381,6 @@ def _import_referrals_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -43916,8 +43648,6 @@ def _invite_user_external_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -44258,8 +43988,6 @@ def _list_account_collections_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -44587,8 +44315,6 @@ def _list_achievements_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -44835,8 +44561,6 @@ def _list_all_roles_v2_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -45156,8 +44880,6 @@ def _list_campaign_store_budget_limits_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -45506,8 +45228,6 @@ def _list_catalog_items_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -45872,8 +45592,6 @@ def _list_collections_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -46223,8 +45941,6 @@ def _list_collections_in_application_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -46537,8 +46253,6 @@ def _list_experiments_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -46936,8 +46650,6 @@ def _list_stores_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -47177,8 +46889,6 @@ def _okta_event_handler_challenge_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -47200,6 +46910,295 @@ def _okta_event_handler_challenge_serialize(
+ @validate_call
+ def price_history(
+ self,
+ application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
+ price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
+ _request_timeout: Union[
+ None,
+ Annotated[StrictFloat, Field(gt=0)],
+ Tuple[
+ Annotated[StrictFloat, Field(gt=0)],
+ Annotated[StrictFloat, Field(gt=0)]
+ ]
+ ] = None,
+ _request_auth: Optional[Dict[StrictStr, Any]] = None,
+ _content_type: Optional[StrictStr] = None,
+ _headers: Optional[Dict[StrictStr, Any]] = None,
+ _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
+ ) -> PriceHistoryResponse:
+ """Get summary of price history
+
+ Fetch the historical price data for a given SKU within a defined timeframe.
+
+ :param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
+ :type application_id: int
+ :param price_history_request: body (required)
+ :type price_history_request: PriceHistoryRequest
+ :param _request_timeout: timeout setting for this request. If one
+ number provided, it will be total request
+ timeout. It can also be a pair (tuple) of
+ (connection, read) timeouts.
+ :type _request_timeout: int, tuple(int, int), optional
+ :param _request_auth: set to override the auth_settings for an a single
+ request; this effectively ignores the
+ authentication in the spec for a single request.
+ :type _request_auth: dict, optional
+ :param _content_type: force content-type for the request.
+ :type _content_type: str, Optional
+ :param _headers: set to override the headers for a single
+ request; this effectively ignores the headers
+ in the spec for a single request.
+ :type _headers: dict, optional
+ :param _host_index: set to override the host_index for a single
+ request; this effectively ignores the host_index
+ in the spec for a single request.
+ :type _host_index: int, optional
+ :return: Returns the result object.
+ """ # noqa: E501
+
+ _param = self._price_history_serialize(
+ application_id=application_id,
+ price_history_request=price_history_request,
+ _request_auth=_request_auth,
+ _content_type=_content_type,
+ _headers=_headers,
+ _host_index=_host_index
+ )
+
+ _response_types_map: Dict[str, Optional[str]] = {
+ '200': "PriceHistoryResponse",
+ }
+ response_data = self.api_client.call_api(
+ *_param,
+ _request_timeout=_request_timeout
+ )
+ response_data.read()
+ return self.api_client.response_deserialize(
+ response_data=response_data,
+ response_types_map=_response_types_map,
+ ).data
+
+
+ @validate_call
+ def price_history_with_http_info(
+ self,
+ application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
+ price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
+ _request_timeout: Union[
+ None,
+ Annotated[StrictFloat, Field(gt=0)],
+ Tuple[
+ Annotated[StrictFloat, Field(gt=0)],
+ Annotated[StrictFloat, Field(gt=0)]
+ ]
+ ] = None,
+ _request_auth: Optional[Dict[StrictStr, Any]] = None,
+ _content_type: Optional[StrictStr] = None,
+ _headers: Optional[Dict[StrictStr, Any]] = None,
+ _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
+ ) -> ApiResponse[PriceHistoryResponse]:
+ """Get summary of price history
+
+ Fetch the historical price data for a given SKU within a defined timeframe.
+
+ :param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
+ :type application_id: int
+ :param price_history_request: body (required)
+ :type price_history_request: PriceHistoryRequest
+ :param _request_timeout: timeout setting for this request. If one
+ number provided, it will be total request
+ timeout. It can also be a pair (tuple) of
+ (connection, read) timeouts.
+ :type _request_timeout: int, tuple(int, int), optional
+ :param _request_auth: set to override the auth_settings for an a single
+ request; this effectively ignores the
+ authentication in the spec for a single request.
+ :type _request_auth: dict, optional
+ :param _content_type: force content-type for the request.
+ :type _content_type: str, Optional
+ :param _headers: set to override the headers for a single
+ request; this effectively ignores the headers
+ in the spec for a single request.
+ :type _headers: dict, optional
+ :param _host_index: set to override the host_index for a single
+ request; this effectively ignores the host_index
+ in the spec for a single request.
+ :type _host_index: int, optional
+ :return: Returns the result object.
+ """ # noqa: E501
+
+ _param = self._price_history_serialize(
+ application_id=application_id,
+ price_history_request=price_history_request,
+ _request_auth=_request_auth,
+ _content_type=_content_type,
+ _headers=_headers,
+ _host_index=_host_index
+ )
+
+ _response_types_map: Dict[str, Optional[str]] = {
+ '200': "PriceHistoryResponse",
+ }
+ response_data = self.api_client.call_api(
+ *_param,
+ _request_timeout=_request_timeout
+ )
+ response_data.read()
+ return self.api_client.response_deserialize(
+ response_data=response_data,
+ response_types_map=_response_types_map,
+ )
+
+
+ @validate_call
+ def price_history_without_preload_content(
+ self,
+ application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
+ price_history_request: Annotated[PriceHistoryRequest, Field(description="body")],
+ _request_timeout: Union[
+ None,
+ Annotated[StrictFloat, Field(gt=0)],
+ Tuple[
+ Annotated[StrictFloat, Field(gt=0)],
+ Annotated[StrictFloat, Field(gt=0)]
+ ]
+ ] = None,
+ _request_auth: Optional[Dict[StrictStr, Any]] = None,
+ _content_type: Optional[StrictStr] = None,
+ _headers: Optional[Dict[StrictStr, Any]] = None,
+ _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0,
+ ) -> RESTResponseType:
+ """Get summary of price history
+
+ Fetch the historical price data for a given SKU within a defined timeframe.
+
+ :param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
+ :type application_id: int
+ :param price_history_request: body (required)
+ :type price_history_request: PriceHistoryRequest
+ :param _request_timeout: timeout setting for this request. If one
+ number provided, it will be total request
+ timeout. It can also be a pair (tuple) of
+ (connection, read) timeouts.
+ :type _request_timeout: int, tuple(int, int), optional
+ :param _request_auth: set to override the auth_settings for an a single
+ request; this effectively ignores the
+ authentication in the spec for a single request.
+ :type _request_auth: dict, optional
+ :param _content_type: force content-type for the request.
+ :type _content_type: str, Optional
+ :param _headers: set to override the headers for a single
+ request; this effectively ignores the headers
+ in the spec for a single request.
+ :type _headers: dict, optional
+ :param _host_index: set to override the host_index for a single
+ request; this effectively ignores the host_index
+ in the spec for a single request.
+ :type _host_index: int, optional
+ :return: Returns the result object.
+ """ # noqa: E501
+
+ _param = self._price_history_serialize(
+ application_id=application_id,
+ price_history_request=price_history_request,
+ _request_auth=_request_auth,
+ _content_type=_content_type,
+ _headers=_headers,
+ _host_index=_host_index
+ )
+
+ _response_types_map: Dict[str, Optional[str]] = {
+ '200': "PriceHistoryResponse",
+ }
+ response_data = self.api_client.call_api(
+ *_param,
+ _request_timeout=_request_timeout
+ )
+ return response_data.response
+
+
+ def _price_history_serialize(
+ self,
+ application_id,
+ price_history_request,
+ _request_auth,
+ _content_type,
+ _headers,
+ _host_index,
+ ) -> RequestSerialized:
+
+ _host = None
+
+ _collection_formats: Dict[str, str] = {
+ }
+
+ _path_params: Dict[str, str] = {}
+ _query_params: List[Tuple[str, str]] = []
+ _header_params: Dict[str, Optional[str]] = _headers or {}
+ _form_params: List[Tuple[str, str]] = []
+ _files: Dict[
+ str, Union[str, bytes, List[str], List[bytes], List[Tuple[str, bytes]]]
+ ] = {}
+ _body_params: Optional[bytes] = None
+
+ # process the path parameters
+ if application_id is not None:
+ _path_params['applicationId'] = application_id
+ # process the query parameters
+ # process the header parameters
+ # process the form parameters
+ # process the body parameter
+ if price_history_request is not None:
+ _body_params = price_history_request
+
+
+ # set the HTTP header `Accept`
+ if 'Accept' not in _header_params:
+ _header_params['Accept'] = self.api_client.select_header_accept(
+ [
+ 'application/json'
+ ]
+ )
+
+ # set the HTTP header `Content-Type`
+ if _content_type:
+ _header_params['Content-Type'] = _content_type
+ else:
+ _default_content_type = (
+ self.api_client.select_header_content_type(
+ [
+ 'application/json'
+ ]
+ )
+ )
+ if _default_content_type is not None:
+ _header_params['Content-Type'] = _default_content_type
+
+ # authentication setting
+ _auth_settings: List[str] = [
+ 'api_key_v1'
+ ]
+
+ return self.api_client.param_serialize(
+ method='POST',
+ resource_path='/v1/applications/{applicationId}/price_history',
+ path_params=_path_params,
+ query_params=_query_params,
+ header_params=_header_params,
+ body=_body_params,
+ post_params=_form_params,
+ files=_files,
+ auth_settings=_auth_settings,
+ collection_formats=_collection_formats,
+ _host=_host,
+ _request_auth=_request_auth
+ )
+
+
+
+
@validate_call
def remove_loyalty_points(
self,
@@ -47221,7 +47220,7 @@ def remove_loyalty_points(
) -> None:
"""Deduct points from customer profile
- Deduct points from the specified loyalty program and specified customer profile. **Important:** - Only active points can be deducted. - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Deduct points from the specified loyalty program and specified customer profile. > [!note] **Note** > - Only active points can be deducted. > - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -47299,7 +47298,7 @@ def remove_loyalty_points_with_http_info(
) -> ApiResponse[None]:
"""Deduct points from customer profile
- Deduct points from the specified loyalty program and specified customer profile. **Important:** - Only active points can be deducted. - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Deduct points from the specified loyalty program and specified customer profile. > [!note] **Note** > - Only active points can be deducted. > - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -47377,7 +47376,7 @@ def remove_loyalty_points_without_preload_content(
) -> RESTResponseType:
"""Deduct points from customer profile
- Deduct points from the specified loyalty program and specified customer profile. **Important:** - Only active points can be deducted. - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint.
+ Deduct points from the specified loyalty program and specified customer profile. > [!note] **Note** > - Only active points can be deducted. > - Only pending points are rolled back when a session is cancelled or reopened. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint.
:param loyalty_program_id: The identifier for the loyalty program. (required)
:type loyalty_program_id: str
@@ -47492,8 +47491,6 @@ def _remove_loyalty_points_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -47768,8 +47765,6 @@ def _reset_password_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -48044,8 +48039,6 @@ def _scim_create_group_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -48320,8 +48313,6 @@ def _scim_create_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -48576,8 +48567,6 @@ def _scim_delete_group_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -48832,8 +48821,6 @@ def _scim_delete_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -49095,8 +49082,6 @@ def _scim_get_group_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -49343,8 +49328,6 @@ def _scim_get_groups_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -49591,8 +49574,6 @@ def _scim_get_resource_types_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -49839,8 +49820,6 @@ def _scim_get_schemas_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -50087,8 +50066,6 @@ def _scim_get_service_provider_config_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -50350,8 +50327,6 @@ def _scim_get_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -50598,8 +50573,6 @@ def _scim_get_users_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -50889,8 +50862,6 @@ def _scim_patch_group_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -51180,8 +51151,6 @@ def _scim_patch_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -51471,8 +51440,6 @@ def _scim_replace_group_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -51762,8 +51729,6 @@ def _scim_replace_user_attributes_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -51818,7 +51783,7 @@ def search_coupons_advanced_application_wide_without_total_count(
) -> GetCouponsWithoutTotalCount200Response:
"""List coupons that match the given attributes (without total count)
- List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -51941,7 +51906,7 @@ def search_coupons_advanced_application_wide_without_total_count_with_http_info(
) -> ApiResponse[GetCouponsWithoutTotalCount200Response]:
"""List coupons that match the given attributes (without total count)
- List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -52064,7 +52029,7 @@ def search_coupons_advanced_application_wide_without_total_count_without_preload
) -> RESTResponseType:
"""List coupons that match the given attributes (without total count)
- List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in all the campaigns of the given Application. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -52292,8 +52257,6 @@ def _search_coupons_advanced_application_wide_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -52348,7 +52311,7 @@ def search_coupons_advanced_without_total_count(
) -> GetCouponsWithoutTotalCount200Response:
"""List coupons that match the given attributes in campaign (without total count)
- List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -52471,7 +52434,7 @@ def search_coupons_advanced_without_total_count_with_http_info(
) -> ApiResponse[GetCouponsWithoutTotalCount200Response]:
"""List coupons that match the given attributes in campaign (without total count)
- List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -52594,7 +52557,7 @@ def search_coupons_advanced_without_total_count_without_preload_content(
) -> RESTResponseType:
"""List coupons that match the given attributes in campaign (without total count)
- List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. **Note:** The total count is not included in the response.
+ List the coupons whose attributes match the query criteria in the given campaign. The match is successful if all the attributes of the request are found in a coupon, even if the coupon has more attributes that are not present on the request. > [!note] The total count is not included in the response.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -52820,8 +52783,6 @@ def _search_coupons_advanced_without_total_count_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -53107,8 +53068,6 @@ def _summarize_campaign_store_budget_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -53151,7 +53110,7 @@ def transfer_loyalty_card(
) -> None:
"""Transfer card data
- Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. **Important:** - The original card is automatically blocked once the new card is created, and it cannot be activated again. - The default status of the new card is _active_.
+ Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. > [!important] **Note** > - The original card is automatically blocked once the new card is created, and it cannot be activated again. > - The default status of the new card is _active_.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -53229,7 +53188,7 @@ def transfer_loyalty_card_with_http_info(
) -> ApiResponse[None]:
"""Transfer card data
- Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. **Important:** - The original card is automatically blocked once the new card is created, and it cannot be activated again. - The default status of the new card is _active_.
+ Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. > [!important] **Note** > - The original card is automatically blocked once the new card is created, and it cannot be activated again. > - The default status of the new card is _active_.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -53307,7 +53266,7 @@ def transfer_loyalty_card_without_preload_content(
) -> RESTResponseType:
"""Transfer card data
- Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. **Important:** - The original card is automatically blocked once the new card is created, and it cannot be activated again. - The default status of the new card is _active_.
+ Transfer loyalty card data, such as linked customers, loyalty balances and transactions, from a given loyalty card to a new, automatically created loyalty card. > [!important] **Note** > - The original card is automatically blocked once the new card is created, and it cannot be activated again. > - The default status of the new card is _active_.
:param loyalty_program_id: Identifier of the card-based loyalty program containing the loyalty card. You can get the ID with the [List loyalty programs](https://docs.talon.one/management-api#tag/Loyalty/operation/getLoyaltyPrograms) endpoint. (required)
:type loyalty_program_id: int
@@ -53422,8 +53381,6 @@ def _transfer_loyalty_card_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -53448,7 +53405,7 @@ def _transfer_loyalty_card_serialize(
@validate_call
def update_account_collection(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
update_collection: Annotated[UpdateCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -53467,7 +53424,7 @@ def update_account_collection(
Edit the description of a given account-level collection and enable or disable the collection in the specified Applications.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param update_collection: body (required)
:type update_collection: UpdateCollection
@@ -53522,7 +53479,7 @@ def update_account_collection(
@validate_call
def update_account_collection_with_http_info(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
update_collection: Annotated[UpdateCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -53541,7 +53498,7 @@ def update_account_collection_with_http_info(
Edit the description of a given account-level collection and enable or disable the collection in the specified Applications.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param update_collection: body (required)
:type update_collection: UpdateCollection
@@ -53596,7 +53553,7 @@ def update_account_collection_with_http_info(
@validate_call
def update_account_collection_without_preload_content(
self,
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint.")],
update_collection: Annotated[UpdateCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -53615,7 +53572,7 @@ def update_account_collection_without_preload_content(
Edit the description of a given account-level collection and enable or disable the collection in the specified Applications.
- :param collection_id: The ID of the collection. You can get it with the [List collections in account](#operation/listAccountCollections) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in account](#tag/Collections/operation/listAccountCollections) endpoint. (required)
:type collection_id: int
:param update_collection: body (required)
:type update_collection: UpdateCollection
@@ -53722,8 +53679,6 @@ def _update_account_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -54052,8 +54007,6 @@ def _update_achievement_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -54343,8 +54296,6 @@ def _update_additional_cost_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -54634,8 +54585,6 @@ def _update_attribute_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -54678,7 +54627,7 @@ def update_campaign(
) -> Campaign:
"""Update campaign
- Update the given campaign. **Important:** You cannot use this endpoint to update campaigns if [campaign staging and revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) is enabled for your Application.
+ Update the given campaign. > [!important] You cannot use this endpoint to update campaigns if [campaign staging and > revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) > is enabled for your Application.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -54753,7 +54702,7 @@ def update_campaign_with_http_info(
) -> ApiResponse[Campaign]:
"""Update campaign
- Update the given campaign. **Important:** You cannot use this endpoint to update campaigns if [campaign staging and revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) is enabled for your Application.
+ Update the given campaign. > [!important] You cannot use this endpoint to update campaigns if [campaign staging and > revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) > is enabled for your Application.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -54828,7 +54777,7 @@ def update_campaign_without_preload_content(
) -> RESTResponseType:
"""Update campaign
- Update the given campaign. **Important:** You cannot use this endpoint to update campaigns if [campaign staging and revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) is enabled for your Application.
+ Update the given campaign. > [!important] You cannot use this endpoint to update campaigns if [campaign staging and > revisions](https://docs.talon.one/docs/product/applications/managing-general-settings#campaign-staging-and-revisions) > is enabled for your Application.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -54940,8 +54889,6 @@ def _update_campaign_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -54968,7 +54915,7 @@ def update_collection(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
update_campaign_collection: Annotated[UpdateCampaignCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -54991,7 +54938,7 @@ def update_collection(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param update_campaign_collection: body (required)
:type update_campaign_collection: UpdateCampaignCollection
@@ -55048,7 +54995,7 @@ def update_collection_with_http_info(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
update_campaign_collection: Annotated[UpdateCampaignCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -55071,7 +55018,7 @@ def update_collection_with_http_info(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param update_campaign_collection: body (required)
:type update_campaign_collection: UpdateCampaignCollection
@@ -55128,7 +55075,7 @@ def update_collection_without_preload_content(
self,
application_id: Annotated[StrictInt, Field(description="The ID of the Application. It is displayed in your Talon.One deployment URL.")],
campaign_id: Annotated[StrictInt, Field(description="The ID of the campaign. It is displayed in your Talon.One deployment URL.")],
- collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint.")],
+ collection_id: Annotated[StrictInt, Field(description="The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint.")],
update_campaign_collection: Annotated[UpdateCampaignCollection, Field(description="body")],
_request_timeout: Union[
None,
@@ -55151,7 +55098,7 @@ def update_collection_without_preload_content(
:type application_id: int
:param campaign_id: The ID of the campaign. It is displayed in your Talon.One deployment URL. (required)
:type campaign_id: int
- :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#operation/listCollectionsInApplication) endpoint. (required)
+ :param collection_id: The ID of the collection. You can get it with the [List collections in Application](#tag/Collections/operation/listCollectionsInApplication) endpoint. (required)
:type collection_id: int
:param update_campaign_collection: body (required)
:type update_campaign_collection: UpdateCampaignCollection
@@ -55264,8 +55211,6 @@ def _update_collection_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -55309,7 +55254,7 @@ def update_coupon(
) -> Coupon:
"""Update coupon
- Update the specified coupon. Important
With this PUT endpoint, if you do not explicitly set a value for the startDate, expiryDate, and recipientIntegrationId properties in your request, it is automatically set to null.
+ Update the specified coupon. > [!note] > With this `PUT` endpoint, if you do not explicitly set a value for the `startDate`, `expiryDate`, > and `recipientIntegrationId` properties in your request, it is automatically set to `null`.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55388,7 +55333,7 @@ def update_coupon_with_http_info(
) -> ApiResponse[Coupon]:
"""Update coupon
- Update the specified coupon. Important
With this PUT endpoint, if you do not explicitly set a value for the startDate, expiryDate, and recipientIntegrationId properties in your request, it is automatically set to null.
+ Update the specified coupon. > [!note] > With this `PUT` endpoint, if you do not explicitly set a value for the `startDate`, `expiryDate`, > and `recipientIntegrationId` properties in your request, it is automatically set to `null`.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55467,7 +55412,7 @@ def update_coupon_without_preload_content(
) -> RESTResponseType:
"""Update coupon
- Update the specified coupon. Important
With this PUT endpoint, if you do not explicitly set a value for the startDate, expiryDate, and recipientIntegrationId properties in your request, it is automatically set to null.
+ Update the specified coupon. > [!note] > With this `PUT` endpoint, if you do not explicitly set a value for the `startDate`, `expiryDate`, > and `recipientIntegrationId` properties in your request, it is automatically set to `null`.
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55585,8 +55530,6 @@ def _update_coupon_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -55629,7 +55572,7 @@ def update_coupon_batch(
) -> None:
"""Update coupons
- Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#operation/getCouponsWithoutTotalCount). Important
- Only send sequential requests to this endpoint.
- Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team.
- With this
PUT endpoint, if you do not explicitly set a value for the startDate and expiryDate properties in your request, it is automatically set to null.
To update a specific coupon, use [Update coupon](#operation/updateCoupon).
+ Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount). > [!note] **Note** > - Only send sequential requests to this endpoint. > - Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team. > - With this `PUT` endpoint, if you do not explicitly set a value for the `startDate` and `expiryDate` properties in your request, it is automatically set to `null`. To update a specific coupon, use [Update coupon](#tag/Coupons/operation/updateCoupon).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55704,7 +55647,7 @@ def update_coupon_batch_with_http_info(
) -> ApiResponse[None]:
"""Update coupons
- Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#operation/getCouponsWithoutTotalCount). Important
- Only send sequential requests to this endpoint.
- Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team.
- With this
PUT endpoint, if you do not explicitly set a value for the startDate and expiryDate properties in your request, it is automatically set to null.
To update a specific coupon, use [Update coupon](#operation/updateCoupon).
+ Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount). > [!note] **Note** > - Only send sequential requests to this endpoint. > - Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team. > - With this `PUT` endpoint, if you do not explicitly set a value for the `startDate` and `expiryDate` properties in your request, it is automatically set to `null`. To update a specific coupon, use [Update coupon](#tag/Coupons/operation/updateCoupon).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55779,7 +55722,7 @@ def update_coupon_batch_without_preload_content(
) -> RESTResponseType:
"""Update coupons
- Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#operation/getCouponsWithoutTotalCount). Important
- Only send sequential requests to this endpoint.
- Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team.
- With this
PUT endpoint, if you do not explicitly set a value for the startDate and expiryDate properties in your request, it is automatically set to null.
To update a specific coupon, use [Update coupon](#operation/updateCoupon).
+ Update all coupons or a specific batch of coupons in the given campaign. You can find the `batchId` on the **Coupons** page of your campaign in the Campaign Manager, or you can use [List coupons](#tag/Coupons/operation/getCouponsWithoutTotalCount). > [!note] **Note** > - Only send sequential requests to this endpoint. > - Requests to this endpoint time out after 30 minutes. If you hit a timeout, contact our support team. > - With this `PUT` endpoint, if you do not explicitly set a value for the `startDate` and `expiryDate` properties in your request, it is automatically set to `null`. To update a specific coupon, use [Update coupon](#tag/Coupons/operation/updateCoupon).
:param application_id: The ID of the Application. It is displayed in your Talon.One deployment URL. (required)
:type application_id: int
@@ -55884,8 +55827,6 @@ def _update_coupon_batch_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -56199,8 +56140,6 @@ def _update_loyalty_card_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -56520,8 +56459,6 @@ def _update_referral_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -56811,8 +56748,6 @@ def _update_role_v2_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -57123,8 +57058,6 @@ def _update_store_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
@@ -57414,8 +57347,6 @@ def _update_user_serialize(
# authentication setting
_auth_settings: List[str] = [
- 'management_key',
- 'manager_auth',
'api_key_v1'
]
diff --git a/talon_one/api_client.py b/talon_one/api_client.py
index 6e4dbd8..db2bb86 100644
--- a/talon_one/api_client.py
+++ b/talon_one/api_client.py
@@ -1,7 +1,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -68,6 +68,7 @@ class ApiClient:
'date': datetime.date,
'datetime': datetime.datetime,
'decimal': decimal.Decimal,
+ 'UUID': uuid.UUID,
'object': object,
}
_pool = None
@@ -90,7 +91,7 @@ def __init__(
self.default_headers[header_name] = header_value
self.cookie = cookie
# Set default User-Agent.
- self.user_agent = 'OpenAPI-Generator/26.06.0/python'
+ self.user_agent = 'OpenAPI-Generator/26.07.0/python'
self.client_side_validation = configuration.client_side_validation
def __enter__(self):
@@ -305,7 +306,7 @@ def response_deserialize(
response_text = None
return_data = None
try:
- if response_type == "bytearray":
+ if response_type in ("bytearray", "bytes"):
return_data = response_data.data
elif response_type == "file":
return_data = self.__deserialize_file(response_data)
@@ -467,6 +468,8 @@ def __deserialize(self, data, klass):
return self.__deserialize_datetime(data)
elif klass is decimal.Decimal:
return decimal.Decimal(data)
+ elif klass is uuid.UUID:
+ return uuid.UUID(data)
elif issubclass(klass, Enum):
return self.__deserialize_enum(data, klass)
else:
diff --git a/talon_one/configuration.py b/talon_one/configuration.py
index 74ee78a..25b95dc 100644
--- a/talon_one/configuration.py
+++ b/talon_one/configuration.py
@@ -1,7 +1,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -112,8 +112,6 @@
"AuthSettings",
{
"api_key_v1": APIKeyAuthSetting,
- "manager_auth": APIKeyAuthSetting,
- "management_key": APIKeyAuthSetting,
},
total=False,
)
@@ -158,6 +156,8 @@ class Configuration:
string values to replace variables in templated server configuration.
The validation of enums is performed for variables with defined enum
values before.
+ :param verify_ssl: bool - Set this to false to skip verifying SSL certificate
+ when calling API from https server.
:param ssl_ca_cert: str - the path to a file of concatenated CA certificates
in PEM format.
:param retries: int | urllib3.util.retry.Retry - Retry configuration.
@@ -165,6 +165,16 @@ class Configuration:
in PEM (str) or DER (bytes) format.
:param cert_file: the path to a client certificate file, for mTLS.
:param key_file: the path to a client key file, for mTLS.
+ :param assert_hostname: Set this to True/False to enable/disable SSL hostname verification.
+ :param tls_server_name: SSL/TLS Server Name Indication (SNI). Set this to the SNI value expected by the server.
+ :param connection_pool_maxsize: Connection pool max size. None in the constructor is coerced to 100 for async and cpu_count * 5 for sync.
+ :param proxy: Proxy URL.
+ :param proxy_headers: Proxy headers.
+ :param safe_chars_for_path_param: Safe characters for path parameter encoding.
+ :param client_side_validation: Enable client-side validation. Default True.
+ :param socket_options: Options to pass down to the underlying urllib3 socket.
+ :param datetime_format: Datetime format string for serialization.
+ :param date_format: Date format string for serialization.
:Example:
@@ -208,6 +218,17 @@ def __init__(
ca_cert_data: Optional[Union[str, bytes]] = None,
cert_file: Optional[str]=None,
key_file: Optional[str]=None,
+ verify_ssl: bool=True,
+ assert_hostname: Optional[bool]=None,
+ tls_server_name: Optional[str]=None,
+ connection_pool_maxsize: Optional[int]=None,
+ proxy: Optional[str]=None,
+ proxy_headers: Optional[Any]=None,
+ safe_chars_for_path_param: str='',
+ client_side_validation: bool=True,
+ socket_options: Optional[Any]=None,
+ datetime_format: str="%Y-%m-%dT%H:%M:%S.%f%z",
+ date_format: str="%Y-%m-%d",
*,
debug: Optional[bool] = None,
) -> None:
@@ -277,7 +298,7 @@ def __init__(
"""Debug switch
"""
- self.verify_ssl = True
+ self.verify_ssl = verify_ssl
"""SSL/TLS verification
Set this to false to skip verifying SSL certificate when calling API
from https server.
@@ -295,46 +316,43 @@ def __init__(
self.key_file = key_file
"""client key file
"""
- self.assert_hostname = None
+ self.assert_hostname = assert_hostname
"""Set this to True/False to enable/disable SSL hostname verification.
"""
- self.tls_server_name = None
+ self.tls_server_name = tls_server_name
"""SSL/TLS Server Name Indication (SNI)
Set this to the SNI value expected by the server.
"""
- self.connection_pool_maxsize = multiprocessing.cpu_count() * 5
+ self.connection_pool_maxsize = connection_pool_maxsize if connection_pool_maxsize is not None else multiprocessing.cpu_count() * 5
"""urllib3 connection pool's maximum number of connections saved
- per pool. urllib3 uses 1 connection as default value, but this is
- not the best value when you are making a lot of possibly parallel
- requests to the same host, which is often the case here.
- cpu_count * 5 is used as default value to increase performance.
+ per pool. None in the constructor is coerced to cpu_count * 5.
"""
- self.proxy: Optional[str] = None
+ self.proxy = proxy
"""Proxy URL
"""
- self.proxy_headers = None
+ self.proxy_headers = proxy_headers
"""Proxy headers
"""
- self.safe_chars_for_path_param = ''
+ self.safe_chars_for_path_param = safe_chars_for_path_param
"""Safe chars for path_param
"""
self.retries = retries
"""Retry configuration
"""
# Enable client side validation
- self.client_side_validation = True
+ self.client_side_validation = client_side_validation
- self.socket_options = None
+ self.socket_options = socket_options
"""Options to pass down to the underlying urllib3 socket
"""
- self.datetime_format = "%Y-%m-%dT%H:%M:%S.%f%z"
+ self.datetime_format = datetime_format
"""datetime format
"""
- self.date_format = "%Y-%m-%d"
+ self.date_format = date_format
"""date format
"""
@@ -525,24 +543,6 @@ def auth_settings(self)-> AuthSettings:
'api_key_v1',
),
}
- if 'manager_auth' in self.api_key:
- auth['manager_auth'] = {
- 'type': 'api_key',
- 'in': 'header',
- 'key': 'Authorization',
- 'value': self.get_api_key_with_prefix(
- 'manager_auth',
- ),
- }
- if 'management_key' in self.api_key:
- auth['management_key'] = {
- 'type': 'api_key',
- 'in': 'header',
- 'key': 'Authorization',
- 'value': self.get_api_key_with_prefix(
- 'management_key',
- ),
- }
return auth
def to_debug_report(self) -> str:
@@ -554,7 +554,7 @@ def to_debug_report(self) -> str:
"OS: {env}\n"\
"Python Version: {pyversion}\n"\
"Version of the API: \n"\
- "SDK Package Version: 26.06.0".\
+ "SDK Package Version: 26.07.0".\
format(env=sys.platform, pyversion=sys.version)
def get_host_settings(self) -> List[HostSetting]:
diff --git a/talon_one/exceptions.py b/talon_one/exceptions.py
index 1a7b1c2..4fdcd02 100644
--- a/talon_one/exceptions.py
+++ b/talon_one/exceptions.py
@@ -1,7 +1,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/talon_one/models/__init__.py b/talon_one/models/__init__.py
index 371fd31..1fe5263 100644
--- a/talon_one/models/__init__.py
+++ b/talon_one/models/__init__.py
@@ -4,7 +4,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -225,6 +225,9 @@
from talon_one.models.effect import Effect
from talon_one.models.effect_entity import EffectEntity
from talon_one.models.email_entity import EmailEntity
+from talon_one.models.embedded_analytics_configuration import EmbeddedAnalyticsConfiguration
+from talon_one.models.embedded_analytics_configuration_dashboards import EmbeddedAnalyticsConfigurationDashboards
+from talon_one.models.embedded_dashboard_configuration import EmbeddedDashboardConfiguration
from talon_one.models.endpoint import Endpoint
from talon_one.models.entity import Entity
from talon_one.models.entity_with_talang_visible_id import EntityWithTalangVisibleID
@@ -243,6 +246,9 @@
from talon_one.models.experiment_campaign_copy import ExperimentCampaignCopy
from talon_one.models.experiment_copy import ExperimentCopy
from talon_one.models.experiment_copy_experiment import ExperimentCopyExperiment
+from talon_one.models.experiment_list_results import ExperimentListResults
+from talon_one.models.experiment_list_results_request import ExperimentListResultsRequest
+from talon_one.models.experiment_result import ExperimentResult
from talon_one.models.experiment_results import ExperimentResults
from talon_one.models.experiment_variant import ExperimentVariant
from talon_one.models.experiment_variant_allocation import ExperimentVariantAllocation
@@ -321,6 +327,8 @@
from talon_one.models.get_users200_response import GetUsers200Response
from talon_one.models.get_webhooks200_response import GetWebhooks200Response
from talon_one.models.giveaway import Giveaway
+from talon_one.models.giveaway_pool_notification import GiveawayPoolNotification
+from talon_one.models.giveaway_pool_notification_data import GiveawayPoolNotificationData
from talon_one.models.giveaways_pool import GiveawaysPool
from talon_one.models.hidden_conditions_effects import HiddenConditionsEffects
from talon_one.models.history import History
@@ -562,6 +570,7 @@
from talon_one.models.role_v2_permissions import RoleV2Permissions
from talon_one.models.role_v2_readonly import RoleV2Readonly
from talon_one.models.role_v2_roles_group import RoleV2RolesGroup
+from talon_one.models.roles_v2_thresholds import RolesV2Thresholds
from talon_one.models.rollback_added_loyalty_points_effect_props import RollbackAddedLoyaltyPointsEffectProps
from talon_one.models.rollback_coupon_effect_props import RollbackCouponEffectProps
from talon_one.models.rollback_deducted_loyalty_points_effect_props import RollbackDeductedLoyaltyPointsEffectProps
@@ -570,6 +579,7 @@
from talon_one.models.rollback_referral_effect_props import RollbackReferralEffectProps
from talon_one.models.rule import Rule
from talon_one.models.rule_failure_reason import RuleFailureReason
+from talon_one.models.rule_metadata import RuleMetadata
from talon_one.models.ruleset import Ruleset
from talon_one.models.sso_config import SSOConfig
from talon_one.models.saml_connection import SamlConnection
diff --git a/talon_one/models/accept_coupon_effect_props.py b/talon_one/models/accept_coupon_effect_props.py
index 9abed04..a94af62 100644
--- a/talon_one/models/accept_coupon_effect_props.py
+++ b/talon_one/models/accept_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AcceptCouponEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class AcceptCouponEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/accept_referral_effect_props.py b/talon_one/models/accept_referral_effect_props.py
index 2b4dd02..9874c69 100644
--- a/talon_one/models/accept_referral_effect_props.py
+++ b/talon_one/models/accept_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AcceptReferralEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class AcceptReferralEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/access_log_entry.py b/talon_one/models/access_log_entry.py
index 6509ab7..b95fdb7 100644
--- a/talon_one/models/access_log_entry.py
+++ b/talon_one/models/access_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccessLogEntry(BaseModel):
"""
@@ -37,7 +38,8 @@ class AccessLogEntry(BaseModel):
__properties: ClassVar[List[str]] = ["uuid", "status", "method", "requestUri", "time", "requestPayload", "responsePayload"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account.py b/talon_one/models/account.py
index c833b39..ea26417 100644
--- a/talon_one/models/account.py
+++ b/talon_one/models/account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Account(BaseModel):
"""
@@ -56,7 +57,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_additional_cost.py b/talon_one/models/account_additional_cost.py
index 50be43e..a06f2a8 100644
--- a/talon_one/models/account_additional_cost.py
+++ b/talon_one/models/account_additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountAdditionalCost(BaseModel):
"""
@@ -63,7 +64,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -75,8 +77,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_analytics.py b/talon_one/models/account_analytics.py
index bbbabc1..f325df1 100644
--- a/talon_one/models/account_analytics.py
+++ b/talon_one/models/account_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountAnalytics(BaseModel):
"""
@@ -50,7 +51,8 @@ class AccountAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["applications", "liveApplications", "sandboxApplications", "campaigns", "activeCampaigns", "liveActiveCampaigns", "coupons", "activeCoupons", "expiredCoupons", "referralCodes", "activeReferralCodes", "expiredReferralCodes", "activeRules", "users", "roles", "customAttributes", "webhooks", "loyaltyPrograms", "liveLoyaltyPrograms", "lastUpdatedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic.py b/talon_one/models/account_dashboard_statistic.py
index b125ad2..fbfe540 100644
--- a/talon_one/models/account_dashboard_statistic.py
+++ b/talon_one/models/account_dashboard_statistic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.account_dashboard_statistic_revenue import AccountDashboardStatisticRevenue
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatistic(BaseModel):
"""
@@ -39,7 +40,8 @@ class AccountDashboardStatistic(BaseModel):
__properties: ClassVar[List[str]] = ["revenue", "discounts", "loyaltyPoints", "referrals", "campaigns"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic_campaigns.py b/talon_one/models/account_dashboard_statistic_campaigns.py
index 290a0ad..5feb699 100644
--- a/talon_one/models/account_dashboard_statistic_campaigns.py
+++ b/talon_one/models/account_dashboard_statistic_campaigns.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatisticCampaigns(BaseModel):
"""
@@ -32,7 +33,8 @@ class AccountDashboardStatisticCampaigns(BaseModel):
__properties: ClassVar[List[str]] = ["live", "endingSoon", "lowOnBudget"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic_discount.py b/talon_one/models/account_dashboard_statistic_discount.py
index 8bdf1fd..ebfce77 100644
--- a/talon_one/models/account_dashboard_statistic_discount.py
+++ b/talon_one/models/account_dashboard_statistic_discount.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatisticDiscount(BaseModel):
"""
@@ -33,7 +34,8 @@ class AccountDashboardStatisticDiscount(BaseModel):
__properties: ClassVar[List[str]] = ["total", "average", "datetime"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic_loyalty_points.py b/talon_one/models/account_dashboard_statistic_loyalty_points.py
index c6f5207..c318f45 100644
--- a/talon_one/models/account_dashboard_statistic_loyalty_points.py
+++ b/talon_one/models/account_dashboard_statistic_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatisticLoyaltyPoints(BaseModel):
"""
@@ -32,7 +33,8 @@ class AccountDashboardStatisticLoyaltyPoints(BaseModel):
__properties: ClassVar[List[str]] = ["total", "datetime"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic_referrals.py b/talon_one/models/account_dashboard_statistic_referrals.py
index 2e2697d..830bb3e 100644
--- a/talon_one/models/account_dashboard_statistic_referrals.py
+++ b/talon_one/models/account_dashboard_statistic_referrals.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatisticReferrals(BaseModel):
"""
@@ -32,7 +33,8 @@ class AccountDashboardStatisticReferrals(BaseModel):
__properties: ClassVar[List[str]] = ["total", "datetime"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_dashboard_statistic_revenue.py b/talon_one/models/account_dashboard_statistic_revenue.py
index 306f6cc..240a0fa 100644
--- a/talon_one/models/account_dashboard_statistic_revenue.py
+++ b/talon_one/models/account_dashboard_statistic_revenue.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountDashboardStatisticRevenue(BaseModel):
"""
@@ -33,7 +34,8 @@ class AccountDashboardStatisticRevenue(BaseModel):
__properties: ClassVar[List[str]] = ["total", "influenced", "datetime"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_entity.py b/talon_one/models/account_entity.py
index d13aa8c..2f8dffb 100644
--- a/talon_one/models/account_entity.py
+++ b/talon_one/models/account_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class AccountEntity(BaseModel):
__properties: ClassVar[List[str]] = ["accountId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/account_limits.py b/talon_one/models/account_limits.py
index 07f8ddf..1892bcb 100644
--- a/talon_one/models/account_limits.py
+++ b/talon_one/models/account_limits.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AccountLimits(BaseModel):
"""
@@ -43,7 +44,8 @@ class AccountLimits(BaseModel):
__properties: ClassVar[List[str]] = ["liveApplications", "sandboxApplications", "activeCampaigns", "coupons", "referralCodes", "activeRules", "liveLoyaltyPrograms", "sandboxLoyaltyPrograms", "webhooks", "users", "apiVolume", "promotionTypes", "SecondaryDeploymentPrice", "currencyCode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement.py b/talon_one/models/achievement.py
index 41e6017..ba2f718 100644
--- a/talon_one/models/achievement.py
+++ b/talon_one/models/achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.time_point import TimePoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Achievement(BaseModel):
"""
@@ -87,7 +88,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -99,8 +101,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_additional_properties.py b/talon_one/models/achievement_additional_properties.py
index af550e3..cb8f0b2 100644
--- a/talon_one/models/achievement_additional_properties.py
+++ b/talon_one/models/achievement_additional_properties.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementAdditionalProperties(BaseModel):
"""
@@ -44,7 +45,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_additional_properties_v2.py b/talon_one/models/achievement_additional_properties_v2.py
index da07c2f..57c180b 100644
--- a/talon_one/models/achievement_additional_properties_v2.py
+++ b/talon_one/models/achievement_additional_properties_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementAdditionalPropertiesV2(BaseModel):
"""
@@ -43,7 +44,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_base.py b/talon_one/models/achievement_base.py
index ccfad9b..1410747 100644
--- a/talon_one/models/achievement_base.py
+++ b/talon_one/models/achievement_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.time_point import TimePoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementBase(BaseModel):
"""
@@ -73,7 +74,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -85,8 +87,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_base_v2.py b/talon_one/models/achievement_base_v2.py
index 50e9164..ff6d4a8 100644
--- a/talon_one/models/achievement_base_v2.py
+++ b/talon_one/models/achievement_base_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementBaseV2(BaseModel):
"""
@@ -74,7 +75,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -86,8 +88,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_progress.py b/talon_one/models/achievement_progress.py
index d574e4b..c7d1ece 100644
--- a/talon_one/models/achievement_progress.py
+++ b/talon_one/models/achievement_progress.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementProgress(BaseModel):
"""
@@ -42,7 +43,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_progress_with_definition.py b/talon_one/models/achievement_progress_with_definition.py
index fde5289..caf618c 100644
--- a/talon_one/models/achievement_progress_with_definition.py
+++ b/talon_one/models/achievement_progress_with_definition.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementProgressWithDefinition(BaseModel):
"""
@@ -75,7 +76,8 @@ def achievement_activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -87,8 +89,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_reference.py b/talon_one/models/achievement_reference.py
index d19fb06..8cc8ca7 100644
--- a/talon_one/models/achievement_reference.py
+++ b/talon_one/models/achievement_reference.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementReference(BaseModel):
"""
@@ -33,7 +34,8 @@ class AchievementReference(BaseModel):
__properties: ClassVar[List[str]] = ["achievementId", "applicationId", "applicationName", "campaignId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_status_entry.py b/talon_one/models/achievement_status_entry.py
index 47e8607..125c011 100644
--- a/talon_one/models/achievement_status_entry.py
+++ b/talon_one/models/achievement_status_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.time_point import TimePoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementStatusEntry(BaseModel):
"""
@@ -86,7 +87,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -98,8 +100,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/achievement_v2.py b/talon_one/models/achievement_v2.py
index 3fca384..45710c4 100644
--- a/talon_one/models/achievement_v2.py
+++ b/talon_one/models/achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AchievementV2(BaseModel):
"""
@@ -90,7 +91,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -102,8 +104,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/activate_loyalty_points.py b/talon_one/models/activate_loyalty_points.py
index 0cf8c4d..6a3821b 100644
--- a/talon_one/models/activate_loyalty_points.py
+++ b/talon_one/models/activate_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,17 +23,19 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ActivateLoyaltyPoints(BaseModel):
"""
Activate loyalty points
""" # noqa: E501
- transaction_uuids: Optional[Annotated[List[UUID], Field(min_length=1, max_length=50)]] = Field(default=None, description="An array of transaction UUIDs used to activate specific pending point transactions. If provided, do not include the `sessionId` parameter. ", alias="transactionUUIDs")
+ transaction_uuids: Optional[Annotated[List[UUID], Field(min_length=1, max_length=50)]] = Field(default=None, description="An array of transaction UUIDs used to activate specific pending point transactions. If provided, do not include the `sessionId` parameter. ", alias="transactionUUIDs")
session_id: Optional[Annotated[str, Field(min_length=1, strict=True)]] = Field(default=None, description="The ID of the session containing the pending point transactions to activate. If provided, do not include the `transactionUUIDs` parameter. ", alias="sessionId")
__properties: ClassVar[List[str]] = ["transactionUUIDs", "sessionId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/activate_loyalty_points_response.py b/talon_one/models/activate_loyalty_points_response.py
index 6fed735..e2d05cc 100644
--- a/talon_one/models/activate_loyalty_points_response.py
+++ b/talon_one/models/activate_loyalty_points_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_ledger_entry import LoyaltyLedgerEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ActivateLoyaltyPointsResponse(BaseModel):
"""
@@ -31,7 +32,8 @@ class ActivateLoyaltyPointsResponse(BaseModel):
__properties: ClassVar[List[str]] = ["ledgerEntries"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/activate_user_request.py b/talon_one/models/activate_user_request.py
index 11a9ddc..f3aa5f8 100644
--- a/talon_one/models/activate_user_request.py
+++ b/talon_one/models/activate_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ActivateUserRequest(BaseModel):
"""
@@ -30,7 +31,8 @@ class ActivateUserRequest(BaseModel):
__properties: ClassVar[List[str]] = ["email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_free_item_effect_props.py b/talon_one/models/add_free_item_effect_props.py
index 7d9c51d..58c45bb 100644
--- a/talon_one/models/add_free_item_effect_props.py
+++ b/talon_one/models/add_free_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddFreeItemEffectProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class AddFreeItemEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["sku", "name", "desiredQuantity"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_item_catalog_action.py b/talon_one/models/add_item_catalog_action.py
index 93bae52..2e7ef58 100644
--- a/talon_one/models/add_item_catalog_action.py
+++ b/talon_one/models/add_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.product import Product
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddItemCatalogAction(BaseModel):
"""
@@ -35,7 +36,8 @@ class AddItemCatalogAction(BaseModel):
__properties: ClassVar[List[str]] = ["sku", "price", "attributes", "product", "replaceIfExists"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_loyalty_points.py b/talon_one/models/add_loyalty_points.py
index b37d444..daa7b66 100644
--- a/talon_one/models/add_loyalty_points.py
+++ b/talon_one/models/add_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddLoyaltyPoints(BaseModel):
"""
@@ -39,7 +40,8 @@ class AddLoyaltyPoints(BaseModel):
__properties: ClassVar[List[str]] = ["points", "name", "validityDuration", "validUntil", "pendingDuration", "pendingUntil", "subledgerId", "applicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_loyalty_points_effect_props.py b/talon_one/models/add_loyalty_points_effect_props.py
index 3e0addc..9efa160 100644
--- a/talon_one/models/add_loyalty_points_effect_props.py
+++ b/talon_one/models/add_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddLoyaltyPointsEffectProps(BaseModel):
"""
@@ -57,7 +58,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -69,8 +71,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_price_adjustment_catalog_action.py b/talon_one/models/add_price_adjustment_catalog_action.py
index ca97290..a491d28 100644
--- a/talon_one/models/add_price_adjustment_catalog_action.py
+++ b/talon_one/models/add_price_adjustment_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,17 +22,19 @@
from talon_one.models.new_price_adjustment import NewPriceAdjustment
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddPriceAdjustmentCatalogAction(BaseModel):
"""
- The specific properties of the \"ADD_PRICE_ADJUSTMENT\" catalog sync action.
+ The specific properties of the \"ADD_PRICE_ADJUSTMENT\" catalog sync action. **Note:** You can only use this object if the `Beta` **price types** feature is enabled for your Application. To enable it, contact your Technical Account Manager.
""" # noqa: E501
sku: StrictStr = Field(description="The SKU of the item for which the price is being adjusted.")
adjustments: List[NewPriceAdjustment] = Field(description="A list of adjustments to apply to a given item.")
__properties: ClassVar[List[str]] = ["sku", "adjustments"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/add_to_audience_effect_props.py b/talon_one/models/add_to_audience_effect_props.py
index 07527c1..2547454 100644
--- a/talon_one/models/add_to_audience_effect_props.py
+++ b/talon_one/models/add_to_audience_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddToAudienceEffectProps(BaseModel):
"""
@@ -33,7 +34,8 @@ class AddToAudienceEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["audienceId", "audienceName", "profileIntegrationId", "profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/added_deducted_points_balances_action.py b/talon_one/models/added_deducted_points_balances_action.py
index cc1324e..4166e8d 100644
--- a/talon_one/models/added_deducted_points_balances_action.py
+++ b/talon_one/models/added_deducted_points_balances_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddedDeductedPointsBalancesAction(BaseModel):
"""
@@ -44,7 +45,8 @@ def operation_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/added_deducted_points_balances_notification.py b/talon_one/models/added_deducted_points_balances_notification.py
index 5a3a734..85f1ace 100644
--- a/talon_one/models/added_deducted_points_balances_notification.py
+++ b/talon_one/models/added_deducted_points_balances_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.added_deducted_points_balances_action import AddedDeductedPointsBalancesAction
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddedDeductedPointsBalancesNotification(BaseModel):
"""
@@ -55,7 +56,8 @@ def type_of_change_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/added_deducted_points_balances_notification_policy.py b/talon_one/models/added_deducted_points_balances_notification_policy.py
index 206aa7c..f86a765 100644
--- a/talon_one/models/added_deducted_points_balances_notification_policy.py
+++ b/talon_one/models/added_deducted_points_balances_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddedDeductedPointsBalancesNotificationPolicy(BaseModel):
"""
@@ -40,7 +41,8 @@ def scopes_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/added_deducted_points_notification.py b/talon_one/models/added_deducted_points_notification.py
index f692fad..6b10f5a 100644
--- a/talon_one/models/added_deducted_points_notification.py
+++ b/talon_one/models/added_deducted_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddedDeductedPointsNotification(BaseModel):
"""
@@ -67,7 +68,8 @@ def operation_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -79,8 +81,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/added_deducted_points_notification_policy.py b/talon_one/models/added_deducted_points_notification_policy.py
index cdf189c..1b6324a 100644
--- a/talon_one/models/added_deducted_points_notification_policy.py
+++ b/talon_one/models/added_deducted_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AddedDeductedPointsNotificationPolicy(BaseModel):
"""
@@ -40,7 +41,8 @@ def scopes_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/additional_campaign_properties.py b/talon_one/models/additional_campaign_properties.py
index 047bfc4..3aa0625 100644
--- a/talon_one/models/additional_campaign_properties.py
+++ b/talon_one/models/additional_campaign_properties.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.campaign_budget import CampaignBudget
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AdditionalCampaignProperties(BaseModel):
"""
@@ -63,7 +64,8 @@ def frontend_state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -75,8 +77,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/additional_cost.py b/talon_one/models/additional_cost.py
index a1efbf6..317d8aa 100644
--- a/talon_one/models/additional_cost.py
+++ b/talon_one/models/additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AdditionalCost(BaseModel):
"""
@@ -30,7 +31,8 @@ class AdditionalCost(BaseModel):
__properties: ClassVar[List[str]] = ["price"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/adjustment_details.py b/talon_one/models/adjustment_details.py
index 476d81d..fc6b837 100644
--- a/talon_one/models/adjustment_details.py
+++ b/talon_one/models/adjustment_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AdjustmentDetails(BaseModel):
"""
@@ -32,7 +33,8 @@ class AdjustmentDetails(BaseModel):
__properties: ClassVar[List[str]] = ["referenceId", "selectedPriceType", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_data_point.py b/talon_one/models/analytics_data_point.py
index c44f9c5..efe2677 100644
--- a/talon_one/models/analytics_data_point.py
+++ b/talon_one/models/analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsDataPoint(BaseModel):
"""
@@ -31,7 +32,8 @@ class AnalyticsDataPoint(BaseModel):
__properties: ClassVar[List[str]] = ["total", "influenced"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_data_point_with_trend.py b/talon_one/models/analytics_data_point_with_trend.py
index 129045f..52182c0 100644
--- a/talon_one/models/analytics_data_point_with_trend.py
+++ b/talon_one/models/analytics_data_point_with_trend.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsDataPointWithTrend(BaseModel):
"""
@@ -31,7 +32,8 @@ class AnalyticsDataPointWithTrend(BaseModel):
__properties: ClassVar[List[str]] = ["value", "trend"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_data_point_with_trend_and_influenced_rate.py b/talon_one/models/analytics_data_point_with_trend_and_influenced_rate.py
index 817aa97..c4bb63d 100644
--- a/talon_one/models/analytics_data_point_with_trend_and_influenced_rate.py
+++ b/talon_one/models/analytics_data_point_with_trend_and_influenced_rate.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsDataPointWithTrendAndInfluencedRate(BaseModel):
"""
@@ -32,7 +33,8 @@ class AnalyticsDataPointWithTrendAndInfluencedRate(BaseModel):
__properties: ClassVar[List[str]] = ["value", "influencedRate", "trend"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_data_point_with_trend_and_uplift.py b/talon_one/models/analytics_data_point_with_trend_and_uplift.py
index c093cbc..bcc78c1 100644
--- a/talon_one/models/analytics_data_point_with_trend_and_uplift.py
+++ b/talon_one/models/analytics_data_point_with_trend_and_uplift.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsDataPointWithTrendAndUplift(BaseModel):
"""
@@ -32,7 +33,8 @@ class AnalyticsDataPointWithTrendAndUplift(BaseModel):
__properties: ClassVar[List[str]] = ["value", "uplift", "trend"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_product.py b/talon_one/models/analytics_product.py
index 78cd2c4..2e12678 100644
--- a/talon_one/models/analytics_product.py
+++ b/talon_one/models/analytics_product.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.analytics_data_point_with_trend import AnalyticsDataPointWithTrend
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsProduct(BaseModel):
"""
@@ -34,7 +35,8 @@ class AnalyticsProduct(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "catalogId", "unitsSold"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/analytics_sku.py b/talon_one/models/analytics_sku.py
index ff72f03..b0fea9f 100644
--- a/talon_one/models/analytics_sku.py
+++ b/talon_one/models/analytics_sku.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.analytics_data_point_with_trend import AnalyticsDataPointWithTrend
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AnalyticsSKU(BaseModel):
"""
@@ -37,7 +38,8 @@ class AnalyticsSKU(BaseModel):
__properties: ClassVar[List[str]] = ["id", "sku", "lastUpdated", "catalogId", "productId", "unitsSold"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/api_error.py b/talon_one/models/api_error.py
index 1775f71..e811235 100644
--- a/talon_one/models/api_error.py
+++ b/talon_one/models/api_error.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.error_source import ErrorSource
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class APIError(BaseModel):
"""
@@ -33,7 +34,8 @@ class APIError(BaseModel):
__properties: ClassVar[List[str]] = ["title", "details", "source"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application.py b/talon_one/models/application.py
index 21d448a..53b1630 100644
--- a/talon_one/models/application.py
+++ b/talon_one/models/application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.loyalty_program import LoyaltyProgram
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Application(BaseModel):
"""
@@ -86,7 +87,8 @@ def default_discount_additional_cost_per_item_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -98,8 +100,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_analytics_data_point.py b/talon_one/models/application_analytics_data_point.py
index 22a3a46..705119f 100644
--- a/talon_one/models/application_analytics_data_point.py
+++ b/talon_one/models/application_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.analytics_data_point import AnalyticsDataPoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationAnalyticsDataPoint(BaseModel):
"""
@@ -39,7 +40,8 @@ class ApplicationAnalyticsDataPoint(BaseModel):
__properties: ClassVar[List[str]] = ["startTime", "endTime", "totalRevenue", "sessionsCount", "avgItemsPerSession", "avgSessionValue", "totalDiscounts", "couponsCount"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_api_health.py b/talon_one/models/application_api_health.py
index f086069..cc30d75 100644
--- a/talon_one/models/application_api_health.py
+++ b/talon_one/models/application_api_health.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationApiHealth(BaseModel):
"""
@@ -39,7 +40,8 @@ def summary_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_api_key.py b/talon_one/models/application_api_key.py
index 26477a4..d824065 100644
--- a/talon_one/models/application_api_key.py
+++ b/talon_one/models/application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationAPIKey(BaseModel):
"""
@@ -60,7 +61,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -72,8 +74,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_campaign_analytics.py b/talon_one/models/application_campaign_analytics.py
index 6e43b96..aabfc84 100644
--- a/talon_one/models/application_campaign_analytics.py
+++ b/talon_one/models/application_campaign_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.analytics_data_point_with_trend_and_uplift import AnalyticsDataPointWithTrendAndUplift
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCampaignAnalytics(BaseModel):
"""
@@ -53,7 +54,8 @@ def campaign_state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_campaign_stats.py b/talon_one/models/application_campaign_stats.py
index 5e18a7a..c38a73b 100644
--- a/talon_one/models/application_campaign_stats.py
+++ b/talon_one/models/application_campaign_stats.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCampaignStats(BaseModel):
"""
@@ -35,7 +36,8 @@ class ApplicationCampaignStats(BaseModel):
__properties: ClassVar[List[str]] = ["disabled", "staged", "scheduled", "running", "expired", "archived"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_cif.py b/talon_one/models/application_cif.py
index cc90088..7408b29 100644
--- a/talon_one/models/application_cif.py
+++ b/talon_one/models/application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCIF(BaseModel):
"""
@@ -39,7 +40,8 @@ class ApplicationCIF(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "name", "description", "activeExpressionId", "modifiedBy", "createdBy", "modified", "applicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_cif_expression.py b/talon_one/models/application_cif_expression.py
index 9d902b1..796b681 100644
--- a/talon_one/models/application_cif_expression.py
+++ b/talon_one/models/application_cif_expression.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCIFExpression(BaseModel):
"""
@@ -36,7 +37,8 @@ class ApplicationCIFExpression(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "cartItemFilterId", "createdBy", "expression", "applicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_cif_references.py b/talon_one/models/application_cif_references.py
index 0c7168c..2ff5208 100644
--- a/talon_one/models/application_cif_references.py
+++ b/talon_one/models/application_cif_references.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_detail import CampaignDetail
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCIFReferences(BaseModel):
"""
@@ -32,7 +33,8 @@ class ApplicationCIFReferences(BaseModel):
__properties: ClassVar[List[str]] = ["applicationCartItemFilterId", "campaigns"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_customer.py b/talon_one/models/application_customer.py
index 5e087d4..e65a42b 100644
--- a/talon_one/models/application_customer.py
+++ b/talon_one/models/application_customer.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.loyalty_membership import LoyaltyMembership
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCustomer(BaseModel):
"""
@@ -39,13 +40,14 @@ class ApplicationCustomer(BaseModel):
total_sales: Union[StrictFloat, StrictInt] = Field(description="The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. ", alias="totalSales")
loyalty_memberships: Optional[List[LoyaltyMembership]] = Field(default=None, description="**DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. ", alias="loyaltyMemberships")
audience_memberships: Optional[List[AudienceMembership]] = Field(default=None, description="The audiences the customer belongs to.", alias="audienceMemberships")
- last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
+ last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
sandbox: Optional[StrictBool] = Field(default=None, description="An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). ")
advocate_integration_id: Optional[Annotated[str, Field(strict=True, max_length=1000)]] = Field(default=None, description="The Integration ID of the Customer Profile that referred this Customer in the Application.", alias="advocateIntegrationId")
__properties: ClassVar[List[str]] = ["id", "created", "integrationId", "attributes", "accountId", "closedSessions", "totalSales", "loyaltyMemberships", "audienceMemberships", "lastActivity", "sandbox", "advocateIntegrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_customer_entity.py b/talon_one/models/application_customer_entity.py
index 0cae81a..9127abb 100644
--- a/talon_one/models/application_customer_entity.py
+++ b/talon_one/models/application_customer_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationCustomerEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class ApplicationCustomerEntity(BaseModel):
__properties: ClassVar[List[str]] = ["profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_entity.py b/talon_one/models/application_entity.py
index 23ba321..9d62bc0 100644
--- a/talon_one/models/application_entity.py
+++ b/talon_one/models/application_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class ApplicationEntity(BaseModel):
__properties: ClassVar[List[str]] = ["applicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_event.py b/talon_one/models/application_event.py
index 6f03df2..f11a07c 100644
--- a/talon_one/models/application_event.py
+++ b/talon_one/models/application_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationEvent(BaseModel):
"""
@@ -44,7 +45,8 @@ class ApplicationEvent(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "profileId", "storeId", "storeIntegrationId", "sessionId", "type", "attributes", "effects", "ruleFailureReasons"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_notification.py b/talon_one/models/application_notification.py
index 4395825..eac7b47 100644
--- a/talon_one/models/application_notification.py
+++ b/talon_one/models/application_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationNotification(BaseModel):
"""
@@ -30,7 +31,8 @@ class ApplicationNotification(BaseModel):
__properties: ClassVar[List[str]] = ["event"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_referee.py b/talon_one/models/application_referee.py
index 490ad2e..dea98f0 100644
--- a/talon_one/models/application_referee.py
+++ b/talon_one/models/application_referee.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationReferee(BaseModel):
"""
@@ -37,7 +38,8 @@ class ApplicationReferee(BaseModel):
__properties: ClassVar[List[str]] = ["applicationId", "sessionId", "advocateIntegrationId", "friendIntegrationId", "code", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_session.py b/talon_one/models/application_session.py
index 67052f3..bc65196 100644
--- a/talon_one/models/application_session.py
+++ b/talon_one/models/application_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.cart_item import CartItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationSession(BaseModel):
"""
@@ -54,7 +55,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -66,8 +68,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_session_entity.py b/talon_one/models/application_session_entity.py
index c28e5c6..acd3d27 100644
--- a/talon_one/models/application_session_entity.py
+++ b/talon_one/models/application_session_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationSessionEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class ApplicationSessionEntity(BaseModel):
__properties: ClassVar[List[str]] = ["sessionId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/application_store_entity.py b/talon_one/models/application_store_entity.py
index abe441b..e107362 100644
--- a/talon_one/models/application_store_entity.py
+++ b/talon_one/models/application_store_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ApplicationStoreEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class ApplicationStoreEntity(BaseModel):
__properties: ClassVar[List[str]] = ["storeId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/async_coupon_creation_response.py b/talon_one/models/async_coupon_creation_response.py
index 2b26f22..ff4df7f 100644
--- a/talon_one/models/async_coupon_creation_response.py
+++ b/talon_one/models/async_coupon_creation_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AsyncCouponCreationResponse(BaseModel):
"""
@@ -30,7 +31,8 @@ class AsyncCouponCreationResponse(BaseModel):
__properties: ClassVar[List[str]] = ["batchId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/async_coupon_deletion_job_response.py b/talon_one/models/async_coupon_deletion_job_response.py
index 6972ac9..39f5ff5 100644
--- a/talon_one/models/async_coupon_deletion_job_response.py
+++ b/talon_one/models/async_coupon_deletion_job_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AsyncCouponDeletionJobResponse(BaseModel):
"""
@@ -30,7 +31,8 @@ class AsyncCouponDeletionJobResponse(BaseModel):
__properties: ClassVar[List[str]] = ["id"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/async_coupons_data.py b/talon_one/models/async_coupons_data.py
index aa34d12..77aa530 100644
--- a/talon_one/models/async_coupons_data.py
+++ b/talon_one/models/async_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AsyncCouponsData(BaseModel):
"""
@@ -41,7 +42,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/attribute.py b/talon_one/models/attribute.py
index 2aadc45..f20c98d 100644
--- a/talon_one/models/attribute.py
+++ b/talon_one/models/attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Attribute(BaseModel):
"""
@@ -87,7 +88,8 @@ def allowed_subscriptions_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -99,8 +101,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/attributes_mandatory.py b/talon_one/models/attributes_mandatory.py
index f771f43..45c01b9 100644
--- a/talon_one/models/attributes_mandatory.py
+++ b/talon_one/models/attributes_mandatory.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AttributesMandatory(BaseModel):
"""
@@ -31,7 +32,8 @@ class AttributesMandatory(BaseModel):
__properties: ClassVar[List[str]] = ["campaigns", "coupons"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/attributes_settings.py b/talon_one/models/attributes_settings.py
index 7420da6..ecaa6f0 100644
--- a/talon_one/models/attributes_settings.py
+++ b/talon_one/models/attributes_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.attributes_mandatory import AttributesMandatory
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AttributesSettings(BaseModel):
"""
@@ -31,7 +32,8 @@ class AttributesSettings(BaseModel):
__properties: ClassVar[List[str]] = ["mandatory"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience.py b/talon_one/models/audience.py
index dfabbdb..20ed9a3 100644
--- a/talon_one/models/audience.py
+++ b/talon_one/models/audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Audience(BaseModel):
"""
@@ -41,7 +42,8 @@ class Audience(BaseModel):
__properties: ClassVar[List[str]] = ["accountId", "id", "created", "name", "sandbox", "description", "integration", "integrationId", "createdIn3rdParty", "lastUpdate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience_analytics.py b/talon_one/models/audience_analytics.py
index d77b44e..7602695 100644
--- a/talon_one/models/audience_analytics.py
+++ b/talon_one/models/audience_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AudienceAnalytics(BaseModel):
"""
@@ -31,7 +32,8 @@ class AudienceAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["audienceId", "membersCount"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience_customer.py b/talon_one/models/audience_customer.py
index 63fd4c5..271778d 100644
--- a/talon_one/models/audience_customer.py
+++ b/talon_one/models/audience_customer.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.loyalty_membership import LoyaltyMembership
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AudienceCustomer(BaseModel):
"""
@@ -39,14 +40,15 @@ class AudienceCustomer(BaseModel):
total_sales: Union[StrictFloat, StrictInt] = Field(description="The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. ", alias="totalSales")
loyalty_memberships: Optional[List[LoyaltyMembership]] = Field(default=None, description="**DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. ", alias="loyaltyMemberships")
audience_memberships: Optional[List[AudienceMembership]] = Field(default=None, description="The audiences the customer belongs to.", alias="audienceMemberships")
- last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
+ last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
sandbox: Optional[StrictBool] = Field(default=None, description="An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). ")
connected_applications_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of the IDs of the Applications that are connected to this customer profile.", alias="connectedApplicationsIds")
connected_audiences: Optional[List[StrictInt]] = Field(default=None, description="A list of the IDs of the audiences that are connected to this customer profile.", alias="connectedAudiences")
__properties: ClassVar[List[str]] = ["id", "created", "integrationId", "attributes", "accountId", "closedSessions", "totalSales", "loyaltyMemberships", "audienceMemberships", "lastActivity", "sandbox", "connectedApplicationsIds", "connectedAudiences"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience_integration_id.py b/talon_one/models/audience_integration_id.py
index 2832e32..c11b613 100644
--- a/talon_one/models/audience_integration_id.py
+++ b/talon_one/models/audience_integration_id.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AudienceIntegrationID(BaseModel):
"""
@@ -31,7 +32,8 @@ class AudienceIntegrationID(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience_membership.py b/talon_one/models/audience_membership.py
index 736bbe8..9d11be4 100644
--- a/talon_one/models/audience_membership.py
+++ b/talon_one/models/audience_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AudienceMembership(BaseModel):
"""
@@ -31,7 +32,8 @@ class AudienceMembership(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/audience_reference.py b/talon_one/models/audience_reference.py
index 70551d0..f28a980 100644
--- a/talon_one/models/audience_reference.py
+++ b/talon_one/models/audience_reference.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AudienceReference(BaseModel):
"""
@@ -33,7 +34,8 @@ class AudienceReference(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId", "id", "integration"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/award_giveaway_effect_props.py b/talon_one/models/award_giveaway_effect_props.py
index a857e85..c0ba757 100644
--- a/talon_one/models/award_giveaway_effect_props.py
+++ b/talon_one/models/award_giveaway_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class AwardGiveawayEffectProps(BaseModel):
"""
@@ -35,7 +36,8 @@ class AwardGiveawayEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["poolId", "poolName", "recipientIntegrationId", "giveawayId", "code"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_campaign.py b/talon_one/models/base_campaign.py
index e4e9339..1ccc00c 100644
--- a/talon_one/models/base_campaign.py
+++ b/talon_one/models/base_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseCampaign(BaseModel):
"""
@@ -36,7 +37,7 @@ class BaseCampaign(BaseModel):
end_time: Optional[datetime] = Field(default=None, description="Timestamp when the campaign will become inactive.", alias="endTime")
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this campaign.")
state: StrictStr = Field(description="A disabled or archived campaign is not evaluated for rules or coupons. ")
- active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
+ active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
tags: Annotated[List[Annotated[str, Field(min_length=1, strict=True, max_length=50)]], Field(max_length=50)] = Field(description="A list of tags for the campaign.")
reevaluate_on_return: Optional[StrictBool] = Field(default=None, description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: List[StrictStr] = Field(description="The features enabled in this campaign.")
@@ -46,7 +47,8 @@ class BaseCampaign(BaseModel):
campaign_groups: Optional[List[StrictInt]] = Field(default=None, description="The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. ", alias="campaignGroups")
type: Optional[StrictStr] = Field(default='advanced', description="The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. ")
linked_store_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. ", alias="linkedStoreIds")
- __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds"]
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
+ __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds", "couponAttributes"]
@field_validator('state')
def state_validate_enum(cls, value):
@@ -74,7 +76,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -86,8 +89,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -152,7 +154,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"limits": [LimitConfig.from_dict(_item) for _item in obj["limits"]] if obj.get("limits") is not None else None,
"campaignGroups": obj.get("campaignGroups"),
"type": obj.get("type") if obj.get("type") is not None else 'advanced',
- "linkedStoreIds": obj.get("linkedStoreIds")
+ "linkedStoreIds": obj.get("linkedStoreIds"),
+ "couponAttributes": obj.get("couponAttributes")
})
return _obj
diff --git a/talon_one/models/base_loyalty_program.py b/talon_one/models/base_loyalty_program.py
index 58440de..c4c974c 100644
--- a/talon_one/models/base_loyalty_program.py
+++ b/talon_one/models/base_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.code_generator_settings import CodeGeneratorSettings
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseLoyaltyProgram(BaseModel):
"""
@@ -87,7 +88,8 @@ def return_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -99,8 +101,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_notification.py b/talon_one/models/base_notification.py
index a27ec19..fdb3cec 100644
--- a/talon_one/models/base_notification.py
+++ b/talon_one/models/base_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.base_notification_webhook import BaseNotificationWebhook
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseNotification(BaseModel):
"""
@@ -43,7 +44,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_notification_entity.py b/talon_one/models/base_notification_entity.py
index 61abfc3..962ef28 100644
--- a/talon_one/models/base_notification_entity.py
+++ b/talon_one/models/base_notification_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseNotificationEntity(BaseModel):
"""
@@ -31,7 +32,8 @@ class BaseNotificationEntity(BaseModel):
__properties: ClassVar[List[str]] = ["policy", "enabled"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_notification_webhook.py b/talon_one/models/base_notification_webhook.py
index 5bae1b0..41205fb 100644
--- a/talon_one/models/base_notification_webhook.py
+++ b/talon_one/models/base_notification_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseNotificationWebhook(BaseModel):
"""
@@ -37,7 +38,8 @@ class BaseNotificationWebhook(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "modified", "url", "headers", "enabled"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_notifications.py b/talon_one/models/base_notifications.py
index da12150..dee900c 100644
--- a/talon_one/models/base_notifications.py
+++ b/talon_one/models/base_notifications.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.base_notification import BaseNotification
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseNotifications(BaseModel):
"""
@@ -31,7 +32,8 @@ class BaseNotifications(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/base_saml_connection.py b/talon_one/models/base_saml_connection.py
index fed891c..0a0c1e2 100644
--- a/talon_one/models/base_saml_connection.py
+++ b/talon_one/models/base_saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BaseSamlConnection(BaseModel):
"""
@@ -38,7 +39,8 @@ class BaseSamlConnection(BaseModel):
__properties: ClassVar[List[str]] = ["accountId", "name", "enabled", "issuer", "signOnURL", "signOutURL", "metadataURL", "audienceURI"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/best_prior_price.py b/talon_one/models/best_prior_price.py
index 61bce31..8d23a9c 100644
--- a/talon_one/models/best_prior_price.py
+++ b/talon_one/models/best_prior_price.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.best_prior_price_metadata import BestPriorPriceMetadata
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BestPriorPrice(BaseModel):
"""
@@ -38,7 +39,8 @@ class BestPriorPrice(BaseModel):
__properties: ClassVar[List[str]] = ["id", "sku", "observedAt", "contextId", "price", "metadata", "target"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/best_prior_price_metadata.py b/talon_one/models/best_prior_price_metadata.py
index b59d3df..abe2c83 100644
--- a/talon_one/models/best_prior_price_metadata.py
+++ b/talon_one/models/best_prior_price_metadata.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.influencing_campaign_details import InfluencingCampaignDetails
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BestPriorPriceMetadata(BaseModel):
"""
@@ -33,7 +34,8 @@ class BestPriorPriceMetadata(BaseModel):
__properties: ClassVar[List[str]] = ["influencingCampaignDetails", "adjustmentDetails"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/best_prior_price_request.py b/talon_one/models/best_prior_price_request.py
index 121f74c..eedcbca 100644
--- a/talon_one/models/best_prior_price_request.py
+++ b/talon_one/models/best_prior_price_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.best_prior_target import BestPriorTarget
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BestPriorPriceRequest(BaseModel):
"""
@@ -48,7 +49,8 @@ def timeframe_end_date_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -60,8 +62,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/best_prior_target.py b/talon_one/models/best_prior_target.py
index ac3af71..fba4b6d 100644
--- a/talon_one/models/best_prior_target.py
+++ b/talon_one/models/best_prior_target.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BestPriorTarget(BaseModel):
"""
@@ -38,7 +39,8 @@ def target_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/binding.py b/talon_one/models/binding.py
index 3bf97a7..4c731ff 100644
--- a/talon_one/models/binding.py
+++ b/talon_one/models/binding.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Binding(BaseModel):
"""
@@ -37,7 +38,8 @@ class Binding(BaseModel):
__properties: ClassVar[List[str]] = ["name", "type", "expression", "valueType", "minValue", "maxValue", "attributeId", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/blueprint.py b/talon_one/models/blueprint.py
index e69a297..7321de6 100644
--- a/talon_one/models/blueprint.py
+++ b/talon_one/models/blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.catalog_rule import CatalogRule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Blueprint(BaseModel):
"""
@@ -59,7 +60,8 @@ def source_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -71,8 +73,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/bulk_application_notification.py b/talon_one/models/bulk_application_notification.py
index d4319a7..55da5fd 100644
--- a/talon_one/models/bulk_application_notification.py
+++ b/talon_one/models/bulk_application_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_notification import ApplicationNotification
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BulkApplicationNotification(BaseModel):
"""
@@ -32,7 +33,8 @@ class BulkApplicationNotification(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/bulk_operation_on_campaigns.py b/talon_one/models/bulk_operation_on_campaigns.py
index 03aac58..293f6e4 100644
--- a/talon_one/models/bulk_operation_on_campaigns.py
+++ b/talon_one/models/bulk_operation_on_campaigns.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class BulkOperationOnCampaigns(BaseModel):
"""
@@ -41,7 +42,8 @@ def operation_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign.py b/talon_one/models/campaign.py
index b936fa5..f192216 100644
--- a/talon_one/models/campaign.py
+++ b/talon_one/models/campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Campaign(BaseModel):
"""
@@ -41,7 +42,7 @@ class Campaign(BaseModel):
end_time: Optional[datetime] = Field(default=None, description="Timestamp when the campaign will become inactive.", alias="endTime")
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this campaign.")
state: StrictStr = Field(description="A disabled or archived campaign is not evaluated for rules or coupons. ")
- active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
+ active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
tags: Annotated[List[Annotated[str, Field(min_length=1, strict=True, max_length=50)]], Field(max_length=50)] = Field(description="A list of tags for the campaign.")
reevaluate_on_return: StrictBool = Field(description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: List[StrictStr] = Field(description="The features enabled in this campaign.")
@@ -51,6 +52,7 @@ class Campaign(BaseModel):
campaign_groups: Optional[List[StrictInt]] = Field(default=None, description="The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. ", alias="campaignGroups")
type: Optional[StrictStr] = Field(default='advanced', description="The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. ")
linked_store_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. ", alias="linkedStoreIds")
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
budgets: Optional[List[CampaignBudget]] = Field(default=None, description="A list of all the budgets that are defined by this campaign and their usage. **Note:** Budgets that are not defined do not appear in this list and their usage is not counted until they are defined. ")
coupon_redemption_count: Optional[StrictInt] = Field(default=None, description="This property is **deprecated**. The count should be available under *budgets* property. Number of coupons redeemed in the campaign. ", alias="couponRedemptionCount")
referral_redemption_count: Optional[StrictInt] = Field(default=None, description="This property is **deprecated**. The count should be available under *budgets* property. Number of referral codes redeemed in the campaign. ", alias="referralRedemptionCount")
@@ -83,7 +85,7 @@ class Campaign(BaseModel):
current_revision_id: Optional[StrictInt] = Field(default=None, description="ID of the revision currently being modified for the campaign. ", alias="currentRevisionId")
current_revision_version_id: Optional[StrictInt] = Field(default=None, description="ID of the latest version applied on the current revision. ", alias="currentRevisionVersionId")
stage_revision: Optional[StrictBool] = Field(default=False, description="Flag for determining whether we use current revision when sending requests with staging API key. ", alias="stageRevision")
- __properties: ClassVar[List[str]] = ["id", "created", "applicationId", "userId", "name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds", "budgets", "couponRedemptionCount", "referralRedemptionCount", "discountCount", "discountEffectCount", "couponCreationCount", "customEffectCount", "referralCreationCount", "addFreeItemEffectCount", "awardedGiveawaysCount", "createdLoyaltyPointsCount", "createdLoyaltyPointsEffectCount", "redeemedLoyaltyPointsCount", "redeemedLoyaltyPointsEffectCount", "callApiEffectCount", "reservecouponEffectCount", "lastActivity", "updated", "createdBy", "updatedBy", "templateId", "frontendState", "storesImported", "valueMapsIds", "experimentId", "revisionFrontendState", "activeRevisionId", "activeRevisionVersionId", "version", "currentRevisionId", "currentRevisionVersionId", "stageRevision"]
+ __properties: ClassVar[List[str]] = ["id", "created", "applicationId", "userId", "name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds", "couponAttributes", "budgets", "couponRedemptionCount", "referralRedemptionCount", "discountCount", "discountEffectCount", "couponCreationCount", "customEffectCount", "referralCreationCount", "addFreeItemEffectCount", "awardedGiveawaysCount", "createdLoyaltyPointsCount", "createdLoyaltyPointsEffectCount", "redeemedLoyaltyPointsCount", "redeemedLoyaltyPointsEffectCount", "callApiEffectCount", "reservecouponEffectCount", "lastActivity", "updated", "createdBy", "updatedBy", "templateId", "frontendState", "storesImported", "valueMapsIds", "experimentId", "revisionFrontendState", "activeRevisionId", "activeRevisionVersionId", "version", "currentRevisionId", "currentRevisionVersionId", "stageRevision"]
@field_validator('state')
def state_validate_enum(cls, value):
@@ -128,7 +130,8 @@ def revision_frontend_state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -140,8 +143,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -218,6 +220,7 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"campaignGroups": obj.get("campaignGroups"),
"type": obj.get("type") if obj.get("type") is not None else 'advanced',
"linkedStoreIds": obj.get("linkedStoreIds"),
+ "couponAttributes": obj.get("couponAttributes"),
"budgets": [CampaignBudget.from_dict(_item) for _item in obj["budgets"]] if obj.get("budgets") is not None else None,
"couponRedemptionCount": obj.get("couponRedemptionCount"),
"referralRedemptionCount": obj.get("referralRedemptionCount"),
diff --git a/talon_one/models/campaign_activation_request.py b/talon_one/models/campaign_activation_request.py
index bee913a..f436d9f 100644
--- a/talon_one/models/campaign_activation_request.py
+++ b/talon_one/models/campaign_activation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignActivationRequest(BaseModel):
"""
@@ -31,7 +32,8 @@ class CampaignActivationRequest(BaseModel):
__properties: ClassVar[List[str]] = ["userIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_analytics.py b/talon_one/models/campaign_analytics.py
index 6aea941..26101b8 100644
--- a/talon_one/models/campaign_analytics.py
+++ b/talon_one/models/campaign_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignAnalytics(BaseModel):
"""
@@ -55,7 +56,8 @@ class CampaignAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["date", "campaignRevenue", "totalCampaignRevenue", "campaignRefund", "totalCampaignRefund", "campaignDiscountCosts", "totalCampaignDiscountCosts", "campaignRefundedDiscounts", "totalCampaignRefundedDiscounts", "campaignFreeItems", "totalCampaignFreeItems", "couponRedemptions", "totalCouponRedemptions", "couponRolledbackRedemptions", "totalCouponRolledbackRedemptions", "referralRedemptions", "totalReferralRedemptions", "couponsCreated", "totalCouponsCreated", "referralsCreated", "totalReferralsCreated", "addedLoyaltyPoints", "totalAddedLoyaltyPoints", "deductedLoyaltyPoints", "totalDeductedLoyaltyPoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_budget.py b/talon_one/models/campaign_budget.py
index cfe439d..7c9472a 100644
--- a/talon_one/models/campaign_budget.py
+++ b/talon_one/models/campaign_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignBudget(BaseModel):
"""
@@ -33,7 +34,8 @@ class CampaignBudget(BaseModel):
__properties: ClassVar[List[str]] = ["action", "limit", "counter"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_collection.py b/talon_one/models/campaign_collection.py
index 118b87b..30fe012 100644
--- a/talon_one/models/campaign_collection.py
+++ b/talon_one/models/campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCollection(BaseModel):
"""
@@ -49,7 +50,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -61,8 +63,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_collection_edited_notification.py b/talon_one/models/campaign_collection_edited_notification.py
index e5787d9..e29557a 100644
--- a/talon_one/models/campaign_collection_edited_notification.py
+++ b/talon_one/models/campaign_collection_edited_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_collection_edited_notification_item import CampaignCollectionEditedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCollectionEditedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_collection_edited_notification_item.py b/talon_one/models/campaign_collection_edited_notification_item.py
index 3203bbe..a8de47f 100644
--- a/talon_one/models/campaign_collection_edited_notification_item.py
+++ b/talon_one/models/campaign_collection_edited_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCollectionEditedNotificationItem(BaseModel):
"""
@@ -38,7 +39,8 @@ class CampaignCollectionEditedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "ruleset", "placeholders", "collection"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_collection_without_payload.py b/talon_one/models/campaign_collection_without_payload.py
index d7188f6..0b071da 100644
--- a/talon_one/models/campaign_collection_without_payload.py
+++ b/talon_one/models/campaign_collection_without_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCollectionWithoutPayload(BaseModel):
"""
@@ -48,7 +49,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -60,8 +62,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_copy.py b/talon_one/models/campaign_copy.py
index 88d667e..4c260cb 100644
--- a/talon_one/models/campaign_copy.py
+++ b/talon_one/models/campaign_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCopy(BaseModel):
"""
@@ -38,7 +39,8 @@ class CampaignCopy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "applicationIds", "description", "startTime", "endTime", "tags", "evaluationGroupId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_created_notification.py b/talon_one/models/campaign_created_notification.py
index 1d8c5c4..8f0e8dd 100644
--- a/talon_one/models/campaign_created_notification.py
+++ b/talon_one/models/campaign_created_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_created_notification_item import CampaignCreatedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCreatedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_created_notification_item.py b/talon_one/models/campaign_created_notification_item.py
index dcd531e..7e339eb 100644
--- a/talon_one/models/campaign_created_notification_item.py
+++ b/talon_one/models/campaign_created_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignCreatedNotificationItem(BaseModel):
"""
@@ -38,7 +39,8 @@ class CampaignCreatedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "ruleset", "placeholders", "evaluationPosition"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_deactivation_request.py b/talon_one/models/campaign_deactivation_request.py
index 283d03e..6ff4c22 100644
--- a/talon_one/models/campaign_deactivation_request.py
+++ b/talon_one/models/campaign_deactivation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignDeactivationRequest(BaseModel):
"""
@@ -31,7 +32,8 @@ class CampaignDeactivationRequest(BaseModel):
__properties: ClassVar[List[str]] = ["userIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_deleted_notification.py b/talon_one/models/campaign_deleted_notification.py
index 9249452..90175a8 100644
--- a/talon_one/models/campaign_deleted_notification.py
+++ b/talon_one/models/campaign_deleted_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_deleted_notification_item import CampaignDeletedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignDeletedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_deleted_notification_item.py b/talon_one/models/campaign_deleted_notification_item.py
index 5e4cd48..5472a5c 100644
--- a/talon_one/models/campaign_deleted_notification_item.py
+++ b/talon_one/models/campaign_deleted_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.campaign import Campaign
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignDeletedNotificationItem(BaseModel):
"""
@@ -34,7 +35,8 @@ class CampaignDeletedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "deletedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_detail.py b/talon_one/models/campaign_detail.py
index df5837e..75b50d1 100644
--- a/talon_one/models/campaign_detail.py
+++ b/talon_one/models/campaign_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignDetail(BaseModel):
"""
@@ -32,7 +33,8 @@ class CampaignDetail(BaseModel):
__properties: ClassVar[List[str]] = ["campaignId", "campaignName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_edited_notification.py b/talon_one/models/campaign_edited_notification.py
index a46b4c6..b699031 100644
--- a/talon_one/models/campaign_edited_notification.py
+++ b/talon_one/models/campaign_edited_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_edited_notification_item import CampaignEditedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEditedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_edited_notification_item.py b/talon_one/models/campaign_edited_notification_item.py
index 6432eaa..e3f0445 100644
--- a/talon_one/models/campaign_edited_notification_item.py
+++ b/talon_one/models/campaign_edited_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEditedNotificationItem(BaseModel):
"""
@@ -37,7 +38,8 @@ class CampaignEditedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "oldCampaign", "ruleset", "placeholders"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_entity.py b/talon_one/models/campaign_entity.py
index c71c394..60d4135 100644
--- a/talon_one/models/campaign_entity.py
+++ b/talon_one/models/campaign_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class CampaignEntity(BaseModel):
__properties: ClassVar[List[str]] = ["campaignId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_evaluation_group.py b/talon_one/models/campaign_evaluation_group.py
index 217f24c..4156bbe 100644
--- a/talon_one/models/campaign_evaluation_group.py
+++ b/talon_one/models/campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEvaluationGroup(BaseModel):
"""
@@ -52,7 +53,8 @@ def evaluation_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -64,8 +66,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_evaluation_position.py b/talon_one/models/campaign_evaluation_position.py
index f170009..1bc2c58 100644
--- a/talon_one/models/campaign_evaluation_position.py
+++ b/talon_one/models/campaign_evaluation_position.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEvaluationPosition(BaseModel):
"""
@@ -32,7 +33,8 @@ class CampaignEvaluationPosition(BaseModel):
__properties: ClassVar[List[str]] = ["groupId", "groupName", "position"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_evaluation_tree_changed_message.py b/talon_one/models/campaign_evaluation_tree_changed_message.py
index 7955166..f35d900 100644
--- a/talon_one/models/campaign_evaluation_tree_changed_message.py
+++ b/talon_one/models/campaign_evaluation_tree_changed_message.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_notification import ApplicationNotification
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEvaluationTreeChangedMessage(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_evaluation_tree_changed_notification.py b/talon_one/models/campaign_evaluation_tree_changed_notification.py
index feacc8e..d8a175d 100644
--- a/talon_one/models/campaign_evaluation_tree_changed_notification.py
+++ b/talon_one/models/campaign_evaluation_tree_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_set import CampaignSet
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignEvaluationTreeChangedNotification(BaseModel):
"""
@@ -33,7 +34,8 @@ class CampaignEvaluationTreeChangedNotification(BaseModel):
__properties: ClassVar[List[str]] = ["applicationId", "oldEvaluationTree", "evaluationTree"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_group.py b/talon_one/models/campaign_group.py
index dff31b3..13e5a7e 100644
--- a/talon_one/models/campaign_group.py
+++ b/talon_one/models/campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignGroup(BaseModel):
"""
@@ -39,7 +40,8 @@ class CampaignGroup(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "modified", "accountId", "name", "description", "subscribedApplicationsIds", "campaignIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_group_entity.py b/talon_one/models/campaign_group_entity.py
index 83d913b..f53231a 100644
--- a/talon_one/models/campaign_group_entity.py
+++ b/talon_one/models/campaign_group_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignGroupEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class CampaignGroupEntity(BaseModel):
__properties: ClassVar[List[str]] = ["campaignGroups"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_log_summary.py b/talon_one/models/campaign_log_summary.py
index e58674f..8b4a613 100644
--- a/talon_one/models/campaign_log_summary.py
+++ b/talon_one/models/campaign_log_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignLogSummary(BaseModel):
"""
@@ -42,7 +43,8 @@ def action_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_notification_base.py b/talon_one/models/campaign_notification_base.py
index a3953cb..c8fc07b 100644
--- a/talon_one/models/campaign_notification_base.py
+++ b/talon_one/models/campaign_notification_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignNotificationBase(BaseModel):
"""
@@ -38,7 +39,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_notification_generic.py b/talon_one/models/campaign_notification_generic.py
index 35c9435..e0824f8 100644
--- a/talon_one/models/campaign_notification_generic.py
+++ b/talon_one/models/campaign_notification_generic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignNotificationGeneric(BaseModel):
"""
@@ -39,7 +40,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_notification_item_base.py b/talon_one/models/campaign_notification_item_base.py
index 20d958a..df72775 100644
--- a/talon_one/models/campaign_notification_item_base.py
+++ b/talon_one/models/campaign_notification_item_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignNotificationItemBase(BaseModel):
"""
@@ -30,7 +31,8 @@ class CampaignNotificationItemBase(BaseModel):
__properties: ClassVar[List[str]] = ["Event"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_notification_policy.py b/talon_one/models/campaign_notification_policy.py
index 24abaf5..74a1b58 100644
--- a/talon_one/models/campaign_notification_policy.py
+++ b/talon_one/models/campaign_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignNotificationPolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class CampaignNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_ruleset_changed_notification.py b/talon_one/models/campaign_ruleset_changed_notification.py
index 396d633..e71458c 100644
--- a/talon_one/models/campaign_ruleset_changed_notification.py
+++ b/talon_one/models/campaign_ruleset_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_ruleset_changed_notification_item import CampaignRulesetChangedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignRulesetChangedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_ruleset_changed_notification_item.py b/talon_one/models/campaign_ruleset_changed_notification_item.py
index 91dbdd1..df613c4 100644
--- a/talon_one/models/campaign_ruleset_changed_notification_item.py
+++ b/talon_one/models/campaign_ruleset_changed_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignRulesetChangedNotificationItem(BaseModel):
"""
@@ -38,7 +39,8 @@ class CampaignRulesetChangedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "oldRuleset", "oldPlaceholders", "ruleset", "placeholders"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_search.py b/talon_one/models/campaign_search.py
index 1b862ab..bd9c1bd 100644
--- a/talon_one/models/campaign_search.py
+++ b/talon_one/models/campaign_search.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignSearch(BaseModel):
"""
@@ -30,7 +31,8 @@ class CampaignSearch(BaseModel):
__properties: ClassVar[List[str]] = ["attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_set.py b/talon_one/models/campaign_set.py
index 0ce4783..1237759 100644
--- a/talon_one/models/campaign_set.py
+++ b/talon_one/models/campaign_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.campaign_set_branch_node import CampaignSetBranchNode
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignSet(BaseModel):
"""
@@ -36,7 +37,8 @@ class CampaignSet(BaseModel):
__properties: ClassVar[List[str]] = ["applicationId", "id", "version", "set", "updatedBy"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_set_branch_node.py b/talon_one/models/campaign_set_branch_node.py
index f9888d6..8648bf3 100644
--- a/talon_one/models/campaign_set_branch_node.py
+++ b/talon_one/models/campaign_set_branch_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_set_node import CampaignSetNode
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignSetBranchNode(BaseModel):
"""
@@ -67,7 +68,8 @@ def evaluation_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -79,8 +81,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_set_leaf_node.py b/talon_one/models/campaign_set_leaf_node.py
index 7418e8f..ba1480a 100644
--- a/talon_one/models/campaign_set_leaf_node.py
+++ b/talon_one/models/campaign_set_leaf_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignSetLeafNode(BaseModel):
"""
@@ -38,7 +39,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_set_node.py b/talon_one/models/campaign_set_node.py
index ab06018..cce9a9b 100644
--- a/talon_one/models/campaign_set_node.py
+++ b/talon_one/models/campaign_set_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignSetNode(BaseModel):
"""
@@ -30,7 +31,8 @@ class CampaignSetNode(BaseModel):
__properties: ClassVar[List[str]] = ["type"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_state_changed_notification.py b/talon_one/models/campaign_state_changed_notification.py
index 3ab4e72..3acf40f 100644
--- a/talon_one/models/campaign_state_changed_notification.py
+++ b/talon_one/models/campaign_state_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_state_changed_notification_item import CampaignStateChangedNotificationItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignStateChangedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_state_changed_notification_item.py b/talon_one/models/campaign_state_changed_notification_item.py
index 40e60c5..0a8d6d1 100644
--- a/talon_one/models/campaign_state_changed_notification_item.py
+++ b/talon_one/models/campaign_state_changed_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignStateChangedNotificationItem(BaseModel):
"""
@@ -38,7 +39,8 @@ class CampaignStateChangedNotificationItem(BaseModel):
__properties: ClassVar[List[str]] = ["Event", "campaign", "oldState", "newState", "ruleset", "placeholders"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_store_budget.py b/talon_one/models/campaign_store_budget.py
index 4f224b2..b3d57b5 100644
--- a/talon_one/models/campaign_store_budget.py
+++ b/talon_one/models/campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.campaign_store_budget_limit_config import CampaignStoreBudgetLimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignStoreBudget(BaseModel):
"""
@@ -36,7 +37,8 @@ class CampaignStoreBudget(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "storeId", "limits"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_store_budget_limit_config.py b/talon_one/models/campaign_store_budget_limit_config.py
index a7ef62b..eb69fee 100644
--- a/talon_one/models/campaign_store_budget_limit_config.py
+++ b/talon_one/models/campaign_store_budget_limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignStoreBudgetLimitConfig(BaseModel):
"""
@@ -53,7 +54,8 @@ def entities_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_template.py b/talon_one/models/campaign_template.py
index 32c883f..f694797 100644
--- a/talon_one/models/campaign_template.py
+++ b/talon_one/models/campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -28,6 +28,7 @@
from talon_one.models.template_limit_config import TemplateLimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignTemplate(BaseModel):
"""
@@ -92,7 +93,8 @@ def campaign_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -104,8 +106,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_template_collection.py b/talon_one/models/campaign_template_collection.py
index b848df4..d0f4439 100644
--- a/talon_one/models/campaign_template_collection.py
+++ b/talon_one/models/campaign_template_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignTemplateCollection(BaseModel):
"""
@@ -39,7 +40,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_template_coupon_reservation_settings.py b/talon_one/models/campaign_template_coupon_reservation_settings.py
index 138ff9a..293ae10 100644
--- a/talon_one/models/campaign_template_coupon_reservation_settings.py
+++ b/talon_one/models/campaign_template_coupon_reservation_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignTemplateCouponReservationSettings(BaseModel):
"""
@@ -32,7 +33,8 @@ class CampaignTemplateCouponReservationSettings(BaseModel):
__properties: ClassVar[List[str]] = ["reservationLimit", "isReservationMandatory"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_template_params.py b/talon_one/models/campaign_template_params.py
index aa5ec28..7a450b9 100644
--- a/talon_one/models/campaign_template_params.py
+++ b/talon_one/models/campaign_template_params.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignTemplateParams(BaseModel):
"""
@@ -41,7 +42,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/campaign_versions.py b/talon_one/models/campaign_versions.py
index 7013a0e..28ad2a4 100644
--- a/talon_one/models/campaign_versions.py
+++ b/talon_one/models/campaign_versions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CampaignVersions(BaseModel):
"""
@@ -46,7 +47,8 @@ def revision_frontend_state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_added_deducted_points_balances_notification.py b/talon_one/models/card_added_deducted_points_balances_notification.py
index 40402ba..e7c7e81 100644
--- a/talon_one/models/card_added_deducted_points_balances_notification.py
+++ b/talon_one/models/card_added_deducted_points_balances_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.added_deducted_points_balances_action import AddedDeductedPointsBalancesAction
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardAddedDeductedPointsBalancesNotification(BaseModel):
"""
@@ -57,7 +58,8 @@ def type_of_change_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -69,8 +71,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_added_deducted_points_balances_notification_policy.py b/talon_one/models/card_added_deducted_points_balances_notification_policy.py
index 13f0a0c..e6d937e 100644
--- a/talon_one/models/card_added_deducted_points_balances_notification_policy.py
+++ b/talon_one/models/card_added_deducted_points_balances_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardAddedDeductedPointsBalancesNotificationPolicy(BaseModel):
"""
@@ -40,7 +41,8 @@ def scopes_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_added_deducted_points_notification.py b/talon_one/models/card_added_deducted_points_notification.py
index 3ef4aa7..0518f85 100644
--- a/talon_one/models/card_added_deducted_points_notification.py
+++ b/talon_one/models/card_added_deducted_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardAddedDeductedPointsNotification(BaseModel):
"""
@@ -69,7 +70,8 @@ def operation_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -81,8 +83,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_added_deducted_points_notification_policy.py b/talon_one/models/card_added_deducted_points_notification_policy.py
index d6e976c..8f43610 100644
--- a/talon_one/models/card_added_deducted_points_notification_policy.py
+++ b/talon_one/models/card_added_deducted_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardAddedDeductedPointsNotificationPolicy(BaseModel):
"""
@@ -40,7 +41,8 @@ def scopes_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_expiring_points_notification_policy.py b/talon_one/models/card_expiring_points_notification_policy.py
index 63f4877..b1672c2 100644
--- a/talon_one/models/card_expiring_points_notification_policy.py
+++ b/talon_one/models/card_expiring_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.card_expiring_points_notification_trigger import CardExpiringPointsNotificationTrigger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardExpiringPointsNotificationPolicy(BaseModel):
"""
@@ -35,7 +36,8 @@ class CardExpiringPointsNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "triggers", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_expiring_points_notification_trigger.py b/talon_one/models/card_expiring_points_notification_trigger.py
index d10318e..3e6e531 100644
--- a/talon_one/models/card_expiring_points_notification_trigger.py
+++ b/talon_one/models/card_expiring_points_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardExpiringPointsNotificationTrigger(BaseModel):
"""
@@ -39,7 +40,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_ledger_points_entry_integration_api.py b/talon_one/models/card_ledger_points_entry_integration_api.py
index cd494b0..4768011 100644
--- a/talon_one/models/card_ledger_points_entry_integration_api.py
+++ b/talon_one/models/card_ledger_points_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardLedgerPointsEntryIntegrationAPI(BaseModel):
"""
@@ -43,7 +44,8 @@ class CardLedgerPointsEntryIntegrationAPI(BaseModel):
__properties: ClassVar[List[str]] = ["id", "transactionUUID", "created", "programId", "customerProfileID", "customerSessionId", "name", "startDate", "expiryDate", "subledgerId", "amount", "validityDuration"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_ledger_transaction_log_entry.py b/talon_one/models/card_ledger_transaction_log_entry.py
index 8b3167e..ecaa0d1 100644
--- a/talon_one/models/card_ledger_transaction_log_entry.py
+++ b/talon_one/models/card_ledger_transaction_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardLedgerTransactionLogEntry(BaseModel):
"""
@@ -59,7 +60,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -71,8 +73,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/card_ledger_transaction_log_entry_integration_api.py b/talon_one/models/card_ledger_transaction_log_entry_integration_api.py
index a136c7a..4a5338f 100644
--- a/talon_one/models/card_ledger_transaction_log_entry_integration_api.py
+++ b/talon_one/models/card_ledger_transaction_log_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CardLedgerTransactionLogEntryIntegrationAPI(BaseModel):
"""
@@ -60,7 +61,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -72,8 +74,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/cart_item.py b/talon_one/models/cart_item.py
index 0addf87..2cf6fe1 100644
--- a/talon_one/models/cart_item.py
+++ b/talon_one/models/cart_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -27,6 +27,7 @@
from talon_one.models.product import Product
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CartItem(BaseModel):
"""
@@ -56,7 +57,8 @@ class CartItem(BaseModel):
__properties: ClassVar[List[str]] = ["name", "sku", "quantity", "returnedQuantity", "remainingQuantity", "price", "category", "product", "weight", "height", "width", "length", "position", "attributes", "additionalCosts", "catalogItemID", "selectedPriceType", "adjustmentReferenceId", "adjustmentEffectiveFrom", "adjustmentEffectiveUntil", "prices"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -85,8 +86,26 @@ def to_dict(self) -> Dict[str, Any]:
* `None` is only added to the output dict for nullable fields that
were set at model initialization. Other fields with value `None`
are ignored.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
+ * OpenAPI `readOnly` fields are excluded.
"""
excluded_fields: Set[str] = set([
+ "returned_quantity",
+ "remaining_quantity",
+ "position",
+ "catalog_item_id",
+ "selected_price_type",
+ "adjustment_reference_id",
+ "adjustment_effective_from",
+ "adjustment_effective_until",
+ "prices",
])
_dict = self.model_dump(
diff --git a/talon_one/models/cart_item_filter_template.py b/talon_one/models/cart_item_filter_template.py
index b2c0888..0352577 100644
--- a/talon_one/models/cart_item_filter_template.py
+++ b/talon_one/models/cart_item_filter_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CartItemFilterTemplate(BaseModel):
"""
@@ -31,7 +32,8 @@ class CartItemFilterTemplate(BaseModel):
__properties: ClassVar[List[str]] = ["name", "expression"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalog.py b/talon_one/models/catalog.py
index c56fa37..bdc38e9 100644
--- a/talon_one/models/catalog.py
+++ b/talon_one/models/catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Catalog(BaseModel):
"""
@@ -39,7 +40,8 @@ class Catalog(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "accountId", "modified", "name", "description", "subscribedApplicationsIds", "version", "createdBy"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalog_action_filter.py b/talon_one/models/catalog_action_filter.py
index 4811afe..5d21013 100644
--- a/talon_one/models/catalog_action_filter.py
+++ b/talon_one/models/catalog_action_filter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CatalogActionFilter(BaseModel):
"""
@@ -39,7 +40,8 @@ def op_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalog_item.py b/talon_one/models/catalog_item.py
index 5d7a925..bb9edfa 100644
--- a/talon_one/models/catalog_item.py
+++ b/talon_one/models/catalog_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.product import Product
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CatalogItem(BaseModel):
"""
@@ -41,7 +42,8 @@ class CatalogItem(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "sku", "price", "catalogid", "version", "attributes", "product"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalog_rule.py b/talon_one/models/catalog_rule.py
index eb32955..545982a 100644
--- a/talon_one/models/catalog_rule.py
+++ b/talon_one/models/catalog_rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.binding import Binding
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CatalogRule(BaseModel):
"""
@@ -35,7 +36,8 @@ class CatalogRule(BaseModel):
__properties: ClassVar[List[str]] = ["title", "bindings", "condition", "effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalog_sync_request.py b/talon_one/models/catalog_sync_request.py
index b78d3a7..8f7bc98 100644
--- a/talon_one/models/catalog_sync_request.py
+++ b/talon_one/models/catalog_sync_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CatalogSyncRequest(BaseModel):
"""
@@ -32,7 +33,8 @@ class CatalogSyncRequest(BaseModel):
__properties: ClassVar[List[str]] = ["actions", "version"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/catalogs_strikethrough_notification_policy.py b/talon_one/models/catalogs_strikethrough_notification_policy.py
index 3380bb8..704f84f 100644
--- a/talon_one/models/catalogs_strikethrough_notification_policy.py
+++ b/talon_one/models/catalogs_strikethrough_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CatalogsStrikethroughNotificationPolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class CatalogsStrikethroughNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "aheadOfDaysTrigger", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/change.py b/talon_one/models/change.py
index abc15c4..57711e5 100644
--- a/talon_one/models/change.py
+++ b/talon_one/models/change.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Change(BaseModel):
"""
@@ -38,7 +39,8 @@ class Change(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "userId", "applicationId", "entity", "old", "new", "managementKeyId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/change_loyalty_tier_level_effect_props.py b/talon_one/models/change_loyalty_tier_level_effect_props.py
index 5761224..fc57f70 100644
--- a/talon_one/models/change_loyalty_tier_level_effect_props.py
+++ b/talon_one/models/change_loyalty_tier_level_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ChangeLoyaltyTierLevelEffectProps(BaseModel):
"""
@@ -36,7 +37,8 @@ class ChangeLoyaltyTierLevelEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["ruleTitle", "programId", "subLedgerId", "previousTierName", "newTierName", "expiryDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/change_profile_password.py b/talon_one/models/change_profile_password.py
index 2652370..b3f35d4 100644
--- a/talon_one/models/change_profile_password.py
+++ b/talon_one/models/change_profile_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ChangeProfilePassword(BaseModel):
"""
@@ -31,7 +32,8 @@ class ChangeProfilePassword(BaseModel):
__properties: ClassVar[List[str]] = ["password", "newPassword"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/code_generator_settings.py b/talon_one/models/code_generator_settings.py
index b12b0d3..a0a538f 100644
--- a/talon_one/models/code_generator_settings.py
+++ b/talon_one/models/code_generator_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CodeGeneratorSettings(BaseModel):
"""
@@ -39,7 +40,8 @@ def coupon_pattern_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/collection.py b/talon_one/models/collection.py
index 0fe6730..951c34b 100644
--- a/talon_one/models/collection.py
+++ b/talon_one/models/collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Collection(BaseModel):
"""
@@ -50,7 +51,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/collection_item.py b/talon_one/models/collection_item.py
index d6b1235..2e5d409 100644
--- a/talon_one/models/collection_item.py
+++ b/talon_one/models/collection_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CollectionItem(BaseModel):
"""
@@ -30,7 +31,8 @@ class CollectionItem(BaseModel):
__properties: ClassVar[List[str]] = ["item"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/collection_without_payload.py b/talon_one/models/collection_without_payload.py
index aeb7b6d..5ada87a 100644
--- a/talon_one/models/collection_without_payload.py
+++ b/talon_one/models/collection_without_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CollectionWithoutPayload(BaseModel):
"""
@@ -49,7 +50,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -61,8 +63,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon.py b/talon_one/models/coupon.py
index 3dd41c9..1f250fc 100644
--- a/talon_one/models/coupon.py
+++ b/talon_one/models/coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Coupon(BaseModel):
"""
@@ -54,7 +55,8 @@ class Coupon(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "value", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "usageCounter", "discountCounter", "discountRemainder", "reservationCounter", "attributes", "referralId", "recipientIntegrationId", "importId", "reservation", "batchId", "isReservationMandatory", "implicitlyReserved"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -66,8 +68,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_constraints.py b/talon_one/models/coupon_constraints.py
index 37657ef..b221242 100644
--- a/talon_one/models/coupon_constraints.py
+++ b/talon_one/models/coupon_constraints.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponConstraints(BaseModel):
"""
@@ -36,7 +37,8 @@ class CouponConstraints(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_created_effect_props.py b/talon_one/models/coupon_created_effect_props.py
index f59b769..5b9adea 100644
--- a/talon_one/models/coupon_created_effect_props.py
+++ b/talon_one/models/coupon_created_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponCreatedEffectProps(BaseModel):
"""
@@ -31,7 +32,8 @@ class CouponCreatedEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value", "profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_creation_job.py b/talon_one/models/coupon_creation_job.py
index cbefb2c..b7b01bb 100644
--- a/talon_one/models/coupon_creation_job.py
+++ b/talon_one/models/coupon_creation_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.code_generator_settings import CodeGeneratorSettings
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponCreationJob(BaseModel):
"""
@@ -55,7 +56,8 @@ class CouponCreationJob(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "applicationId", "accountId", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "numberOfCoupons", "couponSettings", "attributes", "isReservationMandatory", "batchId", "status", "createdAmount", "failCount", "errors", "createdBy", "communicated", "chunkExecutionCount", "chunkSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_deletion_filters.py b/talon_one/models/coupon_deletion_filters.py
index d91043a..327ccbc 100644
--- a/talon_one/models/coupon_deletion_filters.py
+++ b/talon_one/models/coupon_deletion_filters.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponDeletionFilters(BaseModel):
"""
@@ -54,7 +55,8 @@ def valid_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -66,8 +68,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_deletion_job.py b/talon_one/models/coupon_deletion_job.py
index 5582b9f..26130d6 100644
--- a/talon_one/models/coupon_deletion_job.py
+++ b/talon_one/models/coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.coupon_deletion_filters import CouponDeletionFilters
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponDeletionJob(BaseModel):
"""
@@ -43,7 +44,8 @@ class CouponDeletionJob(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "accountId", "filters", "status", "deletedAmount", "failCount", "errors", "createdBy", "communicated", "campaignIDs"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_entity.py b/talon_one/models/coupon_entity.py
index 62d120c..dbf9d16 100644
--- a/talon_one/models/coupon_entity.py
+++ b/talon_one/models/coupon_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponEntity(BaseModel):
"""
@@ -32,7 +33,8 @@ class CouponEntity(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_failure_summary.py b/talon_one/models/coupon_failure_summary.py
index 60e777c..e8e7192 100644
--- a/talon_one/models/coupon_failure_summary.py
+++ b/talon_one/models/coupon_failure_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponFailureSummary(BaseModel):
"""
@@ -40,7 +41,8 @@ class CouponFailureSummary(BaseModel):
__properties: ClassVar[List[str]] = ["id", "eventID", "sessionID", "profileID", "status", "couponCode", "language", "summary", "createdAt", "updatedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_limit_configs.py b/talon_one/models/coupon_limit_configs.py
index 50d92b4..c1a761e 100644
--- a/talon_one/models/coupon_limit_configs.py
+++ b/talon_one/models/coupon_limit_configs.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponLimitConfigs(BaseModel):
"""
@@ -31,7 +32,8 @@ class CouponLimitConfigs(BaseModel):
__properties: ClassVar[List[str]] = ["limits"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_rejection_reason.py b/talon_one/models/coupon_rejection_reason.py
index bbfd345..c39bfa8 100644
--- a/talon_one/models/coupon_rejection_reason.py
+++ b/talon_one/models/coupon_rejection_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponRejectionReason(BaseModel):
"""
@@ -39,7 +40,8 @@ def reason_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_reservations.py b/talon_one/models/coupon_reservations.py
index c28313f..c39d135 100644
--- a/talon_one/models/coupon_reservations.py
+++ b/talon_one/models/coupon_reservations.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponReservations(BaseModel):
"""
@@ -31,7 +32,8 @@ class CouponReservations(BaseModel):
__properties: ClassVar[List[str]] = ["integrationIDs"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_search.py b/talon_one/models/coupon_search.py
index 9a14597..3dfd497 100644
--- a/talon_one/models/coupon_search.py
+++ b/talon_one/models/coupon_search.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponSearch(BaseModel):
"""
@@ -30,7 +31,8 @@ class CouponSearch(BaseModel):
__properties: ClassVar[List[str]] = ["attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_value.py b/talon_one/models/coupon_value.py
index 0b91460..1eef2f8 100644
--- a/talon_one/models/coupon_value.py
+++ b/talon_one/models/coupon_value.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponValue(BaseModel):
"""
@@ -31,7 +32,8 @@ class CouponValue(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupon_with_application.py b/talon_one/models/coupon_with_application.py
index 80d3670..17ba099 100644
--- a/talon_one/models/coupon_with_application.py
+++ b/talon_one/models/coupon_with_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponWithApplication(BaseModel):
"""
@@ -56,7 +57,8 @@ class CouponWithApplication(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "value", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "usageCounter", "discountCounter", "discountRemainder", "reservationCounter", "attributes", "referralId", "recipientIntegrationId", "importId", "reservation", "batchId", "isReservationMandatory", "implicitlyReserved", "applicationId", "applicationName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupons_notification_data.py b/talon_one/models/coupons_notification_data.py
index 74ff6e8..19cf6dc 100644
--- a/talon_one/models/coupons_notification_data.py
+++ b/talon_one/models/coupons_notification_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.extended_coupon import ExtendedCoupon
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponsNotificationData(BaseModel):
"""
@@ -43,7 +44,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/coupons_notification_policy.py b/talon_one/models/coupons_notification_policy.py
index 33b9e00..cfc355e 100644
--- a/talon_one/models/coupons_notification_policy.py
+++ b/talon_one/models/coupons_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CouponsNotificationPolicy(BaseModel):
"""
@@ -43,7 +44,8 @@ def scopes_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_achievement.py b/talon_one/models/create_achievement.py
index 42ea129..0ffeb54 100644
--- a/talon_one/models/create_achievement.py
+++ b/talon_one/models/create_achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.time_point import TimePoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateAchievement(BaseModel):
"""
@@ -70,7 +71,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -82,8 +84,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_achievement_v2.py b/talon_one/models/create_achievement_v2.py
index 43e588e..964c5e8 100644
--- a/talon_one/models/create_achievement_v2.py
+++ b/talon_one/models/create_achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateAchievementV2(BaseModel):
"""
@@ -71,7 +72,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -83,8 +85,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_application_api_key.py b/talon_one/models/create_application_api_key.py
index b741ce6..1815c08 100644
--- a/talon_one/models/create_application_api_key.py
+++ b/talon_one/models/create_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateApplicationAPIKey(BaseModel):
"""
@@ -55,7 +56,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_coupon_data.py b/talon_one/models/create_coupon_data.py
index 398e1a7..d682129 100644
--- a/talon_one/models/create_coupon_data.py
+++ b/talon_one/models/create_coupon_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.extended_coupon import ExtendedCoupon
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateCouponData(BaseModel):
"""
@@ -44,7 +45,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_coupons200_response.py b/talon_one/models/create_coupons200_response.py
index 5b22a0f..aef7b1a 100644
--- a/talon_one/models/create_coupons200_response.py
+++ b/talon_one/models/create_coupons200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.coupon import Coupon
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateCoupons200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class CreateCoupons200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_management_key.py b/talon_one/models/create_management_key.py
index 56a276f..beede97 100644
--- a/talon_one/models/create_management_key.py
+++ b/talon_one/models/create_management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.endpoint import Endpoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateManagementKey(BaseModel):
"""
@@ -35,7 +36,8 @@ class CreateManagementKey(BaseModel):
__properties: ClassVar[List[str]] = ["name", "expiryDate", "endpoints", "allowedApplicationIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_referrals_for_multiple_advocates201_response.py b/talon_one/models/create_referrals_for_multiple_advocates201_response.py
index b336720..ab7d5c1 100644
--- a/talon_one/models/create_referrals_for_multiple_advocates201_response.py
+++ b/talon_one/models/create_referrals_for_multiple_advocates201_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.referral import Referral
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateReferralsForMultipleAdvocates201Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class CreateReferralsForMultipleAdvocates201Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_template_campaign.py b/talon_one/models/create_template_campaign.py
index 4abe67b..4cf4b80 100644
--- a/talon_one/models/create_template_campaign.py
+++ b/talon_one/models/create_template_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateTemplateCampaign(BaseModel):
"""
@@ -42,7 +43,8 @@ class CreateTemplateCampaign(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "templateId", "campaignAttributesOverrides", "templateParamValues", "limitOverrides", "campaignGroups", "tags", "evaluationGroupId", "linkedStoreIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/create_template_campaign_response.py b/talon_one/models/create_template_campaign_response.py
index fe78f18..aa1fe14 100644
--- a/talon_one/models/create_template_campaign_response.py
+++ b/talon_one/models/create_template_campaign_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CreateTemplateCampaignResponse(BaseModel):
"""
@@ -35,7 +36,8 @@ class CreateTemplateCampaignResponse(BaseModel):
__properties: ClassVar[List[str]] = ["campaign", "ruleset", "collections"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/custom_effect.py b/talon_one/models/custom_effect.py
index cdd18de..815564b 100644
--- a/talon_one/models/custom_effect.py
+++ b/talon_one/models/custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomEffect(BaseModel):
"""
@@ -60,7 +61,8 @@ def title_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -72,8 +74,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/custom_effect_props.py b/talon_one/models/custom_effect_props.py
index 0a60afe..1fbd69a 100644
--- a/talon_one/models/custom_effect_props.py
+++ b/talon_one/models/custom_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomEffectProps(BaseModel):
"""
@@ -36,7 +37,8 @@ class CustomEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["effectId", "name", "cartItemPosition", "cartItemSubPosition", "bundleIndex", "bundleName", "payload"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_activity_report.py b/talon_one/models/customer_activity_report.py
index c6c5845..c7d6638 100644
--- a/talon_one/models/customer_activity_report.py
+++ b/talon_one/models/customer_activity_report.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerActivityReport(BaseModel):
"""
@@ -44,7 +45,8 @@ class CustomerActivityReport(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId", "created", "name", "customerId", "lastActivity", "couponRedemptions", "couponUseAttempts", "couponFailedAttempts", "accruedDiscounts", "accruedRevenue", "totalOrders", "totalOrdersNoCoupon", "campaignName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_analytics.py b/talon_one/models/customer_analytics.py
index bfe1ad7..30151e3 100644
--- a/talon_one/models/customer_analytics.py
+++ b/talon_one/models/customer_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerAnalytics(BaseModel):
"""
@@ -36,7 +37,8 @@ class CustomerAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["acceptedCoupons", "createdCoupons", "freeItems", "totalOrders", "totalDiscountedOrders", "totalRevenue", "totalDiscounts"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_inventory.py b/talon_one/models/customer_inventory.py
index 143acef..0335c11 100644
--- a/talon_one/models/customer_inventory.py
+++ b/talon_one/models/customer_inventory.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -27,6 +27,7 @@
from talon_one.models.loyalty import Loyalty
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerInventory(BaseModel):
"""
@@ -41,7 +42,8 @@ class CustomerInventory(BaseModel):
__properties: ClassVar[List[str]] = ["profile", "loyalty", "referrals", "coupons", "giveaways", "achievements"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile.py b/talon_one/models/customer_profile.py
index 82f24f7..e612ede 100644
--- a/talon_one/models/customer_profile.py
+++ b/talon_one/models/customer_profile.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.loyalty_membership import LoyaltyMembership
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfile(BaseModel):
"""
@@ -39,12 +40,13 @@ class CustomerProfile(BaseModel):
total_sales: Union[StrictFloat, StrictInt] = Field(description="The total amount of money spent by the customer **before** discounts are applied. The total sales amount excludes the following: - Cancelled or reopened sessions. - Returned items. ", alias="totalSales")
loyalty_memberships: Optional[List[LoyaltyMembership]] = Field(default=None, description="**DEPRECATED. Always returns `null`.** A list of loyalty programs joined by the customer. ", alias="loyaltyMemberships")
audience_memberships: Optional[List[AudienceMembership]] = Field(default=None, description="The audiences the customer belongs to.", alias="audienceMemberships")
- last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
+ last_activity: datetime = Field(description="Timestamp of the most recent event received from this customer. This field is updated on calls that trigger the Rule Engine and that are not [dry requests](https://docs.talon.one/docs/dev/integration-api/dry-requests/#overlay). For example, [reserving a coupon](https://docs.talon.one/integration-api#tag/Coupons/operation/createCouponReservation) for a customer doesn't impact this field. ", alias="lastActivity")
sandbox: Optional[StrictBool] = Field(default=None, description="An indicator of whether the customer is part of a sandbox or live Application. See the [docs](https://docs.talon.one/docs/product/applications/overview#application-environments). ")
__properties: ClassVar[List[str]] = ["id", "created", "integrationId", "attributes", "accountId", "closedSessions", "totalSales", "loyaltyMemberships", "audienceMemberships", "lastActivity", "sandbox"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_audience_request.py b/talon_one/models/customer_profile_audience_request.py
index 9b36b19..744d1a9 100644
--- a/talon_one/models/customer_profile_audience_request.py
+++ b/talon_one/models/customer_profile_audience_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile_audience_request_item import CustomerProfileAudienceRequestItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileAudienceRequest(BaseModel):
"""
@@ -31,7 +32,8 @@ class CustomerProfileAudienceRequest(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_audience_request_item.py b/talon_one/models/customer_profile_audience_request_item.py
index 10f3959..ab87f2e 100644
--- a/talon_one/models/customer_profile_audience_request_item.py
+++ b/talon_one/models/customer_profile_audience_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileAudienceRequestItem(BaseModel):
"""
@@ -29,7 +30,7 @@ class CustomerProfileAudienceRequestItem(BaseModel):
""" # noqa: E501
action: StrictStr = Field(description="Defines the action to perform: - `add`: Adds the customer profile to the audience. **Note**: If the customer profile does not exist, it will be created. The profile will not be visible in any Application until a session or profile update is received for that profile. - `delete`: Removes the customer profile from the audience. ")
profile_integration_id: Annotated[str, Field(strict=True, max_length=1000)] = Field(description="The ID of this customer profile in the third-party integration.", alias="profileIntegrationId")
- audience_id: StrictInt = Field(description="The ID of the audience. You get it via the `id` property when [creating an audience](#operation/createAudienceV2).", alias="audienceId")
+ audience_id: StrictInt = Field(description="The ID of the audience. You get it via the `id` property when [creating an audience](#tag/Audiences/operation/createAudienceV2).", alias="audienceId")
__properties: ClassVar[List[str]] = ["action", "profileIntegrationId", "audienceId"]
@field_validator('action')
@@ -40,7 +41,8 @@ def action_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_entity.py b/talon_one/models/customer_profile_entity.py
index bf9e918..a21bf73 100644
--- a/talon_one/models/customer_profile_entity.py
+++ b/talon_one/models/customer_profile_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileEntity(BaseModel):
"""
@@ -32,7 +33,8 @@ class CustomerProfileEntity(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_integration_request_v2.py b/talon_one/models/customer_profile_integration_request_v2.py
index 7bd2b29..2343727 100644
--- a/talon_one/models/customer_profile_integration_request_v2.py
+++ b/talon_one/models/customer_profile_integration_request_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.profile_audiences_changes import ProfileAudiencesChanges
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileIntegrationRequestV2(BaseModel):
"""
@@ -45,7 +46,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_integration_response_v2.py b/talon_one/models/customer_profile_integration_response_v2.py
index 209cfe2..f646ac4 100644
--- a/talon_one/models/customer_profile_integration_response_v2.py
+++ b/talon_one/models/customer_profile_integration_response_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -30,6 +30,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileIntegrationResponseV2(BaseModel):
"""
@@ -47,7 +48,8 @@ class CustomerProfileIntegrationResponseV2(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile", "event", "loyalty", "triggeredCampaigns", "ruleFailureReasons", "awardedGiveaways", "effects", "createdCoupons", "createdReferrals"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_search_query.py b/talon_one/models/customer_profile_search_query.py
index 6b95e91..1c8be9d 100644
--- a/talon_one/models/customer_profile_search_query.py
+++ b/talon_one/models/customer_profile_search_query.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileSearchQuery(BaseModel):
"""
@@ -32,7 +33,8 @@ class CustomerProfileSearchQuery(BaseModel):
__properties: ClassVar[List[str]] = ["attributes", "integrationIDs", "profileIDs"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_profile_update_v2_response.py b/talon_one/models/customer_profile_update_v2_response.py
index 31e608e..315ac0c 100644
--- a/talon_one/models/customer_profile_update_v2_response.py
+++ b/talon_one/models/customer_profile_update_v2_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile import CustomerProfile
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerProfileUpdateV2Response(BaseModel):
"""
@@ -31,7 +32,8 @@ class CustomerProfileUpdateV2Response(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_session.py b/talon_one/models/customer_session.py
index 5104fa2..292b9eb 100644
--- a/talon_one/models/customer_session.py
+++ b/talon_one/models/customer_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.cart_item import CartItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerSession(BaseModel):
"""
@@ -57,7 +58,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -69,8 +71,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/customer_session_v2.py b/talon_one/models/customer_session_v2.py
index a3a49ee..a89cd45 100644
--- a/talon_one/models/customer_session_v2.py
+++ b/talon_one/models/customer_session_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.experiment_variant_allocation import ExperimentVariantAllocation
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class CustomerSessionV2(BaseModel):
"""
@@ -66,7 +67,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -78,8 +80,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/deactivate_user_request.py b/talon_one/models/deactivate_user_request.py
index 7276d3a..2c4706b 100644
--- a/talon_one/models/deactivate_user_request.py
+++ b/talon_one/models/deactivate_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeactivateUserRequest(BaseModel):
"""
@@ -30,7 +31,8 @@ class DeactivateUserRequest(BaseModel):
__properties: ClassVar[List[str]] = ["email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/deduct_loyalty_points.py b/talon_one/models/deduct_loyalty_points.py
index fb5f758..1e25ab6 100644
--- a/talon_one/models/deduct_loyalty_points.py
+++ b/talon_one/models/deduct_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeductLoyaltyPoints(BaseModel):
"""
@@ -34,7 +35,8 @@ class DeductLoyaltyPoints(BaseModel):
__properties: ClassVar[List[str]] = ["points", "name", "subledgerId", "applicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/deduct_loyalty_points_effect_props.py b/talon_one/models/deduct_loyalty_points_effect_props.py
index 78f0656..6e7846c 100644
--- a/talon_one/models/deduct_loyalty_points_effect_props.py
+++ b/talon_one/models/deduct_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeductLoyaltyPointsEffectProps(BaseModel):
"""
@@ -47,7 +48,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/delete_coupons_data.py b/talon_one/models/delete_coupons_data.py
index f41f452..a17e96a 100644
--- a/talon_one/models/delete_coupons_data.py
+++ b/talon_one/models/delete_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeleteCouponsData(BaseModel):
"""
@@ -44,7 +45,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/delete_loyalty_transactions_request.py b/talon_one/models/delete_loyalty_transactions_request.py
index a06726c..0d8826e 100644
--- a/talon_one/models/delete_loyalty_transactions_request.py
+++ b/talon_one/models/delete_loyalty_transactions_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeleteLoyaltyTransactionsRequest(BaseModel):
"""
@@ -38,7 +39,8 @@ def scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/delete_user_request.py b/talon_one/models/delete_user_request.py
index adf3747..a5dcb76 100644
--- a/talon_one/models/delete_user_request.py
+++ b/talon_one/models/delete_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class DeleteUserRequest(BaseModel):
"""
@@ -30,7 +31,8 @@ class DeleteUserRequest(BaseModel):
__properties: ClassVar[List[str]] = ["email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/effect.py b/talon_one/models/effect.py
index 24203ba..8ff1404 100644
--- a/talon_one/models/effect.py
+++ b/talon_one/models/effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Effect(BaseModel):
"""
@@ -47,7 +48,8 @@ class Effect(BaseModel):
__properties: ClassVar[List[str]] = ["experimentId", "campaignId", "rulesetId", "ruleIndex", "ruleName", "effectType", "triggeredByCoupon", "triggeredForCatalogItem", "conditionIndex", "evaluationGroupID", "evaluationGroupMode", "campaignRevisionId", "campaignRevisionVersionId", "selectedPriceType", "selectedPrice", "adjustmentReferenceId", "props"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/effect_entity.py b/talon_one/models/effect_entity.py
index a85a035..65bea9d 100644
--- a/talon_one/models/effect_entity.py
+++ b/talon_one/models/effect_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EffectEntity(BaseModel):
"""
@@ -46,7 +47,8 @@ class EffectEntity(BaseModel):
__properties: ClassVar[List[str]] = ["experimentId", "campaignId", "rulesetId", "ruleIndex", "ruleName", "effectType", "triggeredByCoupon", "triggeredForCatalogItem", "conditionIndex", "evaluationGroupID", "evaluationGroupMode", "campaignRevisionId", "campaignRevisionVersionId", "selectedPriceType", "selectedPrice", "adjustmentReferenceId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/email_entity.py b/talon_one/models/email_entity.py
index 5207c53..db0de2d 100644
--- a/talon_one/models/email_entity.py
+++ b/talon_one/models/email_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EmailEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class EmailEntity(BaseModel):
__properties: ClassVar[List[str]] = ["email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/embedded_analytics_configuration.py b/talon_one/models/embedded_analytics_configuration.py
new file mode 100644
index 0000000..48bf6f6
--- /dev/null
+++ b/talon_one/models/embedded_analytics_configuration.py
@@ -0,0 +1,92 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict
+from typing import Any, ClassVar, Dict, List
+from talon_one.models.embedded_analytics_configuration_dashboards import EmbeddedAnalyticsConfigurationDashboards
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class EmbeddedAnalyticsConfiguration(BaseModel):
+ """
+ EmbeddedAnalyticsConfiguration
+ """ # noqa: E501
+ dashboards: EmbeddedAnalyticsConfigurationDashboards
+ __properties: ClassVar[List[str]] = ["dashboards"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of EmbeddedAnalyticsConfiguration from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ # override the default output from pydantic by calling `to_dict()` of dashboards
+ if self.dashboards:
+ _dict['dashboards'] = self.dashboards.to_dict()
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of EmbeddedAnalyticsConfiguration from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "dashboards": EmbeddedAnalyticsConfigurationDashboards.from_dict(obj["dashboards"]) if obj.get("dashboards") is not None else None
+ })
+ return _obj
+
+
diff --git a/talon_one/models/embedded_analytics_configuration_dashboards.py b/talon_one/models/embedded_analytics_configuration_dashboards.py
new file mode 100644
index 0000000..08b6a12
--- /dev/null
+++ b/talon_one/models/embedded_analytics_configuration_dashboards.py
@@ -0,0 +1,92 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field
+from typing import Any, ClassVar, Dict, List, Optional
+from talon_one.models.embedded_dashboard_configuration import EmbeddedDashboardConfiguration
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class EmbeddedAnalyticsConfigurationDashboards(BaseModel):
+ """
+ EmbeddedAnalyticsConfigurationDashboards
+ """ # noqa: E501
+ campaign_insights: Optional[EmbeddedDashboardConfiguration] = Field(default=None, description="The configuration of the embedded Insights dashboard for campaigns.", alias="campaignInsights")
+ __properties: ClassVar[List[str]] = ["campaignInsights"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of EmbeddedAnalyticsConfigurationDashboards from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ # override the default output from pydantic by calling `to_dict()` of campaign_insights
+ if self.campaign_insights:
+ _dict['campaignInsights'] = self.campaign_insights.to_dict()
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of EmbeddedAnalyticsConfigurationDashboards from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "campaignInsights": EmbeddedDashboardConfiguration.from_dict(obj["campaignInsights"]) if obj.get("campaignInsights") is not None else None
+ })
+ return _obj
+
+
diff --git a/talon_one/models/embedded_dashboard_configuration.py b/talon_one/models/embedded_dashboard_configuration.py
new file mode 100644
index 0000000..b0db3f0
--- /dev/null
+++ b/talon_one/models/embedded_dashboard_configuration.py
@@ -0,0 +1,90 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictStr
+from typing import Any, ClassVar, Dict, List
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class EmbeddedDashboardConfiguration(BaseModel):
+ """
+ EmbeddedDashboardConfiguration
+ """ # noqa: E501
+ workspace_id: StrictStr = Field(description="The ID of the workspace that contains dashboards.", alias="workspaceId")
+ dashboard_id: StrictStr = Field(description="The ID of the dashboard that contains metrics.", alias="dashboardId")
+ __properties: ClassVar[List[str]] = ["workspaceId", "dashboardId"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of EmbeddedDashboardConfiguration from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of EmbeddedDashboardConfiguration from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "workspaceId": obj.get("workspaceId"),
+ "dashboardId": obj.get("dashboardId")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/endpoint.py b/talon_one/models/endpoint.py
index 2625063..02ef643 100644
--- a/talon_one/models/endpoint.py
+++ b/talon_one/models/endpoint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Endpoint(BaseModel):
"""
@@ -30,7 +31,8 @@ class Endpoint(BaseModel):
__properties: ClassVar[List[str]] = ["path"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/entity.py b/talon_one/models/entity.py
index 232d26f..34e0b55 100644
--- a/talon_one/models/entity.py
+++ b/talon_one/models/entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Entity(BaseModel):
"""
@@ -32,7 +33,8 @@ class Entity(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/entity_with_talang_visible_id.py b/talon_one/models/entity_with_talang_visible_id.py
index b8b7141..17a4827 100644
--- a/talon_one/models/entity_with_talang_visible_id.py
+++ b/talon_one/models/entity_with_talang_visible_id.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EntityWithTalangVisibleID(BaseModel):
"""
@@ -32,7 +33,8 @@ class EntityWithTalangVisibleID(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/environment.py b/talon_one/models/environment.py
index 9cedc81..c8023f4 100644
--- a/talon_one/models/environment.py
+++ b/talon_one/models/environment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -34,6 +34,7 @@
from talon_one.models.template_def import TemplateDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Environment(BaseModel):
"""
@@ -58,7 +59,8 @@ class Environment(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "slots", "functions", "templates", "variables", "giveawaysPools", "loyaltyPrograms", "achievements", "attributes", "additionalCosts", "audiences", "collections", "applicationCartItemFilters", "priceTypes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -70,8 +72,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/error_effect_props.py b/talon_one/models/error_effect_props.py
index 151a327..34761c5 100644
--- a/talon_one/models/error_effect_props.py
+++ b/talon_one/models/error_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ErrorEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class ErrorEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["message"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/error_response.py b/talon_one/models/error_response.py
index 7423919..6644cad 100644
--- a/talon_one/models/error_response.py
+++ b/talon_one/models/error_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.api_error import APIError
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ErrorResponse(BaseModel):
"""
@@ -32,7 +33,8 @@ class ErrorResponse(BaseModel):
__properties: ClassVar[List[str]] = ["message", "errors"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/error_response_with_status.py b/talon_one/models/error_response_with_status.py
index 59ae524..483beff 100644
--- a/talon_one/models/error_response_with_status.py
+++ b/talon_one/models/error_response_with_status.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.api_error import APIError
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ErrorResponseWithStatus(BaseModel):
"""
@@ -33,7 +34,8 @@ class ErrorResponseWithStatus(BaseModel):
__properties: ClassVar[List[str]] = ["message", "errors", "StatusCode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/error_source.py b/talon_one/models/error_source.py
index 69ee8f7..5b24850 100644
--- a/talon_one/models/error_source.py
+++ b/talon_one/models/error_source.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ErrorSource(BaseModel):
"""
@@ -33,7 +34,8 @@ class ErrorSource(BaseModel):
__properties: ClassVar[List[str]] = ["pointer", "parameter", "line", "resource"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/evaluable_campaign_ids.py b/talon_one/models/evaluable_campaign_ids.py
index 22c0b3d..debe752 100644
--- a/talon_one/models/evaluable_campaign_ids.py
+++ b/talon_one/models/evaluable_campaign_ids.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EvaluableCampaignIds(BaseModel):
"""
@@ -30,7 +31,8 @@ class EvaluableCampaignIds(BaseModel):
__properties: ClassVar[List[str]] = ["evaluableCampaignIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/event.py b/talon_one/models/event.py
index 8e8e2a2..244bb75 100644
--- a/talon_one/models/event.py
+++ b/talon_one/models/event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.meta import Meta
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Event(BaseModel):
"""
@@ -44,7 +45,8 @@ class Event(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "profileId", "storeIntegrationId", "type", "attributes", "sessionId", "effects", "ledgerEntries", "meta"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/event_attributes_entity.py b/talon_one/models/event_attributes_entity.py
index 1752e78..2bc1a17 100644
--- a/talon_one/models/event_attributes_entity.py
+++ b/talon_one/models/event_attributes_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EventAttributesEntity(BaseModel):
"""
@@ -32,7 +33,8 @@ class EventAttributesEntity(BaseModel):
__properties: ClassVar[List[str]] = ["type", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/event_type.py b/talon_one/models/event_type.py
index 87447fe..13dc763 100644
--- a/talon_one/models/event_type.py
+++ b/talon_one/models/event_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EventType(BaseModel):
"""
@@ -36,7 +37,8 @@ class EventType(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "title", "name", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/event_v2.py b/talon_one/models/event_v2.py
index 372a79e..ce054ac 100644
--- a/talon_one/models/event_v2.py
+++ b/talon_one/models/event_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EventV2(BaseModel):
"""
@@ -35,7 +36,8 @@ class EventV2(BaseModel):
__properties: ClassVar[List[str]] = ["profileId", "storeIntegrationId", "evaluableCampaignIds", "type", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/event_v3.py b/talon_one/models/event_v3.py
index 78b5b70..dae0cbb 100644
--- a/talon_one/models/event_v3.py
+++ b/talon_one/models/event_v3.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class EventV3(BaseModel):
"""
@@ -38,7 +39,8 @@ class EventV3(BaseModel):
__properties: ClassVar[List[str]] = ["profileId", "storeIntegrationId", "evaluableCampaignIds", "integrationId", "type", "attributes", "connectedSessionID", "previousEventID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment.py b/talon_one/models/experiment.py
index 62ad364..e71ea4a 100644
--- a/talon_one/models/experiment.py
+++ b/talon_one/models/experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.experiment_variant import ExperimentVariant
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Experiment(BaseModel):
"""
@@ -48,7 +49,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -60,8 +62,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_campaign_copy.py b/talon_one/models/experiment_campaign_copy.py
index 3402c98..9dbcfdc 100644
--- a/talon_one/models/experiment_campaign_copy.py
+++ b/talon_one/models/experiment_campaign_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentCampaignCopy(BaseModel):
"""
@@ -37,7 +38,8 @@ class ExperimentCampaignCopy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "tags", "evaluationGroupId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_copy.py b/talon_one/models/experiment_copy.py
index e405bb2..86109cb 100644
--- a/talon_one/models/experiment_copy.py
+++ b/talon_one/models/experiment_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.experiment_copy_experiment import ExperimentCopyExperiment
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentCopy(BaseModel):
"""
@@ -32,7 +33,8 @@ class ExperimentCopy(BaseModel):
__properties: ClassVar[List[str]] = ["targetApplicationId", "experiment"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_copy_experiment.py b/talon_one/models/experiment_copy_experiment.py
index a2949fd..ee6679a 100644
--- a/talon_one/models/experiment_copy_experiment.py
+++ b/talon_one/models/experiment_copy_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.experiment_campaign_copy import ExperimentCampaignCopy
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentCopyExperiment(BaseModel):
"""
@@ -32,7 +33,8 @@ class ExperimentCopyExperiment(BaseModel):
__properties: ClassVar[List[str]] = ["isVariantAssignmentExternal", "campaign"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_list_results.py b/talon_one/models/experiment_list_results.py
new file mode 100644
index 0000000..0c9f992
--- /dev/null
+++ b/talon_one/models/experiment_list_results.py
@@ -0,0 +1,96 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict
+from typing import Any, ClassVar, Dict, List, Optional
+from talon_one.models.experiment_result import ExperimentResult
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class ExperimentListResults(BaseModel):
+ """
+ ExperimentListResults
+ """ # noqa: E501
+ results: Optional[List[ExperimentResult]] = None
+ __properties: ClassVar[List[str]] = ["results"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of ExperimentListResults from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ # override the default output from pydantic by calling `to_dict()` of each item in results (list)
+ _items = []
+ if self.results:
+ for _item_results in self.results:
+ if _item_results:
+ _items.append(_item_results.to_dict())
+ _dict['results'] = _items
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of ExperimentListResults from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "results": [ExperimentResult.from_dict(_item) for _item in obj["results"]] if obj.get("results") is not None else None
+ })
+ return _obj
+
+
diff --git a/talon_one/models/experiment_list_results_request.py b/talon_one/models/experiment_list_results_request.py
new file mode 100644
index 0000000..3a67a3d
--- /dev/null
+++ b/talon_one/models/experiment_list_results_request.py
@@ -0,0 +1,88 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictInt
+from typing import Any, ClassVar, Dict, List
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class ExperimentListResultsRequest(BaseModel):
+ """
+ ExperimentListResultsRequest
+ """ # noqa: E501
+ experiment_ids: List[StrictInt] = Field(alias="experimentIds")
+ __properties: ClassVar[List[str]] = ["experimentIds"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of ExperimentListResultsRequest from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of ExperimentListResultsRequest from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "experimentIds": obj.get("experimentIds")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/experiment_result.py b/talon_one/models/experiment_result.py
new file mode 100644
index 0000000..bfff316
--- /dev/null
+++ b/talon_one/models/experiment_result.py
@@ -0,0 +1,104 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictInt
+from typing import Any, ClassVar, Dict, List
+from talon_one.models.experiment_variant_result import ExperimentVariantResult
+from talon_one.models.experiment_variant_result_confidence import ExperimentVariantResultConfidence
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class ExperimentResult(BaseModel):
+ """
+ ExperimentResult
+ """ # noqa: E501
+ variants: List[ExperimentVariantResult]
+ confidence: ExperimentVariantResultConfidence
+ experiment_id: StrictInt = Field(alias="experimentId")
+ __properties: ClassVar[List[str]] = ["variants", "confidence", "experimentId"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of ExperimentResult from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ # override the default output from pydantic by calling `to_dict()` of each item in variants (list)
+ _items = []
+ if self.variants:
+ for _item_variants in self.variants:
+ if _item_variants:
+ _items.append(_item_variants.to_dict())
+ _dict['variants'] = _items
+ # override the default output from pydantic by calling `to_dict()` of confidence
+ if self.confidence:
+ _dict['confidence'] = self.confidence.to_dict()
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of ExperimentResult from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "variants": [ExperimentVariantResult.from_dict(_item) for _item in obj["variants"]] if obj.get("variants") is not None else None,
+ "confidence": ExperimentVariantResultConfidence.from_dict(obj["confidence"]) if obj.get("confidence") is not None else None,
+ "experimentId": obj.get("experimentId")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/experiment_results.py b/talon_one/models/experiment_results.py
index 34f8d36..3e3b841 100644
--- a/talon_one/models/experiment_results.py
+++ b/talon_one/models/experiment_results.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -18,22 +18,24 @@
import json
from pydantic import BaseModel, ConfigDict
-from typing import Any, ClassVar, Dict, List, Optional
+from typing import Any, ClassVar, Dict, List
from talon_one.models.experiment_variant_result import ExperimentVariantResult
from talon_one.models.experiment_variant_result_confidence import ExperimentVariantResultConfidence
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentResults(BaseModel):
"""
ExperimentResults
""" # noqa: E501
- variants: Optional[List[ExperimentVariantResult]] = None
+ variants: List[ExperimentVariantResult]
confidence: ExperimentVariantResultConfidence
__properties: ClassVar[List[str]] = ["variants", "confidence"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_variant.py b/talon_one/models/experiment_variant.py
index 3c25f88..3382139 100644
--- a/talon_one/models/experiment_variant.py
+++ b/talon_one/models/experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentVariant(BaseModel):
"""
@@ -38,7 +39,8 @@ class ExperimentVariant(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "name", "experimentId", "ruleset", "weight", "isPrimary"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_variant_allocation.py b/talon_one/models/experiment_variant_allocation.py
index cfc7924..037bd43 100644
--- a/talon_one/models/experiment_variant_allocation.py
+++ b/talon_one/models/experiment_variant_allocation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentVariantAllocation(BaseModel):
"""
@@ -31,7 +32,8 @@ class ExperimentVariantAllocation(BaseModel):
__properties: ClassVar[List[str]] = ["experimentID", "variantID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/experiment_variant_result.py b/talon_one/models/experiment_variant_result.py
index 037ed88..df099bd 100644
--- a/talon_one/models/experiment_variant_result.py
+++ b/talon_one/models/experiment_variant_result.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -17,10 +17,11 @@
import re # noqa: F401
import json
-from pydantic import BaseModel, ConfigDict, Field, StrictFloat, StrictInt, StrictStr
+from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictFloat, StrictInt, StrictStr
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentVariantResult(BaseModel):
"""
@@ -29,6 +30,7 @@ class ExperimentVariantResult(BaseModel):
variant_id: Optional[StrictInt] = Field(default=None, description="The ID of the variant.", alias="variantId")
variant_name: Optional[StrictStr] = Field(default=None, description="The name of the variant.", alias="variantName")
variant_weight: Optional[StrictInt] = Field(default=None, description="The weight of the variant.", alias="variantWeight")
+ is_winner: Optional[StrictBool] = Field(default=None, description="Calculated flag if the variant is the winner.", alias="isWinner")
total_revenue: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The total, pre-discount value of all items purchased in a customer session.", alias="totalRevenue")
sessions_count: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The number of all closed sessions.", alias="sessionsCount")
avg_items_per_session: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The number of items from sessions divided by the number of sessions.", alias="avgItemsPerSession")
@@ -36,10 +38,11 @@ class ExperimentVariantResult(BaseModel):
avg_discounted_session_value: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The average customer session value, calculated by dividing the revenue value by the number of sessions.", alias="avgDiscountedSessionValue")
total_discounts: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The total value of discounts given for cart items in sessions.", alias="totalDiscounts")
coupons_count: Optional[Union[StrictFloat, StrictInt]] = Field(default=None, description="The number of times a coupon was successfully redeemed in sessions.", alias="couponsCount")
- __properties: ClassVar[List[str]] = ["variantId", "variantName", "variantWeight", "totalRevenue", "sessionsCount", "avgItemsPerSession", "avgSessionValue", "avgDiscountedSessionValue", "totalDiscounts", "couponsCount"]
+ __properties: ClassVar[List[str]] = ["variantId", "variantName", "variantWeight", "isWinner", "totalRevenue", "sessionsCount", "avgItemsPerSession", "avgSessionValue", "avgDiscountedSessionValue", "totalDiscounts", "couponsCount"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -92,6 +94,7 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"variantId": obj.get("variantId"),
"variantName": obj.get("variantName"),
"variantWeight": obj.get("variantWeight"),
+ "isWinner": obj.get("isWinner"),
"totalRevenue": obj.get("totalRevenue"),
"sessionsCount": obj.get("sessionsCount"),
"avgItemsPerSession": obj.get("avgItemsPerSession"),
diff --git a/talon_one/models/experiment_variant_result_confidence.py b/talon_one/models/experiment_variant_result_confidence.py
index ba035d8..7761b22 100644
--- a/talon_one/models/experiment_variant_result_confidence.py
+++ b/talon_one/models/experiment_variant_result_confidence.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExperimentVariantResultConfidence(BaseModel):
"""
@@ -32,7 +33,8 @@ class ExperimentVariantResultConfidence(BaseModel):
__properties: ClassVar[List[str]] = ["avgSessionValue", "avgDiscountedSessionValue", "avgItemsPerSession"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_card_points_data.py b/talon_one/models/expiring_card_points_data.py
index 6be1c8d..bbef92b 100644
--- a/talon_one/models/expiring_card_points_data.py
+++ b/talon_one/models/expiring_card_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCardPointsData(BaseModel):
"""
@@ -38,7 +39,8 @@ class ExpiringCardPointsData(BaseModel):
__properties: ClassVar[List[str]] = ["ExpiryDate", "LoyaltyProgramID", "AmountOfExpiringPoints", "SubledgerID", "CardIdentifier", "UsersPerCardLimit", "Profiles"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_card_points_notification.py b/talon_one/models/expiring_card_points_notification.py
index 617da55..ba23887 100644
--- a/talon_one/models/expiring_card_points_notification.py
+++ b/talon_one/models/expiring_card_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.expiring_card_points_data import ExpiringCardPointsData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCardPointsNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_coupons_data.py b/talon_one/models/expiring_coupons_data.py
index 7a83337..45abba1 100644
--- a/talon_one/models/expiring_coupons_data.py
+++ b/talon_one/models/expiring_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCouponsData(BaseModel):
"""
@@ -41,7 +42,8 @@ class ExpiringCouponsData(BaseModel):
__properties: ClassVar[List[str]] = ["CouponValue", "CreatedDate", "ValidFrom", "ValidUntil", "CampaignId", "CustomerProfileId", "UsageLimit", "UsageCounter", "BatchId", "Attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_coupons_notification.py b/talon_one/models/expiring_coupons_notification.py
index 88563ce..f0d7778 100644
--- a/talon_one/models/expiring_coupons_notification.py
+++ b/talon_one/models/expiring_coupons_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.expiring_coupons_data import ExpiringCouponsData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCouponsNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_coupons_notification_policy.py b/talon_one/models/expiring_coupons_notification_policy.py
index d418b51..6764c87 100644
--- a/talon_one/models/expiring_coupons_notification_policy.py
+++ b/talon_one/models/expiring_coupons_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.expiring_coupons_notification_trigger import ExpiringCouponsNotificationTrigger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCouponsNotificationPolicy(BaseModel):
"""
@@ -35,7 +36,8 @@ class ExpiringCouponsNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "triggers", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_coupons_notification_trigger.py b/talon_one/models/expiring_coupons_notification_trigger.py
index c705e9f..53cf5a2 100644
--- a/talon_one/models/expiring_coupons_notification_trigger.py
+++ b/talon_one/models/expiring_coupons_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringCouponsNotificationTrigger(BaseModel):
"""
@@ -39,7 +40,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_points_data.py b/talon_one/models/expiring_points_data.py
index 40f6b10..001a62e 100644
--- a/talon_one/models/expiring_points_data.py
+++ b/talon_one/models/expiring_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringPointsData(BaseModel):
"""
@@ -36,7 +37,8 @@ class ExpiringPointsData(BaseModel):
__properties: ClassVar[List[str]] = ["ExpiryDate", "LoyaltyProgramID", "CustomerProfileID", "AmountOfExpiringPoints", "SubledgerID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_points_notification.py b/talon_one/models/expiring_points_notification.py
index 1160749..21db5cf 100644
--- a/talon_one/models/expiring_points_notification.py
+++ b/talon_one/models/expiring_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.expiring_points_data import ExpiringPointsData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringPointsNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_points_notification_policy.py b/talon_one/models/expiring_points_notification_policy.py
index f368c3b..4cdc6eb 100644
--- a/talon_one/models/expiring_points_notification_policy.py
+++ b/talon_one/models/expiring_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.expiring_points_notification_trigger import ExpiringPointsNotificationTrigger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringPointsNotificationPolicy(BaseModel):
"""
@@ -35,7 +36,8 @@ class ExpiringPointsNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "triggers", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/expiring_points_notification_trigger.py b/talon_one/models/expiring_points_notification_trigger.py
index cc0eaeb..ff3a347 100644
--- a/talon_one/models/expiring_points_notification_trigger.py
+++ b/talon_one/models/expiring_points_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExpiringPointsNotificationTrigger(BaseModel):
"""
@@ -39,7 +40,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/export.py b/talon_one/models/export.py
index 4ca5f7c..98852f0 100644
--- a/talon_one/models/export.py
+++ b/talon_one/models/export.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Export(BaseModel):
"""
@@ -43,7 +44,8 @@ def entity_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/extend_loyalty_points_expiry_date_effect_props.py b/talon_one/models/extend_loyalty_points_expiry_date_effect_props.py
index 4e1492d..36fb619 100644
--- a/talon_one/models/extend_loyalty_points_expiry_date_effect_props.py
+++ b/talon_one/models/extend_loyalty_points_expiry_date_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_ledger_entry_expiry_date_change import LoyaltyLedgerEntryExpiryDateChange
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExtendLoyaltyPointsExpiryDateEffectProps(BaseModel):
"""
@@ -34,7 +35,8 @@ class ExtendLoyaltyPointsExpiryDateEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["programId", "subLedgerId", "extensionDuration", "affectedTransactions"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/extended_coupon.py b/talon_one/models/extended_coupon.py
index 02cf7d0..2c983ce 100644
--- a/talon_one/models/extended_coupon.py
+++ b/talon_one/models/extended_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ExtendedCoupon(BaseModel):
"""
@@ -55,7 +56,8 @@ class ExtendedCoupon(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "value", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "usageCounter", "discountCounter", "discountRemainder", "reservationCounter", "attributes", "referralId", "recipientIntegrationId", "importId", "reservation", "batchId", "isReservationMandatory", "implicitlyReserved", "ApplicationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/feature_flag.py b/talon_one/models/feature_flag.py
index bdb07db..72bf15f 100644
--- a/talon_one/models/feature_flag.py
+++ b/talon_one/models/feature_flag.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class FeatureFlag(BaseModel):
"""
@@ -34,7 +35,8 @@ class FeatureFlag(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value", "created", "modified"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/features_feed.py b/talon_one/models/features_feed.py
index 55a5e82..4e17b67 100644
--- a/talon_one/models/features_feed.py
+++ b/talon_one/models/features_feed.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class FeaturesFeed(BaseModel):
"""
@@ -31,7 +32,8 @@ class FeaturesFeed(BaseModel):
__properties: ClassVar[List[str]] = ["title", "pubDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/func_arg_def.py b/talon_one/models/func_arg_def.py
index a72ca2b..7982ede 100644
--- a/talon_one/models/func_arg_def.py
+++ b/talon_one/models/func_arg_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class FuncArgDef(BaseModel):
"""
@@ -39,7 +40,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/function_def.py b/talon_one/models/function_def.py
index a4eebcd..8a81702 100644
--- a/talon_one/models/function_def.py
+++ b/talon_one/models/function_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.func_arg_def import FuncArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class FunctionDef(BaseModel):
"""
@@ -36,7 +37,8 @@ class FunctionDef(BaseModel):
__properties: ClassVar[List[str]] = ["name", "type", "description", "help", "args"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_audit_log_summary.py b/talon_one/models/generate_audit_log_summary.py
index df44f0b..dad0cf2 100644
--- a/talon_one/models/generate_audit_log_summary.py
+++ b/talon_one/models/generate_audit_log_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateAuditLogSummary(BaseModel):
"""
@@ -30,7 +31,8 @@ class GenerateAuditLogSummary(BaseModel):
__properties: ClassVar[List[str]] = ["logID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_campaign_description.py b/talon_one/models/generate_campaign_description.py
index 8ec56ed..4a9d6ba 100644
--- a/talon_one/models/generate_campaign_description.py
+++ b/talon_one/models/generate_campaign_description.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCampaignDescription(BaseModel):
"""
@@ -32,7 +33,8 @@ class GenerateCampaignDescription(BaseModel):
__properties: ClassVar[List[str]] = ["campaignID", "rulesetID", "currency"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_campaign_summary.py b/talon_one/models/generate_campaign_summary.py
index 4cd5f91..eb94732 100644
--- a/talon_one/models/generate_campaign_summary.py
+++ b/talon_one/models/generate_campaign_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCampaignSummary(BaseModel):
"""
@@ -32,7 +33,8 @@ class GenerateCampaignSummary(BaseModel):
__properties: ClassVar[List[str]] = ["campaignID", "rulesetID", "currency"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_campaign_tags.py b/talon_one/models/generate_campaign_tags.py
index dd022cf..adba8d5 100644
--- a/talon_one/models/generate_campaign_tags.py
+++ b/talon_one/models/generate_campaign_tags.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCampaignTags(BaseModel):
"""
@@ -30,7 +31,8 @@ class GenerateCampaignTags(BaseModel):
__properties: ClassVar[List[str]] = ["rulesetID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_coupon_failure_detailed_summary.py b/talon_one/models/generate_coupon_failure_detailed_summary.py
index f602209..bcdeb7f 100644
--- a/talon_one/models/generate_coupon_failure_detailed_summary.py
+++ b/talon_one/models/generate_coupon_failure_detailed_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCouponFailureDetailedSummary(BaseModel):
"""
@@ -35,7 +36,8 @@ class GenerateCouponFailureDetailedSummary(BaseModel):
__properties: ClassVar[List[str]] = ["applicationID", "sessionID", "eventID", "coupon", "language"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_coupon_failure_summary.py b/talon_one/models/generate_coupon_failure_summary.py
index e479a13..2055942 100644
--- a/talon_one/models/generate_coupon_failure_summary.py
+++ b/talon_one/models/generate_coupon_failure_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCouponFailureSummary(BaseModel):
"""
@@ -31,7 +32,8 @@ class GenerateCouponFailureSummary(BaseModel):
__properties: ClassVar[List[str]] = ["eventID", "language"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_coupon_rejections200_response.py b/talon_one/models/generate_coupon_rejections200_response.py
index 2871203..4b2b61a 100644
--- a/talon_one/models/generate_coupon_rejections200_response.py
+++ b/talon_one/models/generate_coupon_rejections200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.coupon_failure_summary import CouponFailureSummary
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateCouponRejections200Response(BaseModel):
"""
@@ -31,7 +32,8 @@ class GenerateCouponRejections200Response(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_item_filter_description.py b/talon_one/models/generate_item_filter_description.py
index 9f40d20..93cd3ef 100644
--- a/talon_one/models/generate_item_filter_description.py
+++ b/talon_one/models/generate_item_filter_description.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateItemFilterDescription(BaseModel):
"""
@@ -30,7 +31,8 @@ class GenerateItemFilterDescription(BaseModel):
__properties: ClassVar[List[str]] = ["itemFilter"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_loyalty_card.py b/talon_one/models/generate_loyalty_card.py
index 79a19a6..db81ef3 100644
--- a/talon_one/models/generate_loyalty_card.py
+++ b/talon_one/models/generate_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateLoyaltyCard(BaseModel):
"""
@@ -53,7 +54,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_rule_title.py b/talon_one/models/generate_rule_title.py
index ba6239b..d106e87 100644
--- a/talon_one/models/generate_rule_title.py
+++ b/talon_one/models/generate_rule_title.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.generate_rule_title_rule import GenerateRuleTitleRule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateRuleTitle(BaseModel):
"""
@@ -32,7 +33,8 @@ class GenerateRuleTitle(BaseModel):
__properties: ClassVar[List[str]] = ["rule", "currency"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_rule_title_rule.py b/talon_one/models/generate_rule_title_rule.py
index a40958a..f4b8740 100644
--- a/talon_one/models/generate_rule_title_rule.py
+++ b/talon_one/models/generate_rule_title_rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateRuleTitleRule(BaseModel):
"""
@@ -32,7 +33,8 @@ class GenerateRuleTitleRule(BaseModel):
__properties: ClassVar[List[str]] = ["effects", "condition"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/generate_user_session_summary.py b/talon_one/models/generate_user_session_summary.py
index 11a236b..be0af99 100644
--- a/talon_one/models/generate_user_session_summary.py
+++ b/talon_one/models/generate_user_session_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GenerateUserSessionSummary(BaseModel):
"""
@@ -31,7 +32,8 @@ class GenerateUserSessionSummary(BaseModel):
__properties: ClassVar[List[str]] = ["sessionID", "applicationID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_access_logs_without_total_count200_response.py b/talon_one/models/get_access_logs_without_total_count200_response.py
index 496a660..a32eb53 100644
--- a/talon_one/models/get_access_logs_without_total_count200_response.py
+++ b/talon_one/models/get_access_logs_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.access_log_entry import AccessLogEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAccessLogsWithoutTotalCount200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetAccessLogsWithoutTotalCount200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_additional_costs200_response.py b/talon_one/models/get_additional_costs200_response.py
index 18009d5..5192441 100644
--- a/talon_one/models/get_additional_costs200_response.py
+++ b/talon_one/models/get_additional_costs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.account_additional_cost import AccountAdditionalCost
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAdditionalCosts200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetAdditionalCosts200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_customer_friends200_response.py b/talon_one/models/get_application_customer_friends200_response.py
index b86a767..191238b 100644
--- a/talon_one/models/get_application_customer_friends200_response.py
+++ b/talon_one/models/get_application_customer_friends200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_referee import ApplicationReferee
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationCustomerFriends200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetApplicationCustomerFriends200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_customers200_response.py b/talon_one/models/get_application_customers200_response.py
index b0fcfc9..d003531 100644
--- a/talon_one/models/get_application_customers200_response.py
+++ b/talon_one/models/get_application_customers200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_customer import ApplicationCustomer
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationCustomers200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetApplicationCustomers200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_customers_by_attributes200_response.py b/talon_one/models/get_application_customers_by_attributes200_response.py
index 216fea9..4069017 100644
--- a/talon_one/models/get_application_customers_by_attributes200_response.py
+++ b/talon_one/models/get_application_customers_by_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_customer import ApplicationCustomer
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationCustomersByAttributes200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetApplicationCustomersByAttributes200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_event_types200_response.py b/talon_one/models/get_application_event_types200_response.py
index 8bbf3fd..f3593f7 100644
--- a/talon_one/models/get_application_event_types200_response.py
+++ b/talon_one/models/get_application_event_types200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationEventTypes200Response(BaseModel):
"""
@@ -31,7 +32,8 @@ class GetApplicationEventTypes200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_events_without_total_count200_response.py b/talon_one/models/get_application_events_without_total_count200_response.py
index a2245b7..0ea8e7a 100644
--- a/talon_one/models/get_application_events_without_total_count200_response.py
+++ b/talon_one/models/get_application_events_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_event import ApplicationEvent
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationEventsWithoutTotalCount200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetApplicationEventsWithoutTotalCount200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_application_sessions200_response.py b/talon_one/models/get_application_sessions200_response.py
index bbedf7d..e073091 100644
--- a/talon_one/models/get_application_sessions200_response.py
+++ b/talon_one/models/get_application_sessions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application_session import ApplicationSession
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplicationSessions200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetApplicationSessions200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_applications200_response.py b/talon_one/models/get_applications200_response.py
index 81d35a1..1c21038 100644
--- a/talon_one/models/get_applications200_response.py
+++ b/talon_one/models/get_applications200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.application import Application
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetApplications200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetApplications200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_attributes200_response.py b/talon_one/models/get_attributes200_response.py
index 0c63cf8..94a6943 100644
--- a/talon_one/models/get_attributes200_response.py
+++ b/talon_one/models/get_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.attribute import Attribute
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAttributes200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetAttributes200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_audience_memberships200_response.py b/talon_one/models/get_audience_memberships200_response.py
index 46d1cd1..a81133b 100644
--- a/talon_one/models/get_audience_memberships200_response.py
+++ b/talon_one/models/get_audience_memberships200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile import CustomerProfile
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAudienceMemberships200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetAudienceMemberships200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_audiences200_response.py b/talon_one/models/get_audiences200_response.py
index 3fd7ef2..731b008 100644
--- a/talon_one/models/get_audiences200_response.py
+++ b/talon_one/models/get_audiences200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.audience import Audience
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAudiences200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetAudiences200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_audiences_analytics200_response.py b/talon_one/models/get_audiences_analytics200_response.py
index f1a4b86..9648279 100644
--- a/talon_one/models/get_audiences_analytics200_response.py
+++ b/talon_one/models/get_audiences_analytics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.audience_analytics import AudienceAnalytics
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetAudiencesAnalytics200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetAudiencesAnalytics200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_campaign_analytics200_response.py b/talon_one/models/get_campaign_analytics200_response.py
index 3440a0e..35cef8f 100644
--- a/talon_one/models/get_campaign_analytics200_response.py
+++ b/talon_one/models/get_campaign_analytics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_analytics import CampaignAnalytics
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCampaignAnalytics200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCampaignAnalytics200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_campaign_groups200_response.py b/talon_one/models/get_campaign_groups200_response.py
index 4de1449..93852d6 100644
--- a/talon_one/models/get_campaign_groups200_response.py
+++ b/talon_one/models/get_campaign_groups200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_group import CampaignGroup
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCampaignGroups200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCampaignGroups200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_campaign_templates200_response.py b/talon_one/models/get_campaign_templates200_response.py
index 0d441cb..79757fa 100644
--- a/talon_one/models/get_campaign_templates200_response.py
+++ b/talon_one/models/get_campaign_templates200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign_template import CampaignTemplate
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCampaignTemplates200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCampaignTemplates200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_campaigns200_response.py b/talon_one/models/get_campaigns200_response.py
index e60a820..cdb0d96 100644
--- a/talon_one/models/get_campaigns200_response.py
+++ b/talon_one/models/get_campaigns200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.campaign import Campaign
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCampaigns200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCampaigns200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_changes200_response.py b/talon_one/models/get_changes200_response.py
index 81c1027..4342209 100644
--- a/talon_one/models/get_changes200_response.py
+++ b/talon_one/models/get_changes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.change import Change
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetChanges200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetChanges200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_collection_items200_response.py b/talon_one/models/get_collection_items200_response.py
index 71db041..e3574f1 100644
--- a/talon_one/models/get_collection_items200_response.py
+++ b/talon_one/models/get_collection_items200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.collection_item import CollectionItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCollectionItems200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCollectionItems200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_coupons_without_total_count200_response.py b/talon_one/models/get_coupons_without_total_count200_response.py
index 8bd53c7..d797303 100644
--- a/talon_one/models/get_coupons_without_total_count200_response.py
+++ b/talon_one/models/get_coupons_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.coupon import Coupon
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCouponsWithoutTotalCount200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCouponsWithoutTotalCount200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customer_achievement_history200_response.py b/talon_one/models/get_customer_achievement_history200_response.py
index 57f8ffb..2f93995 100644
--- a/talon_one/models/get_customer_achievement_history200_response.py
+++ b/talon_one/models/get_customer_achievement_history200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.achievement_progress import AchievementProgress
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomerAchievementHistory200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCustomerAchievementHistory200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customer_achievements200_response.py b/talon_one/models/get_customer_achievements200_response.py
index 24cd3d2..4a06626 100644
--- a/talon_one/models/get_customer_achievements200_response.py
+++ b/talon_one/models/get_customer_achievements200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.achievement_status_entry import AchievementStatusEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomerAchievements200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCustomerAchievements200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customer_activity_reports_without_total_count200_response.py b/talon_one/models/get_customer_activity_reports_without_total_count200_response.py
index ac1a830..94bcbc3 100644
--- a/talon_one/models/get_customer_activity_reports_without_total_count200_response.py
+++ b/talon_one/models/get_customer_activity_reports_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_activity_report import CustomerActivityReport
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomerActivityReportsWithoutTotalCount200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCustomerActivityReportsWithoutTotalCount200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customer_profile_achievement_progress200_response.py b/talon_one/models/get_customer_profile_achievement_progress200_response.py
index 588bfd0..5f83c02 100644
--- a/talon_one/models/get_customer_profile_achievement_progress200_response.py
+++ b/talon_one/models/get_customer_profile_achievement_progress200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.achievement_progress_with_definition import AchievementProgressWithDefinition
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomerProfileAchievementProgress200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCustomerProfileAchievementProgress200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customer_profiles200_response.py b/talon_one/models/get_customer_profiles200_response.py
index 02ae686..e54ea15 100644
--- a/talon_one/models/get_customer_profiles200_response.py
+++ b/talon_one/models/get_customer_profiles200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile import CustomerProfile
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomerProfiles200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetCustomerProfiles200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_customers_by_attributes200_response.py b/talon_one/models/get_customers_by_attributes200_response.py
index 8464027..cbaba17 100644
--- a/talon_one/models/get_customers_by_attributes200_response.py
+++ b/talon_one/models/get_customers_by_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile import CustomerProfile
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetCustomersByAttributes200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class GetCustomersByAttributes200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_dashboard_statistics200_response.py b/talon_one/models/get_dashboard_statistics200_response.py
index feb4704..afb2a1e 100644
--- a/talon_one/models/get_dashboard_statistics200_response.py
+++ b/talon_one/models/get_dashboard_statistics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_dashboard_data import LoyaltyDashboardData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetDashboardStatistics200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetDashboardStatistics200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_event_types200_response.py b/talon_one/models/get_event_types200_response.py
index ff5a05b..a1701ed 100644
--- a/talon_one/models/get_event_types200_response.py
+++ b/talon_one/models/get_event_types200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.event_type import EventType
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetEventTypes200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetEventTypes200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_exports200_response.py b/talon_one/models/get_exports200_response.py
index cee7ea4..aade45f 100644
--- a/talon_one/models/get_exports200_response.py
+++ b/talon_one/models/get_exports200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.export import Export
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetExports200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetExports200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_integration_coupon_request.py b/talon_one/models/get_integration_coupon_request.py
index 62b9920..c0f4512 100644
--- a/talon_one/models/get_integration_coupon_request.py
+++ b/talon_one/models/get_integration_coupon_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetIntegrationCouponRequest(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetIntegrationCouponRequest(BaseModel):
__properties: ClassVar[List[str]] = ["campaignIds", "limit"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_card_points200_response.py b/talon_one/models/get_loyalty_card_points200_response.py
index f135cdd..e00705f 100644
--- a/talon_one/models/get_loyalty_card_points200_response.py
+++ b/talon_one/models/get_loyalty_card_points200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.card_ledger_points_entry_integration_api import CardLedgerPointsEntryIntegrationAPI
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyCardPoints200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyCardPoints200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_card_transaction_logs200_response.py b/talon_one/models/get_loyalty_card_transaction_logs200_response.py
index 7456f21..325ae65 100644
--- a/talon_one/models/get_loyalty_card_transaction_logs200_response.py
+++ b/talon_one/models/get_loyalty_card_transaction_logs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.card_ledger_transaction_log_entry import CardLedgerTransactionLogEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyCardTransactionLogs200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyCardTransactionLogs200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_card_transactions200_response.py b/talon_one/models/get_loyalty_card_transactions200_response.py
index 1dd622e..bb3d497 100644
--- a/talon_one/models/get_loyalty_card_transactions200_response.py
+++ b/talon_one/models/get_loyalty_card_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.card_ledger_transaction_log_entry_integration_api import CardLedgerTransactionLogEntryIntegrationAPI
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyCardTransactions200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyCardTransactions200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_cards200_response.py b/talon_one/models/get_loyalty_cards200_response.py
index 3e6c6f2..f3d1346 100644
--- a/talon_one/models/get_loyalty_cards200_response.py
+++ b/talon_one/models/get_loyalty_cards200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_card import LoyaltyCard
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyCards200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyCards200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_program_profile_points200_response.py b/talon_one/models/get_loyalty_program_profile_points200_response.py
index 7377632..48d799e 100644
--- a/talon_one/models/get_loyalty_program_profile_points200_response.py
+++ b/talon_one/models/get_loyalty_program_profile_points200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.ledger_points_entry_integration_api import LedgerPointsEntryIntegrationAPI
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyProgramProfilePoints200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyProgramProfilePoints200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_program_profile_transactions200_response.py b/talon_one/models/get_loyalty_program_profile_transactions200_response.py
index 86ab0e5..37b6b13 100644
--- a/talon_one/models/get_loyalty_program_profile_transactions200_response.py
+++ b/talon_one/models/get_loyalty_program_profile_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.ledger_transaction_log_entry_integration_api import LedgerTransactionLogEntryIntegrationAPI
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyProgramProfileTransactions200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyProgramProfileTransactions200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_program_transactions200_response.py b/talon_one/models/get_loyalty_program_transactions200_response.py
index 1070fd9..85a3af3 100644
--- a/talon_one/models/get_loyalty_program_transactions200_response.py
+++ b/talon_one/models/get_loyalty_program_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_program_transaction import LoyaltyProgramTransaction
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyProgramTransactions200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyProgramTransactions200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_loyalty_programs200_response.py b/talon_one/models/get_loyalty_programs200_response.py
index d017f77..19f1b2b 100644
--- a/talon_one/models/get_loyalty_programs200_response.py
+++ b/talon_one/models/get_loyalty_programs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_program import LoyaltyProgram
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetLoyaltyPrograms200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetLoyaltyPrograms200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_referrals_without_total_count200_response.py b/talon_one/models/get_referrals_without_total_count200_response.py
index 6bd3c5a..2398881 100644
--- a/talon_one/models/get_referrals_without_total_count200_response.py
+++ b/talon_one/models/get_referrals_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.referral import Referral
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetReferralsWithoutTotalCount200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetReferralsWithoutTotalCount200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_reserved_customers200_response.py b/talon_one/models/get_reserved_customers200_response.py
index e3a4554..02bbb4a 100644
--- a/talon_one/models/get_reserved_customers200_response.py
+++ b/talon_one/models/get_reserved_customers200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile import CustomerProfile
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetReservedCustomers200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetReservedCustomers200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_rulesets200_response.py b/talon_one/models/get_rulesets200_response.py
index 02617bb..c3ca8f0 100644
--- a/talon_one/models/get_rulesets200_response.py
+++ b/talon_one/models/get_rulesets200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.ruleset import Ruleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetRulesets200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetRulesets200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_users200_response.py b/talon_one/models/get_users200_response.py
index 9689493..e71c080 100644
--- a/talon_one/models/get_users200_response.py
+++ b/talon_one/models/get_users200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.user import User
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetUsers200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetUsers200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/get_webhooks200_response.py b/talon_one/models/get_webhooks200_response.py
index 86963c8..5610df0 100644
--- a/talon_one/models/get_webhooks200_response.py
+++ b/talon_one/models/get_webhooks200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.webhook_with_outgoing_integration_details import WebhookWithOutgoingIntegrationDetails
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GetWebhooks200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class GetWebhooks200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/giveaway.py b/talon_one/models/giveaway.py
index 2792710..e8f2088 100644
--- a/talon_one/models/giveaway.py
+++ b/talon_one/models/giveaway.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Giveaway(BaseModel):
"""
@@ -41,7 +42,8 @@ class Giveaway(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "code", "poolId", "startDate", "endDate", "attributes", "used", "importId", "profileIntegrationId", "profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/giveaway_pool_notification.py b/talon_one/models/giveaway_pool_notification.py
new file mode 100644
index 0000000..cce85ed
--- /dev/null
+++ b/talon_one/models/giveaway_pool_notification.py
@@ -0,0 +1,107 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictInt, StrictStr, field_validator
+from typing import Any, ClassVar, Dict, List
+from talon_one.models.giveaway_pool_notification_data import GiveawayPoolNotificationData
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class GiveawayPoolNotification(BaseModel):
+ """
+ GiveawayPoolNotification
+ """ # noqa: E501
+ total_result_size: StrictInt = Field(alias="TotalResultSize")
+ data: List[GiveawayPoolNotificationData] = Field(description="The array of giveaway pool notifications.", alias="Data")
+ notification_type: StrictStr = Field(description="The type of notification.", alias="NotificationType")
+ __properties: ClassVar[List[str]] = ["TotalResultSize", "Data", "NotificationType"]
+
+ @field_validator('notification_type')
+ def notification_type_validate_enum(cls, value):
+ """Validates the enum"""
+ if value not in set(['GiveawayPoolNotification']):
+ raise ValueError("must be one of enum values ('GiveawayPoolNotification')")
+ return value
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of GiveawayPoolNotification from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ # override the default output from pydantic by calling `to_dict()` of each item in data (list)
+ _items = []
+ if self.data:
+ for _item_data in self.data:
+ if _item_data:
+ _items.append(_item_data.to_dict())
+ _dict['Data'] = _items
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of GiveawayPoolNotification from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "TotalResultSize": obj.get("TotalResultSize"),
+ "Data": [GiveawayPoolNotificationData.from_dict(_item) for _item in obj["Data"]] if obj.get("Data") is not None else None,
+ "NotificationType": obj.get("NotificationType")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/giveaway_pool_notification_data.py b/talon_one/models/giveaway_pool_notification_data.py
new file mode 100644
index 0000000..b4e7894
--- /dev/null
+++ b/talon_one/models/giveaway_pool_notification_data.py
@@ -0,0 +1,107 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictInt, StrictStr
+from typing import Any, ClassVar, Dict, List
+from typing_extensions import Annotated
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class GiveawayPoolNotificationData(BaseModel):
+ """
+ GiveawayPoolNotificationData
+ """ # noqa: E501
+ event: StrictStr = Field(description="The event type of the notification.", alias="Event")
+ pool_id: Annotated[int, Field(strict=True, ge=1)] = Field(description="The ID of the giveaway pool.", alias="PoolId")
+ pool_name: StrictStr = Field(description="The name of the giveaway pool.", alias="PoolName")
+ pool_description: StrictStr = Field(description="The description of the giveaway pool.", alias="PoolDescription")
+ account_id: Annotated[int, Field(strict=True, ge=1)] = Field(description="The ID of the account that owns the giveaway pool.", alias="AccountId")
+ application_id: Annotated[int, Field(strict=True, ge=1)] = Field(description="The ID of the Application connected to the giveaway pool.", alias="ApplicationId")
+ total_codes: StrictInt = Field(description="The total number of codes in the giveaway pool.", alias="TotalCodes")
+ used_codes: StrictInt = Field(description="The number of codes that have been used.", alias="UsedCodes")
+ remaining_codes: StrictInt = Field(description="The number of codes remaining in the giveaway pool.", alias="RemainingCodes")
+ threshold_percent: StrictInt = Field(description="The percentage threshold for the notification. The notification is triggered when the number of codes drops below this threshold.", alias="ThresholdPercent")
+ __properties: ClassVar[List[str]] = ["Event", "PoolId", "PoolName", "PoolDescription", "AccountId", "ApplicationId", "TotalCodes", "UsedCodes", "RemainingCodes", "ThresholdPercent"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of GiveawayPoolNotificationData from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of GiveawayPoolNotificationData from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "Event": obj.get("Event"),
+ "PoolId": obj.get("PoolId"),
+ "PoolName": obj.get("PoolName"),
+ "PoolDescription": obj.get("PoolDescription"),
+ "AccountId": obj.get("AccountId"),
+ "ApplicationId": obj.get("ApplicationId"),
+ "TotalCodes": obj.get("TotalCodes"),
+ "UsedCodes": obj.get("UsedCodes"),
+ "RemainingCodes": obj.get("RemainingCodes"),
+ "ThresholdPercent": obj.get("ThresholdPercent")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/giveaways_pool.py b/talon_one/models/giveaways_pool.py
index a619fab..a4af438 100644
--- a/talon_one/models/giveaways_pool.py
+++ b/talon_one/models/giveaways_pool.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class GiveawaysPool(BaseModel):
"""
@@ -40,7 +41,8 @@ class GiveawaysPool(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "accountId", "name", "description", "subscribedApplicationsIds", "sandbox", "modified", "createdBy", "modifiedBy"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/hidden_conditions_effects.py b/talon_one/models/hidden_conditions_effects.py
index e129f90..8078ba1 100644
--- a/talon_one/models/hidden_conditions_effects.py
+++ b/talon_one/models/hidden_conditions_effects.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class HiddenConditionsEffects(BaseModel):
"""
@@ -33,7 +34,8 @@ class HiddenConditionsEffects(BaseModel):
__properties: ClassVar[List[str]] = ["builtInEffects", "conditions", "customEffects", "webhooks"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/history.py b/talon_one/models/history.py
index 57fa1a3..13700d3 100644
--- a/talon_one/models/history.py
+++ b/talon_one/models/history.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.best_prior_price_metadata import BestPriorPriceMetadata
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class History(BaseModel):
"""
@@ -37,7 +38,8 @@ class History(BaseModel):
__properties: ClassVar[List[str]] = ["id", "observedAt", "contextId", "price", "metadata", "target"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/identifiable_entity.py b/talon_one/models/identifiable_entity.py
index bc6e9f8..54f2e60 100644
--- a/talon_one/models/identifiable_entity.py
+++ b/talon_one/models/identifiable_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IdentifiableEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class IdentifiableEntity(BaseModel):
__properties: ClassVar[List[str]] = ["id"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/import_entity.py b/talon_one/models/import_entity.py
index 9e0133d..750a7ab 100644
--- a/talon_one/models/import_entity.py
+++ b/talon_one/models/import_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ImportEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class ImportEntity(BaseModel):
__properties: ClassVar[List[str]] = ["importId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/increase_achievement_progress_effect_props.py b/talon_one/models/increase_achievement_progress_effect_props.py
index e224e41..3f7283b 100644
--- a/talon_one/models/increase_achievement_progress_effect_props.py
+++ b/talon_one/models/increase_achievement_progress_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IncreaseAchievementProgressEffectProps(BaseModel):
"""
@@ -36,7 +37,8 @@ class IncreaseAchievementProgressEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["achievementId", "achievementName", "progressTrackerId", "delta", "value", "target", "isJustCompleted"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/influencing_campaign_details.py b/talon_one/models/influencing_campaign_details.py
index 3452c23..9a85e84 100644
--- a/talon_one/models/influencing_campaign_details.py
+++ b/talon_one/models/influencing_campaign_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class InfluencingCampaignDetails(BaseModel):
"""
@@ -31,7 +32,8 @@ class InfluencingCampaignDetails(BaseModel):
__properties: ClassVar[List[str]] = ["campaignId", "discountValue"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_campaign.py b/talon_one/models/integration_campaign.py
index 0e3857e..e018146 100644
--- a/talon_one/models/integration_campaign.py
+++ b/talon_one/models/integration_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationCampaign(BaseModel):
"""
@@ -56,7 +57,8 @@ def features_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_coupon.py b/talon_one/models/integration_coupon.py
index b4ce9c0..7d080d9 100644
--- a/talon_one/models/integration_coupon.py
+++ b/talon_one/models/integration_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationCoupon(BaseModel):
"""
@@ -55,7 +56,8 @@ class IntegrationCoupon(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "value", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "usageCounter", "discountCounter", "discountRemainder", "reservationCounter", "attributes", "referralId", "recipientIntegrationId", "importId", "reservation", "batchId", "isReservationMandatory", "implicitlyReserved", "profileRedemptionCount"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_customer_profile_audience_request.py b/talon_one/models/integration_customer_profile_audience_request.py
index 5c01a54..8a92298 100644
--- a/talon_one/models/integration_customer_profile_audience_request.py
+++ b/talon_one/models/integration_customer_profile_audience_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.integration_customer_profile_audience_request_item import IntegrationCustomerProfileAudienceRequestItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationCustomerProfileAudienceRequest(BaseModel):
"""
@@ -31,7 +32,8 @@ class IntegrationCustomerProfileAudienceRequest(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_customer_profile_audience_request_item.py b/talon_one/models/integration_customer_profile_audience_request_item.py
index 04c56af..bc09959 100644
--- a/talon_one/models/integration_customer_profile_audience_request_item.py
+++ b/talon_one/models/integration_customer_profile_audience_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationCustomerProfileAudienceRequestItem(BaseModel):
"""
@@ -40,7 +41,8 @@ def action_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_customer_session_response.py b/talon_one/models/integration_customer_session_response.py
index 4cf051a..c4def47 100644
--- a/talon_one/models/integration_customer_session_response.py
+++ b/talon_one/models/integration_customer_session_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.effect import Effect
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationCustomerSessionResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class IntegrationCustomerSessionResponse(BaseModel):
__properties: ClassVar[List[str]] = ["customerSession", "effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_entity.py b/talon_one/models/integration_entity.py
index 9352198..e94a7d2 100644
--- a/talon_one/models/integration_entity.py
+++ b/talon_one/models/integration_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEntity(BaseModel):
"""
@@ -33,7 +34,8 @@ class IntegrationEntity(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_event.py b/talon_one/models/integration_event.py
index 3a34836..c452514 100644
--- a/talon_one/models/integration_event.py
+++ b/talon_one/models/integration_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEvent(BaseModel):
"""
@@ -34,7 +35,8 @@ class IntegrationEvent(BaseModel):
__properties: ClassVar[List[str]] = ["profileId", "storeIntegrationId", "type", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_event_v2_request.py b/talon_one/models/integration_event_v2_request.py
index 4a29e82..f4697fe 100644
--- a/talon_one/models/integration_event_v2_request.py
+++ b/talon_one/models/integration_event_v2_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEventV2Request(BaseModel):
"""
@@ -48,7 +49,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -60,8 +62,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_event_v2_response.py b/talon_one/models/integration_event_v2_response.py
index cc5b916..3d0dcbd 100644
--- a/talon_one/models/integration_event_v2_response.py
+++ b/talon_one/models/integration_event_v2_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -30,6 +30,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEventV2Response(BaseModel):
"""
@@ -47,7 +48,8 @@ class IntegrationEventV2Response(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile", "loyalty", "triggeredCampaigns", "effects", "ruleFailureReasons", "createdCoupons", "createdReferrals", "awardedGiveaways", "event"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_event_v3_request.py b/talon_one/models/integration_event_v3_request.py
index db5323f..8def776 100644
--- a/talon_one/models/integration_event_v3_request.py
+++ b/talon_one/models/integration_event_v3_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEventV3Request(BaseModel):
"""
@@ -51,7 +52,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -63,8 +65,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_event_v3_response.py b/talon_one/models/integration_event_v3_response.py
index 1343171..cb24b55 100644
--- a/talon_one/models/integration_event_v3_response.py
+++ b/talon_one/models/integration_event_v3_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -30,6 +30,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationEventV3Response(BaseModel):
"""
@@ -47,7 +48,8 @@ class IntegrationEventV3Response(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile", "loyalty", "triggeredCampaigns", "effects", "ruleFailureReasons", "createdCoupons", "createdReferrals", "awardedGiveaways", "advancedEvent"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_config.py b/talon_one/models/integration_hub_config.py
index 928e714..6eb568f 100644
--- a/talon_one/models/integration_hub_config.py
+++ b/talon_one/models/integration_hub_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubConfig(BaseModel):
"""
@@ -31,7 +32,8 @@ class IntegrationHubConfig(BaseModel):
__properties: ClassVar[List[str]] = ["integrationHubUrl", "accessToken"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_coupon_based_notifications.py b/talon_one/models/integration_hub_event_payload_coupon_based_notifications.py
index ac42446..689ac79 100644
--- a/talon_one/models/integration_hub_event_payload_coupon_based_notifications.py
+++ b/talon_one/models/integration_hub_event_payload_coupon_based_notifications.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.integration_hub_event_payload_coupon_based_notifications_limits import IntegrationHubEventPayloadCouponBasedNotificationsLimits
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadCouponBasedNotifications(BaseModel):
"""
@@ -52,7 +53,8 @@ class IntegrationHubEventPayloadCouponBasedNotifications(BaseModel):
__properties: ClassVar[List[str]] = ["Id", "Created", "CampaignId", "Value", "UsageLimit", "DiscountLimit", "ReservationLimit", "StartDate", "ExpiryDate", "UsageCounter", "DiscountCounter", "DiscountRemainder", "ReferralId", "RecipientIntegrationId", "ImportId", "BatchId", "Attributes", "Limits", "PublishedAt", "SourceOfEvent", "EmployeeName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -64,8 +66,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_coupon_based_notifications_limits.py b/talon_one/models/integration_hub_event_payload_coupon_based_notifications_limits.py
index 43e3ae5..ee82722 100644
--- a/talon_one/models/integration_hub_event_payload_coupon_based_notifications_limits.py
+++ b/talon_one/models/integration_hub_event_payload_coupon_based_notifications_limits.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadCouponBasedNotificationsLimits(BaseModel):
"""
@@ -33,7 +34,8 @@ class IntegrationHubEventPayloadCouponBasedNotificationsLimits(BaseModel):
__properties: ClassVar[List[str]] = ["Action", "Limit", "Period", "Entities"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_notification.py b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_notification.py
index 41fef0b..ff766e4 100644
--- a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_notification.py
+++ b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action import IntegrationHubEventPayloadLoyaltyProfileBasedPointsChangedNotificationAction
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadLoyaltyProfileBasedNotification(BaseModel):
"""
@@ -46,7 +47,8 @@ class IntegrationHubEventPayloadLoyaltyProfileBasedNotification(BaseModel):
__properties: ClassVar[List[str]] = ["ProfileIntegrationID", "LoyaltyProgramID", "SubledgerID", "SourceOfEvent", "EmployeeName", "UserID", "CurrentPoints", "Actions", "PublishedAt", "CurrentTier", "OldTier", "TierExpirationDate", "TimestampOfTierChange", "PointsRequiredToTheNextTier", "NextTier"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
index 784534b..1bcee00 100644
--- a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
+++ b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action import IntegrationHubEventPayloadLoyaltyProfileBasedPointsChangedNotificationAction
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadLoyaltyProfileBasedPointsChangedNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ class IntegrationHubEventPayloadLoyaltyProfileBasedPointsChangedNotification(Bas
__properties: ClassVar[List[str]] = ["ProfileIntegrationID", "LoyaltyProgramID", "SubledgerID", "SourceOfEvent", "EmployeeName", "UserID", "CurrentPoints", "Actions", "PublishedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
index 9e06dda..7975eba 100644
--- a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
+++ b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadLoyaltyProfileBasedPointsChangedNotificationAction(BaseModel):
"""
@@ -44,7 +45,8 @@ def operation_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
index 6177ae7..64ea7fb 100644
--- a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
+++ b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadLoyaltyProfileBasedTierDowngradeNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ class IntegrationHubEventPayloadLoyaltyProfileBasedTierDowngradeNotification(Bas
__properties: ClassVar[List[str]] = ["ProfileIntegrationID", "LoyaltyProgramID", "SubledgerID", "SourceOfEvent", "CurrentTier", "CurrentPoints", "OldTier", "TierExpirationDate", "TimestampOfTierChange", "PublishedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
index d3134a1..66b8269 100644
--- a/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
+++ b/talon_one/models/integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventPayloadLoyaltyProfileBasedTierUpgradeNotification(BaseModel):
"""
@@ -42,7 +43,8 @@ class IntegrationHubEventPayloadLoyaltyProfileBasedTierUpgradeNotification(BaseM
__properties: ClassVar[List[str]] = ["ProfileIntegrationID", "LoyaltyProgramID", "SubledgerID", "SourceOfEvent", "CurrentTier", "CurrentPoints", "OldTier", "PointsRequiredToTheNextTier", "NextTier", "TierExpirationDate", "TimestampOfTierChange", "PublishedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_event_record.py b/talon_one/models/integration_hub_event_record.py
index 503a223..95f408e 100644
--- a/talon_one/models/integration_hub_event_record.py
+++ b/talon_one/models/integration_hub_event_record.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubEventRecord(BaseModel):
"""
@@ -38,7 +39,8 @@ class IntegrationHubEventRecord(BaseModel):
__properties: ClassVar[List[str]] = ["Id", "FlowId", "EventType", "EventData", "PublishedAt", "ProcessedAt", "ProcessAfter", "Retry"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_flow.py b/talon_one/models/integration_hub_flow.py
index b270440..b20a5a3 100644
--- a/talon_one/models/integration_hub_flow.py
+++ b/talon_one/models/integration_hub_flow.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubFlow(BaseModel):
"""
@@ -32,7 +33,8 @@ class IntegrationHubFlow(BaseModel):
__properties: ClassVar[List[str]] = ["ApplicationID", "EventType", "IntegrationHubFlowUrl"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_flow_config.py b/talon_one/models/integration_hub_flow_config.py
index 54430cf..a5f17b3 100644
--- a/talon_one/models/integration_hub_flow_config.py
+++ b/talon_one/models/integration_hub_flow_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubFlowConfig(BaseModel):
"""
@@ -34,7 +35,8 @@ class IntegrationHubFlowConfig(BaseModel):
__properties: ClassVar[List[str]] = ["ApiKey", "WorkerCount", "MaxEventsPerMessage", "MaxRetries"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_flow_config_response.py b/talon_one/models/integration_hub_flow_config_response.py
index 6f67944..e32a232 100644
--- a/talon_one/models/integration_hub_flow_config_response.py
+++ b/talon_one/models/integration_hub_flow_config_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubFlowConfigResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class IntegrationHubFlowConfigResponse(BaseModel):
__properties: ClassVar[List[str]] = ["WorkerCount", "MaxEventsPerMessage", "MaxRetries"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_flow_response.py b/talon_one/models/integration_hub_flow_response.py
index d952f07..3d6db35 100644
--- a/talon_one/models/integration_hub_flow_response.py
+++ b/talon_one/models/integration_hub_flow_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.integration_hub_flow_config_response import IntegrationHubFlowConfigResponse
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubFlowResponse(BaseModel):
"""
@@ -35,7 +36,8 @@ class IntegrationHubFlowResponse(BaseModel):
__properties: ClassVar[List[str]] = ["Id", "ApplicationID", "EventType", "IntegrationHubFlowUrl", "Config"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_flow_with_config.py b/talon_one/models/integration_hub_flow_with_config.py
index 44d06de..1527886 100644
--- a/talon_one/models/integration_hub_flow_with_config.py
+++ b/talon_one/models/integration_hub_flow_with_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.integration_hub_flow_config import IntegrationHubFlowConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubFlowWithConfig(BaseModel):
"""
@@ -34,7 +35,8 @@ class IntegrationHubFlowWithConfig(BaseModel):
__properties: ClassVar[List[str]] = ["ApplicationID", "EventType", "IntegrationHubFlowUrl", "Config"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_hub_paginated_event_payload.py b/talon_one/models/integration_hub_paginated_event_payload.py
index 6dd4721..4674451 100644
--- a/talon_one/models/integration_hub_paginated_event_payload.py
+++ b/talon_one/models/integration_hub_paginated_event_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationHubPaginatedEventPayload(BaseModel):
"""
@@ -41,7 +42,8 @@ def event_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_profile_entity.py b/talon_one/models/integration_profile_entity.py
index 4cf3c6f..62ccdee 100644
--- a/talon_one/models/integration_profile_entity.py
+++ b/talon_one/models/integration_profile_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationProfileEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class IntegrationProfileEntity(BaseModel):
__properties: ClassVar[List[str]] = ["profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_profile_entity_v3.py b/talon_one/models/integration_profile_entity_v3.py
index b71584f..1bd1423 100644
--- a/talon_one/models/integration_profile_entity_v3.py
+++ b/talon_one/models/integration_profile_entity_v3.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationProfileEntityV3(BaseModel):
"""
@@ -30,7 +31,8 @@ class IntegrationProfileEntityV3(BaseModel):
__properties: ClassVar[List[str]] = ["profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_request.py b/talon_one/models/integration_request.py
index e78683d..7f4ec82 100644
--- a/talon_one/models/integration_request.py
+++ b/talon_one/models/integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_customer_session_v2 import NewCustomerSessionV2
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationRequest(BaseModel):
"""
@@ -43,7 +44,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_response.py b/talon_one/models/integration_response.py
index 1db3914..b36fe6a 100644
--- a/talon_one/models/integration_response.py
+++ b/talon_one/models/integration_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -29,6 +29,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationResponse(BaseModel):
"""
@@ -45,7 +46,8 @@ class IntegrationResponse(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile", "loyalty", "triggeredCampaigns", "effects", "ruleFailureReasons", "createdCoupons", "createdReferrals", "awardedGiveaways"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_state.py b/talon_one/models/integration_state.py
index d688834..bfcb4c4 100644
--- a/talon_one/models/integration_state.py
+++ b/talon_one/models/integration_state.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.loyalty import Loyalty
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationState(BaseModel):
"""
@@ -39,7 +40,8 @@ class IntegrationState(BaseModel):
__properties: ClassVar[List[str]] = ["session", "profile", "event", "loyalty", "coupon"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_state_v2.py b/talon_one/models/integration_state_v2.py
index daccafd..5d61de5 100644
--- a/talon_one/models/integration_state_v2.py
+++ b/talon_one/models/integration_state_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -35,6 +35,7 @@
from talon_one.models.rule_failure_reason import RuleFailureReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationStateV2(BaseModel):
"""
@@ -58,7 +59,8 @@ class IntegrationStateV2(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfile", "loyalty", "triggeredCampaigns", "effects", "ruleFailureReasons", "createdCoupons", "createdReferrals", "awardedGiveaways", "referral", "coupons", "event", "advancedEvent", "customerSession", "return", "previousReturns"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -70,8 +72,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/integration_store_entity.py b/talon_one/models/integration_store_entity.py
index b23a7a4..62821c7 100644
--- a/talon_one/models/integration_store_entity.py
+++ b/talon_one/models/integration_store_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class IntegrationStoreEntity(BaseModel):
"""
@@ -31,7 +32,8 @@ class IntegrationStoreEntity(BaseModel):
__properties: ClassVar[List[str]] = ["storeIntegrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/inventory_coupon.py b/talon_one/models/inventory_coupon.py
index dd541de..56df19a 100644
--- a/talon_one/models/inventory_coupon.py
+++ b/talon_one/models/inventory_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class InventoryCoupon(BaseModel):
"""
@@ -56,7 +57,8 @@ class InventoryCoupon(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "campaignId", "value", "usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "usageCounter", "discountCounter", "discountRemainder", "reservationCounter", "attributes", "referralId", "recipientIntegrationId", "importId", "reservation", "batchId", "isReservationMandatory", "implicitlyReserved", "profileRedemptionCount", "state"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/inventory_referral.py b/talon_one/models/inventory_referral.py
index 037461d..aa12645 100644
--- a/talon_one/models/inventory_referral.py
+++ b/talon_one/models/inventory_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class InventoryReferral(BaseModel):
"""
@@ -45,7 +46,8 @@ class InventoryReferral(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "startDate", "expiryDate", "usageLimit", "campaignId", "advocateProfileIntegrationId", "friendProfileIntegrationId", "attributes", "importId", "code", "usageCounter", "batchId", "referredCustomers"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/item_attribute.py b/talon_one/models/item_attribute.py
index 417f671..65ce71c 100644
--- a/talon_one/models/item_attribute.py
+++ b/talon_one/models/item_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ItemAttribute(BaseModel):
"""
@@ -32,7 +33,8 @@ class ItemAttribute(BaseModel):
__properties: ClassVar[List[str]] = ["attributeid", "name", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/label_target_audience.py b/talon_one/models/label_target_audience.py
index fbd11fe..9b92be4 100644
--- a/talon_one/models/label_target_audience.py
+++ b/talon_one/models/label_target_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.audience_reference import AudienceReference
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LabelTargetAudience(BaseModel):
"""
@@ -39,7 +40,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/label_target_none.py b/talon_one/models/label_target_none.py
index 49417d8..865f310 100644
--- a/talon_one/models/label_target_none.py
+++ b/talon_one/models/label_target_none.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LabelTargetNone(BaseModel):
"""
@@ -37,7 +38,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/ledger_entry.py b/talon_one/models/ledger_entry.py
index bf57d6a..b78057d 100644
--- a/talon_one/models/ledger_entry.py
+++ b/talon_one/models/ledger_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LedgerEntry(BaseModel):
"""
@@ -40,7 +41,8 @@ class LedgerEntry(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "profileId", "accountId", "loyaltyProgramId", "eventId", "amount", "reason", "expiryDate", "referenceId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/ledger_info.py b/talon_one/models/ledger_info.py
index ad8c92e..ddd45c5 100644
--- a/talon_one/models/ledger_info.py
+++ b/talon_one/models/ledger_info.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.tier import Tier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LedgerInfo(BaseModel):
"""
@@ -40,7 +41,8 @@ class LedgerInfo(BaseModel):
__properties: ClassVar[List[str]] = ["currentBalance", "pendingBalance", "negativeBalance", "expiredBalance", "spentBalance", "tentativeCurrentBalance", "tentativePendingBalance", "tentativeNegativeBalance", "currentTier", "pointsToNextTier"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/ledger_points_entry_integration_api.py b/talon_one/models/ledger_points_entry_integration_api.py
index 0876c9f..aa29d2c 100644
--- a/talon_one/models/ledger_points_entry_integration_api.py
+++ b/talon_one/models/ledger_points_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LedgerPointsEntryIntegrationAPI(BaseModel):
"""
@@ -42,7 +43,8 @@ class LedgerPointsEntryIntegrationAPI(BaseModel):
__properties: ClassVar[List[str]] = ["id", "transactionUUID", "created", "programId", "customerSessionId", "name", "startDate", "expiryDate", "subledgerId", "amount", "validityDuration"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/ledger_transaction_log_entry_integration_api.py b/talon_one/models/ledger_transaction_log_entry_integration_api.py
index 75519df..1cd87c9 100644
--- a/talon_one/models/ledger_transaction_log_entry_integration_api.py
+++ b/talon_one/models/ledger_transaction_log_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.loyalty_ledger_entry_flags import LoyaltyLedgerEntryFlags
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LedgerTransactionLogEntryIntegrationAPI(BaseModel):
"""
@@ -54,7 +55,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -66,8 +68,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/library_attribute.py b/talon_one/models/library_attribute.py
index ced0f35..6d4d8f8 100644
--- a/talon_one/models/library_attribute.py
+++ b/talon_one/models/library_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LibraryAttribute(BaseModel):
"""
@@ -50,7 +51,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/limit_config.py b/talon_one/models/limit_config.py
index 6e20bce..e00d42f 100644
--- a/talon_one/models/limit_config.py
+++ b/talon_one/models/limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LimitConfig(BaseModel):
"""
@@ -52,7 +53,8 @@ def entities_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -64,8 +66,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/limit_counter.py b/talon_one/models/limit_counter.py
index 5aabad1..65d4d68 100644
--- a/talon_one/models/limit_counter.py
+++ b/talon_one/models/limit_counter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LimitCounter(BaseModel):
"""
@@ -45,7 +46,8 @@ class LimitCounter(BaseModel):
__properties: ClassVar[List[str]] = ["campaignId", "applicationId", "accountId", "id", "action", "profileId", "profileIntegrationId", "couponId", "couponValue", "referralId", "referralValue", "identifier", "period", "limit", "counter"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_account_collections200_response.py b/talon_one/models/list_account_collections200_response.py
index 8b2d0cb..98ba9d7 100644
--- a/talon_one/models/list_account_collections200_response.py
+++ b/talon_one/models/list_account_collections200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.collection_without_payload import CollectionWithoutPayload
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListAccountCollections200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class ListAccountCollections200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_achievements200_response.py b/talon_one/models/list_achievements200_response.py
index 2d2cfa0..884b61a 100644
--- a/talon_one/models/list_achievements200_response.py
+++ b/talon_one/models/list_achievements200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.achievement import Achievement
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListAchievements200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class ListAchievements200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_all_roles_v2200_response.py b/talon_one/models/list_all_roles_v2200_response.py
index bec087f..18f3774 100644
--- a/talon_one/models/list_all_roles_v2200_response.py
+++ b/talon_one/models/list_all_roles_v2200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.role_v2 import RoleV2
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListAllRolesV2200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class ListAllRolesV2200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_campaign_store_budget_limits200_response.py b/talon_one/models/list_campaign_store_budget_limits200_response.py
index 86260b9..5fb91fb 100644
--- a/talon_one/models/list_campaign_store_budget_limits200_response.py
+++ b/talon_one/models/list_campaign_store_budget_limits200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.list_campaign_store_budgets import ListCampaignStoreBudgets
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListCampaignStoreBudgetLimits200Response(BaseModel):
"""
@@ -31,7 +32,8 @@ class ListCampaignStoreBudgetLimits200Response(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_campaign_store_budgets.py b/talon_one/models/list_campaign_store_budgets.py
index 031b70d..0ba4b2c 100644
--- a/talon_one/models/list_campaign_store_budgets.py
+++ b/talon_one/models/list_campaign_store_budgets.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.list_campaign_store_budgets_store import ListCampaignStoreBudgetsStore
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListCampaignStoreBudgets(BaseModel):
"""
@@ -34,7 +35,8 @@ class ListCampaignStoreBudgets(BaseModel):
__properties: ClassVar[List[str]] = ["store", "limit", "action", "period"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_campaign_store_budgets_store.py b/talon_one/models/list_campaign_store_budgets_store.py
index c1795d7..51cf609 100644
--- a/talon_one/models/list_campaign_store_budgets_store.py
+++ b/talon_one/models/list_campaign_store_budgets_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListCampaignStoreBudgetsStore(BaseModel):
"""
@@ -32,7 +33,8 @@ class ListCampaignStoreBudgetsStore(BaseModel):
__properties: ClassVar[List[str]] = ["id", "integrationId", "name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_catalog_items200_response.py b/talon_one/models/list_catalog_items200_response.py
index 7e59ada..81616dd 100644
--- a/talon_one/models/list_catalog_items200_response.py
+++ b/talon_one/models/list_catalog_items200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.catalog_item import CatalogItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListCatalogItems200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class ListCatalogItems200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_experiments200_response.py b/talon_one/models/list_experiments200_response.py
index bd5cbae..e2bc17b 100644
--- a/talon_one/models/list_experiments200_response.py
+++ b/talon_one/models/list_experiments200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.experiment import Experiment
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListExperiments200Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class ListExperiments200Response(BaseModel):
__properties: ClassVar[List[str]] = ["totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/list_stores200_response.py b/talon_one/models/list_stores200_response.py
index d98af0b..0b3b804 100644
--- a/talon_one/models/list_stores200_response.py
+++ b/talon_one/models/list_stores200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.store import Store
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ListStores200Response(BaseModel):
"""
@@ -33,7 +34,8 @@ class ListStores200Response(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "totalResultSize", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/login_params.py b/talon_one/models/login_params.py
index adcc9ca..b87500e 100644
--- a/talon_one/models/login_params.py
+++ b/talon_one/models/login_params.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoginParams(BaseModel):
"""
@@ -31,7 +32,8 @@ class LoginParams(BaseModel):
__properties: ClassVar[List[str]] = ["email", "password"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty.py b/talon_one/models/loyalty.py
index a93c85a..29b67a6 100644
--- a/talon_one/models/loyalty.py
+++ b/talon_one/models/loyalty.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.loyalty_program_ledgers import LoyaltyProgramLedgers
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Loyalty(BaseModel):
"""
@@ -33,7 +34,8 @@ class Loyalty(BaseModel):
__properties: ClassVar[List[str]] = ["cards", "programs"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_balance.py b/talon_one/models/loyalty_balance.py
index f289256..bf1a5aa 100644
--- a/talon_one/models/loyalty_balance.py
+++ b/talon_one/models/loyalty_balance.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyBalance(BaseModel):
"""
@@ -34,7 +35,8 @@ class LoyaltyBalance(BaseModel):
__properties: ClassVar[List[str]] = ["activePoints", "pendingPoints", "spentPoints", "expiredPoints", "negativePoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_balance_with_tier.py b/talon_one/models/loyalty_balance_with_tier.py
index efdbab4..90597f9 100644
--- a/talon_one/models/loyalty_balance_with_tier.py
+++ b/talon_one/models/loyalty_balance_with_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.tier import Tier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyBalanceWithTier(BaseModel):
"""
@@ -40,7 +41,8 @@ class LoyaltyBalanceWithTier(BaseModel):
__properties: ClassVar[List[str]] = ["activePoints", "pendingPoints", "spentPoints", "expiredPoints", "negativePoints", "currentTier", "projectedTier", "pointsToNextTier", "nextTierName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_balances.py b/talon_one/models/loyalty_balances.py
index defd997..27ca9bb 100644
--- a/talon_one/models/loyalty_balances.py
+++ b/talon_one/models/loyalty_balances.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_balance import LoyaltyBalance
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyBalances(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyBalances(BaseModel):
__properties: ClassVar[List[str]] = ["balance", "subledgerBalances"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_balances_with_tiers.py b/talon_one/models/loyalty_balances_with_tiers.py
index b8859b4..edbb921 100644
--- a/talon_one/models/loyalty_balances_with_tiers.py
+++ b/talon_one/models/loyalty_balances_with_tiers.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_balance_with_tier import LoyaltyBalanceWithTier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyBalancesWithTiers(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyBalancesWithTiers(BaseModel):
__properties: ClassVar[List[str]] = ["balance", "subledgerBalances"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card.py b/talon_one/models/loyalty_card.py
index 0774d0b..33d3b81 100644
--- a/talon_one/models/loyalty_card.py
+++ b/talon_one/models/loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.loyalty_card_profile_registration import LoyaltyCardProfileRegistration
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCard(BaseModel):
"""
@@ -76,7 +77,8 @@ def new_card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -88,8 +90,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card_balances.py b/talon_one/models/loyalty_card_balances.py
index 75d257b..16a7af9 100644
--- a/talon_one/models/loyalty_card_balances.py
+++ b/talon_one/models/loyalty_card_balances.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.loyalty_card_profile_registration import LoyaltyCardProfileRegistration
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCardBalances(BaseModel):
"""
@@ -34,7 +35,8 @@ class LoyaltyCardBalances(BaseModel):
__properties: ClassVar[List[str]] = ["balance", "subledgerBalances", "profiles"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card_batch.py b/talon_one/models/loyalty_card_batch.py
index 2ef59dc..1d008de 100644
--- a/talon_one/models/loyalty_card_batch.py
+++ b/talon_one/models/loyalty_card_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.code_generator_settings import CodeGeneratorSettings
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCardBatch(BaseModel):
"""
@@ -55,7 +56,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card_batch_response.py b/talon_one/models/loyalty_card_batch_response.py
index 4868612..fe4ee5c 100644
--- a/talon_one/models/loyalty_card_batch_response.py
+++ b/talon_one/models/loyalty_card_batch_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCardBatchResponse(BaseModel):
"""
@@ -31,7 +32,8 @@ class LoyaltyCardBatchResponse(BaseModel):
__properties: ClassVar[List[str]] = ["numberOfCardsGenerated", "batchId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card_profile_registration.py b/talon_one/models/loyalty_card_profile_registration.py
index d6ef639..dbefef8 100644
--- a/talon_one/models/loyalty_card_profile_registration.py
+++ b/talon_one/models/loyalty_card_profile_registration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCardProfileRegistration(BaseModel):
"""
@@ -33,7 +34,8 @@ class LoyaltyCardProfileRegistration(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId", "timestamp"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_card_registration.py b/talon_one/models/loyalty_card_registration.py
index 66d91f2..1d37ce4 100644
--- a/talon_one/models/loyalty_card_registration.py
+++ b/talon_one/models/loyalty_card_registration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyCardRegistration(BaseModel):
"""
@@ -30,7 +31,8 @@ class LoyaltyCardRegistration(BaseModel):
__properties: ClassVar[List[str]] = ["integrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_dashboard_data.py b/talon_one/models/loyalty_dashboard_data.py
index c3fcd27..40fb0dc 100644
--- a/talon_one/models/loyalty_dashboard_data.py
+++ b/talon_one/models/loyalty_dashboard_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.loyalty_dashboard_points_breakdown import LoyaltyDashboardPointsBreakdown
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyDashboardData(BaseModel):
"""
@@ -41,7 +42,8 @@ class LoyaltyDashboardData(BaseModel):
__properties: ClassVar[List[str]] = ["date", "totalActivePoints", "totalPendingPoints", "totalSpentPoints", "totalExpiredPoints", "totalNegativePoints", "totalMembers", "newMembers", "spentPoints", "earnedPoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_dashboard_points_breakdown.py b/talon_one/models/loyalty_dashboard_points_breakdown.py
index 58e9b7c..20a20a0 100644
--- a/talon_one/models/loyalty_dashboard_points_breakdown.py
+++ b/talon_one/models/loyalty_dashboard_points_breakdown.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyDashboardPointsBreakdown(BaseModel):
"""
@@ -31,7 +32,8 @@ class LoyaltyDashboardPointsBreakdown(BaseModel):
__properties: ClassVar[List[str]] = ["createdManually", "createdViaRuleEngine"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_ledger.py b/talon_one/models/loyalty_ledger.py
index 7ee933b..d0e087f 100644
--- a/talon_one/models/loyalty_ledger.py
+++ b/talon_one/models/loyalty_ledger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_sub_ledger import LoyaltySubLedger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyLedger(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyLedger(BaseModel):
__properties: ClassVar[List[str]] = ["ledger", "subLedgers"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_ledger_entry.py b/talon_one/models/loyalty_ledger_entry.py
index 3c9ea81..8fb50b6 100644
--- a/talon_one/models/loyalty_ledger_entry.py
+++ b/talon_one/models/loyalty_ledger_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.loyalty_ledger_entry_flags import LoyaltyLedgerEntryFlags
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyLedgerEntry(BaseModel):
"""
@@ -47,7 +48,8 @@ class LoyaltyLedgerEntry(BaseModel):
__properties: ClassVar[List[str]] = ["created", "programID", "customerProfileID", "cardID", "customerSessionID", "eventID", "type", "amount", "startDate", "expiryDate", "name", "subLedgerID", "userID", "archived", "flags", "validityDuration"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_ledger_entry_expiry_date_change.py b/talon_one/models/loyalty_ledger_entry_expiry_date_change.py
index 786ac76..5b588f8 100644
--- a/talon_one/models/loyalty_ledger_entry_expiry_date_change.py
+++ b/talon_one/models/loyalty_ledger_entry_expiry_date_change.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyLedgerEntryExpiryDateChange(BaseModel):
"""
@@ -34,7 +35,8 @@ class LoyaltyLedgerEntryExpiryDateChange(BaseModel):
__properties: ClassVar[List[str]] = ["transactionUUID", "previousExpiryDate", "newExpiryDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_ledger_entry_flags.py b/talon_one/models/loyalty_ledger_entry_flags.py
index 6291567..b443e7d 100644
--- a/talon_one/models/loyalty_ledger_entry_flags.py
+++ b/talon_one/models/loyalty_ledger_entry_flags.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyLedgerEntryFlags(BaseModel):
"""
@@ -30,7 +31,8 @@ class LoyaltyLedgerEntryFlags(BaseModel):
__properties: ClassVar[List[str]] = ["createsNegativeBalance"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_ledger_transactions.py b/talon_one/models/loyalty_ledger_transactions.py
index 71673e7..0135649 100644
--- a/talon_one/models/loyalty_ledger_transactions.py
+++ b/talon_one/models/loyalty_ledger_transactions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.loyalty_ledger_entry import LoyaltyLedgerEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyLedgerTransactions(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyLedgerTransactions(BaseModel):
__properties: ClassVar[List[str]] = ["hasMore", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_membership.py b/talon_one/models/loyalty_membership.py
index 4097ddf..58242e9 100644
--- a/talon_one/models/loyalty_membership.py
+++ b/talon_one/models/loyalty_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyMembership(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyMembership(BaseModel):
__properties: ClassVar[List[str]] = ["joined", "loyaltyProgramId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_program.py b/talon_one/models/loyalty_program.py
index 1679635..608903b 100644
--- a/talon_one/models/loyalty_program.py
+++ b/talon_one/models/loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.loyalty_tier import LoyaltyTier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyProgram(BaseModel):
"""
@@ -99,7 +100,8 @@ def return_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -111,8 +113,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_program_balance.py b/talon_one/models/loyalty_program_balance.py
index 42c595d..c7e2305 100644
--- a/talon_one/models/loyalty_program_balance.py
+++ b/talon_one/models/loyalty_program_balance.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyProgramBalance(BaseModel):
"""
@@ -37,7 +38,8 @@ class LoyaltyProgramBalance(BaseModel):
__properties: ClassVar[List[str]] = ["currentBalance", "pendingBalance", "negativeBalance", "expiredBalance", "spentBalance", "tentativeCurrentBalance", "tentativePendingBalance", "tentativeNegativeBalance"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_program_entity.py b/talon_one/models/loyalty_program_entity.py
index 28a79fb..d582640 100644
--- a/talon_one/models/loyalty_program_entity.py
+++ b/talon_one/models/loyalty_program_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyProgramEntity(BaseModel):
"""
@@ -32,7 +33,8 @@ class LoyaltyProgramEntity(BaseModel):
__properties: ClassVar[List[str]] = ["programID", "programName", "programTitle"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_program_ledgers.py b/talon_one/models/loyalty_program_ledgers.py
index 6111c01..55014f4 100644
--- a/talon_one/models/loyalty_program_ledgers.py
+++ b/talon_one/models/loyalty_program_ledgers.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.ledger_info import LedgerInfo
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyProgramLedgers(BaseModel):
"""
@@ -37,7 +38,8 @@ class LoyaltyProgramLedgers(BaseModel):
__properties: ClassVar[List[str]] = ["id", "title", "name", "joinDate", "ledger", "subLedgers"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_program_transaction.py b/talon_one/models/loyalty_program_transaction.py
index d98e0e8..c606a2e 100644
--- a/talon_one/models/loyalty_program_transaction.py
+++ b/talon_one/models/loyalty_program_transaction.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.loyalty_ledger_entry_flags import LoyaltyLedgerEntryFlags
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyProgramTransaction(BaseModel):
"""
@@ -70,7 +71,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -82,8 +84,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_sub_ledger.py b/talon_one/models/loyalty_sub_ledger.py
index 1ce653b..f251a97 100644
--- a/talon_one/models/loyalty_sub_ledger.py
+++ b/talon_one/models/loyalty_sub_ledger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.tier import Tier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltySubLedger(BaseModel):
"""
@@ -43,7 +44,8 @@ class LoyaltySubLedger(BaseModel):
__properties: ClassVar[List[str]] = ["total", "totalActivePoints", "totalPendingPoints", "totalSpentPoints", "totalExpiredPoints", "totalNegativePoints", "transactions", "expiringPoints", "activePoints", "pendingPoints", "expiredPoints", "currentTier"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/loyalty_tier.py b/talon_one/models/loyalty_tier.py
index 01324fc..45c3db7 100644
--- a/talon_one/models/loyalty_tier.py
+++ b/talon_one/models/loyalty_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class LoyaltyTier(BaseModel):
"""
@@ -38,7 +39,8 @@ class LoyaltyTier(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "programID", "programName", "programTitle", "name", "minPoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/management_key.py b/talon_one/models/management_key.py
index 035992d..72473db 100644
--- a/talon_one/models/management_key.py
+++ b/talon_one/models/management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.endpoint import Endpoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ManagementKey(BaseModel):
"""
@@ -41,7 +42,8 @@ class ManagementKey(BaseModel):
__properties: ClassVar[List[str]] = ["name", "expiryDate", "endpoints", "allowedApplicationIds", "id", "createdBy", "accountID", "created", "disabled", "lastUsed"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/manager_config.py b/talon_one/models/manager_config.py
index 9fb5186..a5159af 100644
--- a/talon_one/models/manager_config.py
+++ b/talon_one/models/manager_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ManagerConfig(BaseModel):
"""
@@ -30,7 +31,8 @@ class ManagerConfig(BaseModel):
__properties: ClassVar[List[str]] = ["schemaVersion"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/message_log_entries.py b/talon_one/models/message_log_entries.py
index 91b5074..49c919e 100644
--- a/talon_one/models/message_log_entries.py
+++ b/talon_one/models/message_log_entries.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.message_log_entry import MessageLogEntry
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MessageLogEntries(BaseModel):
"""
@@ -32,7 +33,8 @@ class MessageLogEntries(BaseModel):
__properties: ClassVar[List[str]] = ["nextCursor", "data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/message_log_entry.py b/talon_one/models/message_log_entry.py
index 77100dc..920abda 100644
--- a/talon_one/models/message_log_entry.py
+++ b/talon_one/models/message_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.message_log_response import MessageLogResponse
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MessageLogEntry(BaseModel):
"""
@@ -55,7 +56,8 @@ def entity_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/message_log_request.py b/talon_one/models/message_log_request.py
index 31d3675..a72f694 100644
--- a/talon_one/models/message_log_request.py
+++ b/talon_one/models/message_log_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MessageLogRequest(BaseModel):
"""
@@ -32,7 +33,8 @@ class MessageLogRequest(BaseModel):
__properties: ClassVar[List[str]] = ["createdAt", "request"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/message_log_response.py b/talon_one/models/message_log_response.py
index 560cb3f..7d97180 100644
--- a/talon_one/models/message_log_response.py
+++ b/talon_one/models/message_log_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MessageLogResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class MessageLogResponse(BaseModel):
__properties: ClassVar[List[str]] = ["createdAt", "response", "status"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/message_test.py b/talon_one/models/message_test.py
index 70a5cd2..2cd9d22 100644
--- a/talon_one/models/message_test.py
+++ b/talon_one/models/message_test.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MessageTest(BaseModel):
"""
@@ -31,7 +32,8 @@ class MessageTest(BaseModel):
__properties: ClassVar[List[str]] = ["httpResponse", "httpStatus"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/meta.py b/talon_one/models/meta.py
index a317cc0..54fbf69 100644
--- a/talon_one/models/meta.py
+++ b/talon_one/models/meta.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.referral_rejection_reason import ReferralRejectionReason
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Meta(BaseModel):
"""
@@ -36,7 +37,8 @@ class Meta(BaseModel):
__properties: ClassVar[List[str]] = ["campaigns", "coupons", "couponRejectionReason", "referralRejectionReason", "warnings"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/model_import.py b/talon_one/models/model_import.py
index 0be92e1..25ad141 100644
--- a/talon_one/models/model_import.py
+++ b/talon_one/models/model_import.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ModelImport(BaseModel):
"""
@@ -37,7 +38,8 @@ class ModelImport(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "accountId", "userId", "entity", "amount"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -49,8 +51,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/model_return.py b/talon_one/models/model_return.py
index 05834fb..e3dca7a 100644
--- a/talon_one/models/model_return.py
+++ b/talon_one/models/model_return.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.returned_cart_item import ReturnedCartItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ModelReturn(BaseModel):
"""
@@ -43,7 +44,8 @@ class ModelReturn(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "accountId", "returnedCartItems", "eventId", "sessionId", "sessionIntegrationId", "profileId", "profileIntegrationId", "createdBy"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multi_application_entity.py b/talon_one/models/multi_application_entity.py
index 70ad24a..7a40fef 100644
--- a/talon_one/models/multi_application_entity.py
+++ b/talon_one/models/multi_application_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultiApplicationEntity(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultiApplicationEntity(BaseModel):
__properties: ClassVar[List[str]] = ["applicationIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_attribute.py b/talon_one/models/multiple_attribute.py
index b98fe1e..03fdff1 100644
--- a/talon_one/models/multiple_attribute.py
+++ b/talon_one/models/multiple_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.attribute import Attribute
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleAttribute(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultipleAttribute(BaseModel):
__properties: ClassVar[List[str]] = ["attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_audiences.py b/talon_one/models/multiple_audiences.py
index 4fea67d..7b310b9 100644
--- a/talon_one/models/multiple_audiences.py
+++ b/talon_one/models/multiple_audiences.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.multiple_audiences_item import MultipleAudiencesItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleAudiences(BaseModel):
"""
@@ -32,7 +33,8 @@ class MultipleAudiences(BaseModel):
__properties: ClassVar[List[str]] = ["accountId", "audiences"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_audiences_item.py b/talon_one/models/multiple_audiences_item.py
index cab8421..34257da 100644
--- a/talon_one/models/multiple_audiences_item.py
+++ b/talon_one/models/multiple_audiences_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleAudiencesItem(BaseModel):
"""
@@ -43,7 +44,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_customer_profile_integration_request.py b/talon_one/models/multiple_customer_profile_integration_request.py
index 5f90059..d664d08 100644
--- a/talon_one/models/multiple_customer_profile_integration_request.py
+++ b/talon_one/models/multiple_customer_profile_integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.multiple_customer_profile_integration_request_item import MultipleCustomerProfileIntegrationRequestItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleCustomerProfileIntegrationRequest(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultipleCustomerProfileIntegrationRequest(BaseModel):
__properties: ClassVar[List[str]] = ["customerProfiles"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_customer_profile_integration_request_item.py b/talon_one/models/multiple_customer_profile_integration_request_item.py
index 0233bce..b799f1f 100644
--- a/talon_one/models/multiple_customer_profile_integration_request_item.py
+++ b/talon_one/models/multiple_customer_profile_integration_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,17 +22,19 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleCustomerProfileIntegrationRequestItem(BaseModel):
"""
MultipleCustomerProfileIntegrationRequestItem
""" # noqa: E501
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this item.")
- integration_id: Annotated[str, Field(strict=True, max_length=1000)] = Field(description="The identifier of this profile, set by your integration layer. It must be unique within the account. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2). ", alias="integrationId")
+ integration_id: Annotated[str, Field(strict=True, max_length=1000)] = Field(description="The identifier of this profile, set by your integration layer. It must be unique within the account. To get the `integrationId` of the profile from a `sessionId`, use the [Update customer session](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2). ", alias="integrationId")
__properties: ClassVar[List[str]] = ["attributes", "integrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_customer_profile_integration_response_v2.py b/talon_one/models/multiple_customer_profile_integration_response_v2.py
index b1f21e9..31a84bc 100644
--- a/talon_one/models/multiple_customer_profile_integration_response_v2.py
+++ b/talon_one/models/multiple_customer_profile_integration_response_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.customer_profile_update_v2_response import CustomerProfileUpdateV2Response
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleCustomerProfileIntegrationResponseV2(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultipleCustomerProfileIntegrationResponseV2(BaseModel):
__properties: ClassVar[List[str]] = ["integrationStates"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_new_attribute.py b/talon_one/models/multiple_new_attribute.py
index d164fe8..dfbe7f5 100644
--- a/talon_one/models/multiple_new_attribute.py
+++ b/talon_one/models/multiple_new_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_attribute import NewAttribute
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleNewAttribute(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultipleNewAttribute(BaseModel):
__properties: ClassVar[List[str]] = ["attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/multiple_new_audiences.py b/talon_one/models/multiple_new_audiences.py
index fc290d2..f71f02f 100644
--- a/talon_one/models/multiple_new_audiences.py
+++ b/talon_one/models/multiple_new_audiences.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_multiple_audiences_item import NewMultipleAudiencesItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MultipleNewAudiences(BaseModel):
"""
@@ -31,7 +32,8 @@ class MultipleNewAudiences(BaseModel):
__properties: ClassVar[List[str]] = ["audiences"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/mutable_entity.py b/talon_one/models/mutable_entity.py
index 86948bd..1dbe0df 100644
--- a/talon_one/models/mutable_entity.py
+++ b/talon_one/models/mutable_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class MutableEntity(BaseModel):
"""
@@ -31,7 +32,8 @@ class MutableEntity(BaseModel):
__properties: ClassVar[List[str]] = ["modified"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_account.py b/talon_one/models/new_account.py
index 21007ca..c949992 100644
--- a/talon_one/models/new_account.py
+++ b/talon_one/models/new_account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAccount(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewAccount(BaseModel):
__properties: ClassVar[List[str]] = ["companyName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_account_sign_up.py b/talon_one/models/new_account_sign_up.py
index 16e2e2a..18143d9 100644
--- a/talon_one/models/new_account_sign_up.py
+++ b/talon_one/models/new_account_sign_up.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAccountSignUp(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewAccountSignUp(BaseModel):
__properties: ClassVar[List[str]] = ["email", "password", "companyName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_additional_cost.py b/talon_one/models/new_additional_cost.py
index d48f895..f9b7860 100644
--- a/talon_one/models/new_additional_cost.py
+++ b/talon_one/models/new_additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAdditionalCost(BaseModel):
"""
@@ -59,7 +60,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -71,8 +73,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_app_wide_coupon_deletion_job.py b/talon_one/models/new_app_wide_coupon_deletion_job.py
index 58fe951..f22ffb6 100644
--- a/talon_one/models/new_app_wide_coupon_deletion_job.py
+++ b/talon_one/models/new_app_wide_coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.coupon_deletion_filters import CouponDeletionFilters
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAppWideCouponDeletionJob(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewAppWideCouponDeletionJob(BaseModel):
__properties: ClassVar[List[str]] = ["filters", "campaignids"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_application.py b/talon_one/models/new_application.py
index 4a24694..4fef8b5 100644
--- a/talon_one/models/new_application.py
+++ b/talon_one/models/new_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewApplication(BaseModel):
"""
@@ -88,7 +89,8 @@ def key_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -100,8 +102,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_application_api_key.py b/talon_one/models/new_application_api_key.py
index 939a72f..b32ecde 100644
--- a/talon_one/models/new_application_api_key.py
+++ b/talon_one/models/new_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewApplicationAPIKey(BaseModel):
"""
@@ -61,7 +62,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -73,8 +75,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_application_cif.py b/talon_one/models/new_application_cif.py
index 31f5285..52975a2 100644
--- a/talon_one/models/new_application_cif.py
+++ b/talon_one/models/new_application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewApplicationCIF(BaseModel):
"""
@@ -36,7 +37,8 @@ class NewApplicationCIF(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "activeExpressionId", "modifiedBy", "createdBy", "modified"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_application_cif_expression.py b/talon_one/models/new_application_cif_expression.py
index 4c0803f..5d13ea7 100644
--- a/talon_one/models/new_application_cif_expression.py
+++ b/talon_one/models/new_application_cif_expression.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewApplicationCIFExpression(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewApplicationCIFExpression(BaseModel):
__properties: ClassVar[List[str]] = ["cartItemFilterId", "createdBy", "expression"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_attribute.py b/talon_one/models/new_attribute.py
index 219b1f1..2ce87b7 100644
--- a/talon_one/models/new_attribute.py
+++ b/talon_one/models/new_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAttribute(BaseModel):
"""
@@ -82,7 +83,8 @@ def allowed_subscriptions_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -94,8 +96,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_audience.py b/talon_one/models/new_audience.py
index 29b42fb..34cf533 100644
--- a/talon_one/models/new_audience.py
+++ b/talon_one/models/new_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewAudience(BaseModel):
"""
@@ -38,7 +39,8 @@ class NewAudience(BaseModel):
__properties: ClassVar[List[str]] = ["name", "sandbox", "description", "integration", "integrationId", "createdIn3rdParty", "lastUpdate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_base_notification.py b/talon_one/models/new_base_notification.py
index 43e344c..f376f8e 100644
--- a/talon_one/models/new_base_notification.py
+++ b/talon_one/models/new_base_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_notification_webhook import NewNotificationWebhook
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewBaseNotification(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewBaseNotification(BaseModel):
__properties: ClassVar[List[str]] = ["policy", "enabled", "webhook"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_blueprint.py b/talon_one/models/new_blueprint.py
index ab6a1f6..fc0cd2f 100644
--- a/talon_one/models/new_blueprint.py
+++ b/talon_one/models/new_blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.catalog_rule import CatalogRule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewBlueprint(BaseModel):
"""
@@ -46,7 +47,8 @@ def category_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign.py b/talon_one/models/new_campaign.py
index 579f0d4..1418073 100644
--- a/talon_one/models/new_campaign.py
+++ b/talon_one/models/new_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaign(BaseModel):
"""
@@ -36,7 +37,7 @@ class NewCampaign(BaseModel):
end_time: Optional[datetime] = Field(default=None, description="Timestamp when the campaign will become inactive.", alias="endTime")
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this campaign.")
state: StrictStr = Field(description="A disabled or archived campaign is not evaluated for rules or coupons. ")
- active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
+ active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
tags: Annotated[List[Annotated[str, Field(min_length=1, strict=True, max_length=50)]], Field(max_length=50)] = Field(description="A list of tags for the campaign.")
reevaluate_on_return: Optional[StrictBool] = Field(default=None, description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: List[StrictStr] = Field(description="The features enabled in this campaign.")
@@ -46,8 +47,9 @@ class NewCampaign(BaseModel):
campaign_groups: Optional[List[StrictInt]] = Field(default=None, description="The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/managing-campaign-groups) this campaign belongs to. ", alias="campaignGroups")
type: Optional[StrictStr] = Field(default='advanced', description="The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. ")
linked_store_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of store IDs that you want to link to the campaign. **Note:** Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. ", alias="linkedStoreIds")
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
evaluation_group_id: Optional[StrictInt] = Field(default=None, description="The ID of the campaign evaluation group the campaign belongs to.", alias="evaluationGroupId")
- __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds", "evaluationGroupId"]
+ __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "type", "linkedStoreIds", "couponAttributes", "evaluationGroupId"]
@field_validator('state')
def state_validate_enum(cls, value):
@@ -75,7 +77,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -87,8 +90,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -154,6 +156,7 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"campaignGroups": obj.get("campaignGroups"),
"type": obj.get("type") if obj.get("type") is not None else 'advanced',
"linkedStoreIds": obj.get("linkedStoreIds"),
+ "couponAttributes": obj.get("couponAttributes"),
"evaluationGroupId": obj.get("evaluationGroupId")
})
return _obj
diff --git a/talon_one/models/new_campaign_collection.py b/talon_one/models/new_campaign_collection.py
index 58782eb..622b704 100644
--- a/talon_one/models/new_campaign_collection.py
+++ b/talon_one/models/new_campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignCollection(BaseModel):
"""
@@ -39,7 +40,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_evaluation_group.py b/talon_one/models/new_campaign_evaluation_group.py
index 78953ea..d8046d9 100644
--- a/talon_one/models/new_campaign_evaluation_group.py
+++ b/talon_one/models/new_campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignEvaluationGroup(BaseModel):
"""
@@ -50,7 +51,8 @@ def evaluation_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_group.py b/talon_one/models/new_campaign_group.py
index 450bb70..85c089a 100644
--- a/talon_one/models/new_campaign_group.py
+++ b/talon_one/models/new_campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignGroup(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewCampaignGroup(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "subscribedApplicationsIds", "campaignIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_set.py b/talon_one/models/new_campaign_set.py
index b4f4d25..9ab432c 100644
--- a/talon_one/models/new_campaign_set.py
+++ b/talon_one/models/new_campaign_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.campaign_set_branch_node import CampaignSetBranchNode
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignSet(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewCampaignSet(BaseModel):
__properties: ClassVar[List[str]] = ["applicationId", "version", "set"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_store_budget.py b/talon_one/models/new_campaign_store_budget.py
index 6d618c2..d70059c 100644
--- a/talon_one/models/new_campaign_store_budget.py
+++ b/talon_one/models/new_campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_campaign_store_budget_store_limit import NewCampaignStoreBudgetStoreLimit
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignStoreBudget(BaseModel):
"""
@@ -50,7 +51,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_store_budget_store_limit.py b/talon_one/models/new_campaign_store_budget_store_limit.py
index f507ff5..14cf808 100644
--- a/talon_one/models/new_campaign_store_budget_store_limit.py
+++ b/talon_one/models/new_campaign_store_budget_store_limit.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignStoreBudgetStoreLimit(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewCampaignStoreBudgetStoreLimit(BaseModel):
__properties: ClassVar[List[str]] = ["storeId", "limit"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_campaign_template.py b/talon_one/models/new_campaign_template.py
index 31c8e83..27d65b5 100644
--- a/talon_one/models/new_campaign_template.py
+++ b/talon_one/models/new_campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -27,6 +27,7 @@
from talon_one.models.template_limit_config import TemplateLimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCampaignTemplate(BaseModel):
"""
@@ -77,7 +78,8 @@ def campaign_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -89,8 +91,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_catalog.py b/talon_one/models/new_catalog.py
index 236e747..d2b83ab 100644
--- a/talon_one/models/new_catalog.py
+++ b/talon_one/models/new_catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCatalog(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewCatalog(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "subscribedApplicationsIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_collection.py b/talon_one/models/new_collection.py
index da45bdd..319ab7f 100644
--- a/talon_one/models/new_collection.py
+++ b/talon_one/models/new_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCollection(BaseModel):
"""
@@ -40,7 +41,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_coupon_creation_job.py b/talon_one/models/new_coupon_creation_job.py
index 6448697..72ca422 100644
--- a/talon_one/models/new_coupon_creation_job.py
+++ b/talon_one/models/new_coupon_creation_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.code_generator_settings import CodeGeneratorSettings
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCouponCreationJob(BaseModel):
"""
@@ -41,7 +42,8 @@ class NewCouponCreationJob(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "numberOfCoupons", "couponSettings", "attributes", "isReservationMandatory"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_coupon_deletion_job.py b/talon_one/models/new_coupon_deletion_job.py
index f5a3dc1..23edf30 100644
--- a/talon_one/models/new_coupon_deletion_job.py
+++ b/talon_one/models/new_coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.coupon_deletion_filters import CouponDeletionFilters
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCouponDeletionJob(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewCouponDeletionJob(BaseModel):
__properties: ClassVar[List[str]] = ["filters"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_coupons.py b/talon_one/models/new_coupons.py
index 557cf09..6165813 100644
--- a/talon_one/models/new_coupons.py
+++ b/talon_one/models/new_coupons.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCoupons(BaseModel):
"""
@@ -36,7 +37,7 @@ class NewCoupons(BaseModel):
expiry_date: Optional[datetime] = Field(default=None, description="Expiration date of the coupon. Coupon never expires if this is omitted.", alias="expiryDate")
limits: Optional[List[LimitConfig]] = Field(default=None, description="Limits configuration for a coupon. These limits will override the limits set from the campaign. **Note:** Only usable when creating a single coupon which is not tied to a specific recipient. Only per-profile limits are allowed to be configured. ")
number_of_coupons: StrictInt = Field(description="The number of new coupon codes to generate for the campaign. Must be at least 1.", alias="numberOfCoupons")
- unique_prefix: Optional[StrictStr] = Field(default=None, description="**DEPRECATED** To create more than 20,000 coupons in one request, use [Create coupons asynchronously](https://docs.talon.one/management-api#operation/createCouponsAsync) endpoint. ", alias="uniquePrefix")
+ unique_prefix: Optional[StrictStr] = Field(default=None, description="**DEPRECATED** To create more than 20,000 coupons in one request, use [Create coupons asynchronously](https://docs.talon.one/management-api#tag/Coupons/operation/createCouponsAsync) endpoint. ", alias="uniquePrefix")
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this item.")
recipient_integration_id: Optional[Annotated[str, Field(strict=True, max_length=1000)]] = Field(default=None, description="The integration ID for this coupon's beneficiary's profile.", alias="recipientIntegrationId")
valid_characters: Optional[List[StrictStr]] = Field(default=None, description="List of characters used to generate the random parts of a code. By default, the list of characters is equivalent to the `[A-Z, 0-9]` regular expression. ", alias="validCharacters")
@@ -46,7 +47,8 @@ class NewCoupons(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "numberOfCoupons", "uniquePrefix", "attributes", "recipientIntegrationId", "validCharacters", "couponPattern", "isReservationMandatory", "implicitlyReserved"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_coupons_for_multiple_recipients.py b/talon_one/models/new_coupons_for_multiple_recipients.py
index 55a9ba6..69d565c 100644
--- a/talon_one/models/new_coupons_for_multiple_recipients.py
+++ b/talon_one/models/new_coupons_for_multiple_recipients.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCouponsForMultipleRecipients(BaseModel):
"""
@@ -40,7 +41,8 @@ class NewCouponsForMultipleRecipients(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "attributes", "recipientsIntegrationIds", "validCharacters", "couponPattern"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_custom_effect.py b/talon_one/models/new_custom_effect.py
index 4d353eb..afa6623 100644
--- a/talon_one/models/new_custom_effect.py
+++ b/talon_one/models/new_custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCustomEffect(BaseModel):
"""
@@ -53,7 +54,8 @@ def title_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_customer_profile.py b/talon_one/models/new_customer_profile.py
index 41edb58..640943e 100644
--- a/talon_one/models/new_customer_profile.py
+++ b/talon_one/models/new_customer_profile.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCustomerProfile(BaseModel):
"""
@@ -30,7 +31,8 @@ class NewCustomerProfile(BaseModel):
__properties: ClassVar[List[str]] = ["attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_customer_session.py b/talon_one/models/new_customer_session.py
index d4cbdc9..fa5cccc 100644
--- a/talon_one/models/new_customer_session.py
+++ b/talon_one/models/new_customer_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.cart_item import CartItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCustomerSession(BaseModel):
"""
@@ -49,7 +50,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -61,8 +63,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_customer_session_v2.py b/talon_one/models/new_customer_session_v2.py
index 400d354..64ff1b0 100644
--- a/talon_one/models/new_customer_session_v2.py
+++ b/talon_one/models/new_customer_session_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.experiment_variant_allocation import ExperimentVariantAllocation
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewCustomerSessionV2(BaseModel):
"""
@@ -55,7 +56,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_event.py b/talon_one/models/new_event.py
index e83aec7..6a6f162 100644
--- a/talon_one/models/new_event.py
+++ b/talon_one/models/new_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewEvent(BaseModel):
"""
@@ -35,7 +36,8 @@ class NewEvent(BaseModel):
__properties: ClassVar[List[str]] = ["profileId", "storeIntegrationId", "type", "attributes", "sessionId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_event_type.py b/talon_one/models/new_event_type.py
index f1ef8b2..f6cccb0 100644
--- a/talon_one/models/new_event_type.py
+++ b/talon_one/models/new_event_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewEventType(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewEventType(BaseModel):
__properties: ClassVar[List[str]] = ["title", "name", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_experiment.py b/talon_one/models/new_experiment.py
index b2d2b47..6292543 100644
--- a/talon_one/models/new_experiment.py
+++ b/talon_one/models/new_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_campaign import NewCampaign
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewExperiment(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewExperiment(BaseModel):
__properties: ClassVar[List[str]] = ["isVariantAssignmentExternal", "campaign"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_experiment_variant.py b/talon_one/models/new_experiment_variant.py
index a21b063..52f2ca1 100644
--- a/talon_one/models/new_experiment_variant.py
+++ b/talon_one/models/new_experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.new_ruleset import NewRuleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewExperimentVariant(BaseModel):
"""
@@ -35,7 +36,8 @@ class NewExperimentVariant(BaseModel):
__properties: ClassVar[List[str]] = ["name", "weight", "ruleset", "isPrimary"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_experiment_variant_array.py b/talon_one/models/new_experiment_variant_array.py
index 6d2b01b..61ad8dd 100644
--- a/talon_one/models/new_experiment_variant_array.py
+++ b/talon_one/models/new_experiment_variant_array.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_experiment_variant import NewExperimentVariant
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewExperimentVariantArray(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewExperimentVariantArray(BaseModel):
__properties: ClassVar[List[str]] = ["variants"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_external_invitation.py b/talon_one/models/new_external_invitation.py
index 4041a19..50ddf73 100644
--- a/talon_one/models/new_external_invitation.py
+++ b/talon_one/models/new_external_invitation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewExternalInvitation(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewExternalInvitation(BaseModel):
__properties: ClassVar[List[str]] = ["name", "userGroups", "email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_giveaways_pool.py b/talon_one/models/new_giveaways_pool.py
index ec0d4e2..56c0ebc 100644
--- a/talon_one/models/new_giveaways_pool.py
+++ b/talon_one/models/new_giveaways_pool.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewGiveawaysPool(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewGiveawaysPool(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "subscribedApplicationsIds", "sandbox"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_internal_audience.py b/talon_one/models/new_internal_audience.py
index d6ab708..52942cc 100644
--- a/talon_one/models/new_internal_audience.py
+++ b/talon_one/models/new_internal_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewInternalAudience(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewInternalAudience(BaseModel):
__properties: ClassVar[List[str]] = ["name", "sandbox", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_invitation.py b/talon_one/models/new_invitation.py
index 47046df..81d4a92 100644
--- a/talon_one/models/new_invitation.py
+++ b/talon_one/models/new_invitation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewInvitation(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewInvitation(BaseModel):
__properties: ClassVar[List[str]] = ["name", "email", "isAdmin", "roles", "acl"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_invite_email.py b/talon_one/models/new_invite_email.py
index 7ea5fd4..c073f6d 100644
--- a/talon_one/models/new_invite_email.py
+++ b/talon_one/models/new_invite_email.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewInviteEmail(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewInviteEmail(BaseModel):
__properties: ClassVar[List[str]] = ["email", "token"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_loyalty_program.py b/talon_one/models/new_loyalty_program.py
index 461d0b0..cf2b961 100644
--- a/talon_one/models/new_loyalty_program.py
+++ b/talon_one/models/new_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.new_loyalty_tier import NewLoyaltyTier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewLoyaltyProgram(BaseModel):
"""
@@ -92,7 +93,8 @@ def return_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -104,8 +106,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_loyalty_tier.py b/talon_one/models/new_loyalty_tier.py
index 522decd..9f490fa 100644
--- a/talon_one/models/new_loyalty_tier.py
+++ b/talon_one/models/new_loyalty_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewLoyaltyTier(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewLoyaltyTier(BaseModel):
__properties: ClassVar[List[str]] = ["name", "minPoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_management_key.py b/talon_one/models/new_management_key.py
index 07367e4..14bf7c8 100644
--- a/talon_one/models/new_management_key.py
+++ b/talon_one/models/new_management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.endpoint import Endpoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewManagementKey(BaseModel):
"""
@@ -42,7 +43,8 @@ class NewManagementKey(BaseModel):
__properties: ClassVar[List[str]] = ["name", "expiryDate", "endpoints", "allowedApplicationIds", "id", "createdBy", "accountID", "created", "disabled", "lastUsed", "key"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_message_test.py b/talon_one/models/new_message_test.py
index a2482f1..f5e6476 100644
--- a/talon_one/models/new_message_test.py
+++ b/talon_one/models/new_message_test.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewMessageTest(BaseModel):
"""
@@ -44,7 +45,8 @@ def verb_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_multiple_audiences_item.py b/talon_one/models/new_multiple_audiences_item.py
index 4f29a9b..7245165 100644
--- a/talon_one/models/new_multiple_audiences_item.py
+++ b/talon_one/models/new_multiple_audiences_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewMultipleAudiencesItem(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewMultipleAudiencesItem(BaseModel):
__properties: ClassVar[List[str]] = ["name", "integrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_notification_webhook.py b/talon_one/models/new_notification_webhook.py
index 68116db..3d2fe1d 100644
--- a/talon_one/models/new_notification_webhook.py
+++ b/talon_one/models/new_notification_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewNotificationWebhook(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewNotificationWebhook(BaseModel):
__properties: ClassVar[List[str]] = ["url", "headers", "enabled"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_outgoing_integration_webhook.py b/talon_one/models/new_outgoing_integration_webhook.py
index 1c27050..b5973be 100644
--- a/talon_one/models/new_outgoing_integration_webhook.py
+++ b/talon_one/models/new_outgoing_integration_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewOutgoingIntegrationWebhook(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewOutgoingIntegrationWebhook(BaseModel):
__properties: ClassVar[List[str]] = ["title", "description", "applicationIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_password.py b/talon_one/models/new_password.py
index 46f8082..cb50572 100644
--- a/talon_one/models/new_password.py
+++ b/talon_one/models/new_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewPassword(BaseModel):
"""
@@ -32,7 +33,8 @@ class NewPassword(BaseModel):
__properties: ClassVar[List[str]] = ["password", "resetToken"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_password_email.py b/talon_one/models/new_password_email.py
index 193b173..e832c3f 100644
--- a/talon_one/models/new_password_email.py
+++ b/talon_one/models/new_password_email.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewPasswordEmail(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewPasswordEmail(BaseModel):
__properties: ClassVar[List[str]] = ["email"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_picklist.py b/talon_one/models/new_picklist.py
index ba07ae3..693a0b8 100644
--- a/talon_one/models/new_picklist.py
+++ b/talon_one/models/new_picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewPicklist(BaseModel):
"""
@@ -39,7 +40,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_price_adjustment.py b/talon_one/models/new_price_adjustment.py
index ce1e27a..bbba41f 100644
--- a/talon_one/models/new_price_adjustment.py
+++ b/talon_one/models/new_price_adjustment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewPriceAdjustment(BaseModel):
"""
@@ -38,7 +39,8 @@ class NewPriceAdjustment(BaseModel):
__properties: ClassVar[List[str]] = ["priceType", "price", "referenceId", "calculatedAt", "effectiveFrom", "effectiveUntil", "contextId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_price_type.py b/talon_one/models/new_price_type.py
index 9f250ca..4564fa8 100644
--- a/talon_one/models/new_price_type.py
+++ b/talon_one/models/new_price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewPriceType(BaseModel):
"""
@@ -41,7 +42,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_referral.py b/talon_one/models/new_referral.py
index fc07ec9..fe88eb4 100644
--- a/talon_one/models/new_referral.py
+++ b/talon_one/models/new_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewReferral(BaseModel):
"""
@@ -38,7 +39,8 @@ class NewReferral(BaseModel):
__properties: ClassVar[List[str]] = ["startDate", "expiryDate", "usageLimit", "campaignId", "advocateProfileIntegrationId", "friendProfileIntegrationId", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_referrals_for_multiple_advocates.py b/talon_one/models/new_referrals_for_multiple_advocates.py
index 621e831..fac1732 100644
--- a/talon_one/models/new_referrals_for_multiple_advocates.py
+++ b/talon_one/models/new_referrals_for_multiple_advocates.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewReferralsForMultipleAdvocates(BaseModel):
"""
@@ -39,7 +40,8 @@ class NewReferralsForMultipleAdvocates(BaseModel):
__properties: ClassVar[List[str]] = ["startDate", "expiryDate", "usageLimit", "campaignId", "advocateProfileIntegrationIds", "attributes", "validCharacters", "referralPattern"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_return.py b/talon_one/models/new_return.py
index 84f598f..b78a224 100644
--- a/talon_one/models/new_return.py
+++ b/talon_one/models/new_return.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.returned_cart_item import ReturnedCartItem
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewReturn(BaseModel):
"""
@@ -31,7 +32,8 @@ class NewReturn(BaseModel):
__properties: ClassVar[List[str]] = ["returnedCartItems"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_revision_version.py b/talon_one/models/new_revision_version.py
index 5c68f4f..1c2c6d8 100644
--- a/talon_one/models/new_revision_version.py
+++ b/talon_one/models/new_revision_version.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewRevisionVersion(BaseModel):
"""
@@ -42,7 +43,8 @@ class NewRevisionVersion(BaseModel):
limits: Optional[List[LimitConfig]] = Field(default=None, description="The set of limits that will operate for this campaign version.")
reevaluate_on_return: Optional[StrictBool] = Field(default=None, description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: Optional[List[StrictStr]] = Field(default=None, description="A list of features for the campaign.")
- __properties: ClassVar[List[str]] = ["name", "startTime", "endTime", "attributes", "description", "activeRulesetId", "tags", "couponSettings", "referralSettings", "limits", "reevaluateOnReturn", "features"]
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
+ __properties: ClassVar[List[str]] = ["name", "startTime", "endTime", "attributes", "description", "activeRulesetId", "tags", "couponSettings", "referralSettings", "limits", "reevaluateOnReturn", "features", "couponAttributes"]
@field_validator('features')
def features_validate_enum(cls, value):
@@ -56,7 +58,8 @@ def features_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +71,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -150,7 +152,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"referralSettings": CodeGeneratorSettings.from_dict(obj["referralSettings"]) if obj.get("referralSettings") is not None else None,
"limits": [LimitConfig.from_dict(_item) for _item in obj["limits"]] if obj.get("limits") is not None else None,
"reevaluateOnReturn": obj.get("reevaluateOnReturn"),
- "features": obj.get("features")
+ "features": obj.get("features"),
+ "couponAttributes": obj.get("couponAttributes")
})
return _obj
diff --git a/talon_one/models/new_role.py b/talon_one/models/new_role.py
index eff9fa7..a5cf5a2 100644
--- a/talon_one/models/new_role.py
+++ b/talon_one/models/new_role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewRole(BaseModel):
"""
@@ -33,7 +34,8 @@ class NewRole(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "acl", "members"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_role_v2.py b/talon_one/models/new_role_v2.py
index af808e9..13f57f4 100644
--- a/talon_one/models/new_role_v2.py
+++ b/talon_one/models/new_role_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.role_v2_permissions import RoleV2Permissions
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewRoleV2(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewRoleV2(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "permissions", "members"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_ruleset.py b/talon_one/models/new_ruleset.py
index 5c7bdd3..c58823d 100644
--- a/talon_one/models/new_ruleset.py
+++ b/talon_one/models/new_ruleset.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.rule import Rule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewRuleset(BaseModel):
"""
@@ -36,7 +37,8 @@ class NewRuleset(BaseModel):
__properties: ClassVar[List[str]] = ["rules", "strikethroughRules", "bindings", "rbVersion", "activate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_saml_connection.py b/talon_one/models/new_saml_connection.py
index e83dbf7..7973705 100644
--- a/talon_one/models/new_saml_connection.py
+++ b/talon_one/models/new_saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewSamlConnection(BaseModel):
"""
@@ -39,7 +40,8 @@ class NewSamlConnection(BaseModel):
__properties: ClassVar[List[str]] = ["accountId", "name", "enabled", "issuer", "signOnURL", "signOutURL", "metadataURL", "audienceURI", "x509certificate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_secondary_deployment.py b/talon_one/models/new_secondary_deployment.py
index 58c0d72..afc6ae3 100644
--- a/talon_one/models/new_secondary_deployment.py
+++ b/talon_one/models/new_secondary_deployment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewSecondaryDeployment(BaseModel):
"""
@@ -38,7 +39,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_store.py b/talon_one/models/new_store.py
index 01de29d..51fb4cb 100644
--- a/talon_one/models/new_store.py
+++ b/talon_one/models/new_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewStore(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewStore(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "attributes", "integrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_template_def.py b/talon_one/models/new_template_def.py
index 949d69f..10c4e2d 100644
--- a/talon_one/models/new_template_def.py
+++ b/talon_one/models/new_template_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewTemplateDef(BaseModel):
"""
@@ -38,7 +39,8 @@ class NewTemplateDef(BaseModel):
__properties: ClassVar[List[str]] = ["title", "description", "help", "category", "expr", "args", "expose"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_user.py b/talon_one/models/new_user.py
index 28698bc..53ea88f 100644
--- a/talon_one/models/new_user.py
+++ b/talon_one/models/new_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewUser(BaseModel):
"""
@@ -34,7 +35,8 @@ class NewUser(BaseModel):
__properties: ClassVar[List[str]] = ["email", "password", "name", "inviteToken"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/new_webhook.py b/talon_one/models/new_webhook.py
index a412f58..6852b84 100644
--- a/talon_one/models/new_webhook.py
+++ b/talon_one/models/new_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NewWebhook(BaseModel):
"""
@@ -56,7 +57,8 @@ def verb_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -68,8 +70,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/notification.py b/talon_one/models/notification.py
index 0a73ded..28c9bec 100644
--- a/talon_one/models/notification.py
+++ b/talon_one/models/notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Notification(BaseModel):
"""
@@ -32,7 +33,8 @@ class Notification(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/notification_activation.py b/talon_one/models/notification_activation.py
index f86c9b7..d3cafd9 100644
--- a/talon_one/models/notification_activation.py
+++ b/talon_one/models/notification_activation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NotificationActivation(BaseModel):
"""
@@ -30,7 +31,8 @@ class NotificationActivation(BaseModel):
__properties: ClassVar[List[str]] = ["enabled"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/notification_list_item.py b/talon_one/models/notification_list_item.py
index 1d9ed9b..2894a09 100644
--- a/talon_one/models/notification_list_item.py
+++ b/talon_one/models/notification_list_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class NotificationListItem(BaseModel):
"""
@@ -33,7 +34,8 @@ class NotificationListItem(BaseModel):
__properties: ClassVar[List[str]] = ["notificationId", "notificationName", "entityId", "enabled"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/okta_event.py b/talon_one/models/okta_event.py
index 5c62480..c6d3ffa 100644
--- a/talon_one/models/okta_event.py
+++ b/talon_one/models/okta_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.okta_event_target import OktaEventTarget
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OktaEvent(BaseModel):
"""
@@ -32,7 +33,8 @@ class OktaEvent(BaseModel):
__properties: ClassVar[List[str]] = ["eventType", "target"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/okta_event_payload.py b/talon_one/models/okta_event_payload.py
index 9e059f6..c625e0f 100644
--- a/talon_one/models/okta_event_payload.py
+++ b/talon_one/models/okta_event_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.okta_event_payload_data import OktaEventPayloadData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OktaEventPayload(BaseModel):
"""
@@ -31,7 +32,8 @@ class OktaEventPayload(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/okta_event_payload_data.py b/talon_one/models/okta_event_payload_data.py
index 068fa39..81be90a 100644
--- a/talon_one/models/okta_event_payload_data.py
+++ b/talon_one/models/okta_event_payload_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.okta_event import OktaEvent
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OktaEventPayloadData(BaseModel):
"""
@@ -31,7 +32,8 @@ class OktaEventPayloadData(BaseModel):
__properties: ClassVar[List[str]] = ["events"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/okta_event_target.py b/talon_one/models/okta_event_target.py
index f970cd8..1ad1524 100644
--- a/talon_one/models/okta_event_target.py
+++ b/talon_one/models/okta_event_target.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OktaEventTarget(BaseModel):
"""
@@ -32,7 +33,8 @@ class OktaEventTarget(BaseModel):
__properties: ClassVar[List[str]] = ["type", "alternateId", "displayName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/one_time_code.py b/talon_one/models/one_time_code.py
index 4f32886..f7f80a1 100644
--- a/talon_one/models/one_time_code.py
+++ b/talon_one/models/one_time_code.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OneTimeCode(BaseModel):
"""
@@ -33,7 +34,8 @@ class OneTimeCode(BaseModel):
__properties: ClassVar[List[str]] = ["userId", "accountId", "token", "code"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_braze_policy.py b/talon_one/models/outgoing_integration_braze_policy.py
index 7f4add7..083e744 100644
--- a/talon_one/models/outgoing_integration_braze_policy.py
+++ b/talon_one/models/outgoing_integration_braze_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationBrazePolicy(BaseModel):
"""
@@ -31,7 +32,8 @@ class OutgoingIntegrationBrazePolicy(BaseModel):
__properties: ClassVar[List[str]] = ["baseUrl", "apiKey"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_clever_tap_policy.py b/talon_one/models/outgoing_integration_clever_tap_policy.py
index 6f3ab45..d8b4754 100644
--- a/talon_one/models/outgoing_integration_clever_tap_policy.py
+++ b/talon_one/models/outgoing_integration_clever_tap_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationCleverTapPolicy(BaseModel):
"""
@@ -32,7 +33,8 @@ class OutgoingIntegrationCleverTapPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["baseUrl", "accountId", "passcode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_configuration.py b/talon_one/models/outgoing_integration_configuration.py
index 37d3bbe..2d1866d 100644
--- a/talon_one/models/outgoing_integration_configuration.py
+++ b/talon_one/models/outgoing_integration_configuration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationConfiguration(BaseModel):
"""
@@ -33,7 +34,8 @@ class OutgoingIntegrationConfiguration(BaseModel):
__properties: ClassVar[List[str]] = ["id", "accountId", "typeId", "policy"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_iterable_policy.py b/talon_one/models/outgoing_integration_iterable_policy.py
index 19092d5..8d0baef 100644
--- a/talon_one/models/outgoing_integration_iterable_policy.py
+++ b/talon_one/models/outgoing_integration_iterable_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationIterablePolicy(BaseModel):
"""
@@ -31,7 +32,8 @@ class OutgoingIntegrationIterablePolicy(BaseModel):
__properties: ClassVar[List[str]] = ["baseUrl", "apiKey"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_mo_engage_policy.py b/talon_one/models/outgoing_integration_mo_engage_policy.py
index 809ff28..1295704 100644
--- a/talon_one/models/outgoing_integration_mo_engage_policy.py
+++ b/talon_one/models/outgoing_integration_mo_engage_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationMoEngagePolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class OutgoingIntegrationMoEngagePolicy(BaseModel):
__properties: ClassVar[List[str]] = ["baseUrl", "appId", "dataApiId", "dataApiKey"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_template.py b/talon_one/models/outgoing_integration_template.py
index ddf50ef..d9ddf2d 100644
--- a/talon_one/models/outgoing_integration_template.py
+++ b/talon_one/models/outgoing_integration_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationTemplate(BaseModel):
"""
@@ -45,7 +46,8 @@ def method_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_template_with_configuration_details.py b/talon_one/models/outgoing_integration_template_with_configuration_details.py
index 87e566c..d7354a3 100644
--- a/talon_one/models/outgoing_integration_template_with_configuration_details.py
+++ b/talon_one/models/outgoing_integration_template_with_configuration_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationTemplateWithConfigurationDetails(BaseModel):
"""
@@ -46,7 +47,8 @@ def method_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_templates.py b/talon_one/models/outgoing_integration_templates.py
index 25a37d8..efdbdd2 100644
--- a/talon_one/models/outgoing_integration_templates.py
+++ b/talon_one/models/outgoing_integration_templates.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.outgoing_integration_template import OutgoingIntegrationTemplate
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationTemplates(BaseModel):
"""
@@ -31,7 +32,8 @@ class OutgoingIntegrationTemplates(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_type.py b/talon_one/models/outgoing_integration_type.py
index ac6f93f..c7c6b73 100644
--- a/talon_one/models/outgoing_integration_type.py
+++ b/talon_one/models/outgoing_integration_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationType(BaseModel):
"""
@@ -35,7 +36,8 @@ class OutgoingIntegrationType(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "description", "category", "documentationLink"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/outgoing_integration_types.py b/talon_one/models/outgoing_integration_types.py
index e070e70..c8a8482 100644
--- a/talon_one/models/outgoing_integration_types.py
+++ b/talon_one/models/outgoing_integration_types.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.outgoing_integration_type import OutgoingIntegrationType
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class OutgoingIntegrationTypes(BaseModel):
"""
@@ -31,7 +32,8 @@ class OutgoingIntegrationTypes(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/patch_item_catalog_action.py b/talon_one/models/patch_item_catalog_action.py
index b65a8ad..a67bdff 100644
--- a/talon_one/models/patch_item_catalog_action.py
+++ b/talon_one/models/patch_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.product import Product
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PatchItemCatalogAction(BaseModel):
"""
@@ -35,7 +36,8 @@ class PatchItemCatalogAction(BaseModel):
__properties: ClassVar[List[str]] = ["sku", "price", "attributes", "product", "createIfNotExists"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/patch_many_items_catalog_action.py b/talon_one/models/patch_many_items_catalog_action.py
index dc33844..937cd27 100644
--- a/talon_one/models/patch_many_items_catalog_action.py
+++ b/talon_one/models/patch_many_items_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.catalog_action_filter import CatalogActionFilter
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PatchManyItemsCatalogAction(BaseModel):
"""
@@ -33,7 +34,8 @@ class PatchManyItemsCatalogAction(BaseModel):
__properties: ClassVar[List[str]] = ["price", "filters", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/pending_active_points_data.py b/talon_one/models/pending_active_points_data.py
index 4a29674..510fc12 100644
--- a/talon_one/models/pending_active_points_data.py
+++ b/talon_one/models/pending_active_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PendingActivePointsData(BaseModel):
"""
@@ -38,7 +39,8 @@ class PendingActivePointsData(BaseModel):
__properties: ClassVar[List[str]] = ["LoyaltyProgramID", "SubledgerID", "CustomerProfileID", "Points", "ActiveOn", "ExpireOn", "SessionIntegrationID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/pending_active_points_notification.py b/talon_one/models/pending_active_points_notification.py
index ade9d40..5627426 100644
--- a/talon_one/models/pending_active_points_notification.py
+++ b/talon_one/models/pending_active_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.pending_active_points_data import PendingActivePointsData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PendingActivePointsNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/pending_points_notification_policy.py b/talon_one/models/pending_points_notification_policy.py
index ef45876..3a337c2 100644
--- a/talon_one/models/pending_points_notification_policy.py
+++ b/talon_one/models/pending_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PendingPointsNotificationPolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class PendingPointsNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/picklist.py b/talon_one/models/picklist.py
index fb2f433..94733cf 100644
--- a/talon_one/models/picklist.py
+++ b/talon_one/models/picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Picklist(BaseModel):
"""
@@ -46,7 +47,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/placeholder_details.py b/talon_one/models/placeholder_details.py
index 5bc0de9..35457b3 100644
--- a/talon_one/models/placeholder_details.py
+++ b/talon_one/models/placeholder_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PlaceholderDetails(BaseModel):
"""
@@ -32,7 +33,8 @@ class PlaceholderDetails(BaseModel):
__properties: ClassVar[List[str]] = ["name", "type", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_detail.py b/talon_one/models/price_detail.py
index 4082aef..6f79edc 100644
--- a/talon_one/models/price_detail.py
+++ b/talon_one/models/price_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from uuid import UUID
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceDetail(BaseModel):
"""
@@ -36,7 +37,8 @@ class PriceDetail(BaseModel):
__properties: ClassVar[List[str]] = ["price", "adjustmentContextId", "adjustmentReferenceId", "adjustmentEffectiveFrom", "adjustmentEffectiveUntil"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_history_request.py b/talon_one/models/price_history_request.py
index a71876a..e7f44eb 100644
--- a/talon_one/models/price_history_request.py
+++ b/talon_one/models/price_history_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceHistoryRequest(BaseModel):
"""
@@ -33,7 +34,8 @@ class PriceHistoryRequest(BaseModel):
__properties: ClassVar[List[str]] = ["sku", "startDate", "endDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_history_response.py b/talon_one/models/price_history_response.py
index 326323f..2d91175 100644
--- a/talon_one/models/price_history_response.py
+++ b/talon_one/models/price_history_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.history import History
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceHistoryResponse(BaseModel):
"""
@@ -32,7 +33,8 @@ class PriceHistoryResponse(BaseModel):
__properties: ClassVar[List[str]] = ["sku", "history"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_type.py b/talon_one/models/price_type.py
index 010904a..8449290 100644
--- a/talon_one/models/price_type.py
+++ b/talon_one/models/price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceType(BaseModel):
"""
@@ -47,7 +48,8 @@ def name_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_type_reference_detail.py b/talon_one/models/price_type_reference_detail.py
index 2bed0b1..c5b7e7b 100644
--- a/talon_one/models/price_type_reference_detail.py
+++ b/talon_one/models/price_type_reference_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceTypeReferenceDetail(BaseModel):
"""
@@ -40,7 +41,8 @@ def referencing_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/price_type_references.py b/talon_one/models/price_type_references.py
index 9dde351..bf14b9a 100644
--- a/talon_one/models/price_type_references.py
+++ b/talon_one/models/price_type_references.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.price_type_reference_detail import PriceTypeReferenceDetail
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PriceTypeReferences(BaseModel):
"""
@@ -32,7 +33,8 @@ class PriceTypeReferences(BaseModel):
__properties: ClassVar[List[str]] = ["priceTypeId", "references"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/product.py b/talon_one/models/product.py
index 4cf905b..0b4e1a5 100644
--- a/talon_one/models/product.py
+++ b/talon_one/models/product.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Product(BaseModel):
"""
@@ -30,7 +31,8 @@ class Product(BaseModel):
__properties: ClassVar[List[str]] = ["name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/product_search_match.py b/talon_one/models/product_search_match.py
index a3561a8..a1a868e 100644
--- a/talon_one/models/product_search_match.py
+++ b/talon_one/models/product_search_match.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProductSearchMatch(BaseModel):
"""
@@ -32,7 +33,8 @@ class ProductSearchMatch(BaseModel):
__properties: ClassVar[List[str]] = ["productId", "value", "productSkuId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/product_unit_analytics.py b/talon_one/models/product_unit_analytics.py
index ba3a271..5818bfb 100644
--- a/talon_one/models/product_unit_analytics.py
+++ b/talon_one/models/product_unit_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.product_unit_analytics_totals import ProductUnitAnalyticsTotals
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProductUnitAnalytics(BaseModel):
"""
@@ -33,7 +34,8 @@ class ProductUnitAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["data", "totals"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/product_unit_analytics_data_point.py b/talon_one/models/product_unit_analytics_data_point.py
index 9261ec2..88cc7a5 100644
--- a/talon_one/models/product_unit_analytics_data_point.py
+++ b/talon_one/models/product_unit_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.analytics_data_point_with_trend import AnalyticsDataPointWithTrend
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProductUnitAnalyticsDataPoint(BaseModel):
"""
@@ -36,7 +37,8 @@ class ProductUnitAnalyticsDataPoint(BaseModel):
__properties: ClassVar[List[str]] = ["startTime", "endTime", "unitsSold", "productId", "productName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/product_unit_analytics_totals.py b/talon_one/models/product_unit_analytics_totals.py
index 8be8e0d..b418c47 100644
--- a/talon_one/models/product_unit_analytics_totals.py
+++ b/talon_one/models/product_unit_analytics_totals.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.analytics_data_point_with_trend import AnalyticsDataPointWithTrend
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProductUnitAnalyticsTotals(BaseModel):
"""
@@ -31,7 +32,8 @@ class ProductUnitAnalyticsTotals(BaseModel):
__properties: ClassVar[List[str]] = ["unitsSold"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/profile_audiences_changes.py b/talon_one/models/profile_audiences_changes.py
index 8f19f13..f57865c 100644
--- a/talon_one/models/profile_audiences_changes.py
+++ b/talon_one/models/profile_audiences_changes.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProfileAudiencesChanges(BaseModel):
"""
@@ -31,7 +32,8 @@ class ProfileAudiencesChanges(BaseModel):
__properties: ClassVar[List[str]] = ["adds", "deletes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/projected_tier.py b/talon_one/models/projected_tier.py
index 1b5bf24..dca9f84 100644
--- a/talon_one/models/projected_tier.py
+++ b/talon_one/models/projected_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ProjectedTier(BaseModel):
"""
@@ -32,7 +33,8 @@ class ProjectedTier(BaseModel):
__properties: ClassVar[List[str]] = ["projectedActivePoints", "stayInTierPoints", "projectedTierName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/promote_experiment.py b/talon_one/models/promote_experiment.py
index e2cf20a..5b5b1f0 100644
--- a/talon_one/models/promote_experiment.py
+++ b/talon_one/models/promote_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.experiment_campaign_copy import ExperimentCampaignCopy
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class PromoteExperiment(BaseModel):
"""
@@ -34,7 +35,8 @@ class PromoteExperiment(BaseModel):
__properties: ClassVar[List[str]] = ["targetApplicationId", "variantId", "disableExperiment", "campaign"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/redeem_referral_effect_props.py b/talon_one/models/redeem_referral_effect_props.py
index bc9da10..d89227e 100644
--- a/talon_one/models/redeem_referral_effect_props.py
+++ b/talon_one/models/redeem_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RedeemReferralEffectProps(BaseModel):
"""
@@ -31,7 +32,8 @@ class RedeemReferralEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["id", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/referral.py b/talon_one/models/referral.py
index 87b12d8..2e0c914 100644
--- a/talon_one/models/referral.py
+++ b/talon_one/models/referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Referral(BaseModel):
"""
@@ -44,7 +45,8 @@ class Referral(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "startDate", "expiryDate", "usageLimit", "campaignId", "advocateProfileIntegrationId", "friendProfileIntegrationId", "attributes", "importId", "code", "usageCounter", "batchId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/referral_constraints.py b/talon_one/models/referral_constraints.py
index f0e9eaf..c75fbdf 100644
--- a/talon_one/models/referral_constraints.py
+++ b/talon_one/models/referral_constraints.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReferralConstraints(BaseModel):
"""
@@ -34,7 +35,8 @@ class ReferralConstraints(BaseModel):
__properties: ClassVar[List[str]] = ["startDate", "expiryDate", "usageLimit"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/referral_created_effect_props.py b/talon_one/models/referral_created_effect_props.py
index 5378a77..a196504 100644
--- a/talon_one/models/referral_created_effect_props.py
+++ b/talon_one/models/referral_created_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReferralCreatedEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class ReferralCreatedEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/referral_rejection_reason.py b/talon_one/models/referral_rejection_reason.py
index 4dae293..c181705 100644
--- a/talon_one/models/referral_rejection_reason.py
+++ b/talon_one/models/referral_rejection_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReferralRejectionReason(BaseModel):
"""
@@ -39,7 +40,8 @@ def reason_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/reject_coupon_effect_props.py b/talon_one/models/reject_coupon_effect_props.py
index 6c6629f..03a776e 100644
--- a/talon_one/models/reject_coupon_effect_props.py
+++ b/talon_one/models/reject_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RejectCouponEffectProps(BaseModel):
"""
@@ -35,7 +36,8 @@ class RejectCouponEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value", "rejectionReason", "conditionIndex", "effectIndex", "details", "campaignExclusionReason"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/reject_referral_effect_props.py b/talon_one/models/reject_referral_effect_props.py
index 52829b2..c8febe6 100644
--- a/talon_one/models/reject_referral_effect_props.py
+++ b/talon_one/models/reject_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RejectReferralEffectProps(BaseModel):
"""
@@ -35,7 +36,8 @@ class RejectReferralEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value", "rejectionReason", "conditionIndex", "effectIndex", "details", "campaignExclusionReason"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/remove_from_audience_effect_props.py b/talon_one/models/remove_from_audience_effect_props.py
index e73a493..bae54d2 100644
--- a/talon_one/models/remove_from_audience_effect_props.py
+++ b/talon_one/models/remove_from_audience_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RemoveFromAudienceEffectProps(BaseModel):
"""
@@ -33,7 +34,8 @@ class RemoveFromAudienceEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["audienceId", "audienceName", "profileIntegrationId", "profileId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/remove_item_catalog_action.py b/talon_one/models/remove_item_catalog_action.py
index 2457237..f1b5bb1 100644
--- a/talon_one/models/remove_item_catalog_action.py
+++ b/talon_one/models/remove_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RemoveItemCatalogAction(BaseModel):
"""
@@ -30,7 +31,8 @@ class RemoveItemCatalogAction(BaseModel):
__properties: ClassVar[List[str]] = ["sku"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/remove_many_items_catalog_action.py b/talon_one/models/remove_many_items_catalog_action.py
index c7d159f..91a3fb5 100644
--- a/talon_one/models/remove_many_items_catalog_action.py
+++ b/talon_one/models/remove_many_items_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.catalog_action_filter import CatalogActionFilter
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RemoveManyItemsCatalogAction(BaseModel):
"""
@@ -31,7 +32,8 @@ class RemoveManyItemsCatalogAction(BaseModel):
__properties: ClassVar[List[str]] = ["filters"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/reopen_session_response.py b/talon_one/models/reopen_session_response.py
index 4a1af3f..88ec921 100644
--- a/talon_one/models/reopen_session_response.py
+++ b/talon_one/models/reopen_session_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.effect import Effect
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReopenSessionResponse(BaseModel):
"""
@@ -31,7 +32,8 @@ class ReopenSessionResponse(BaseModel):
__properties: ClassVar[List[str]] = ["effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/reserve_coupon_effect_props.py b/talon_one/models/reserve_coupon_effect_props.py
index 6c63445..e7ac59a 100644
--- a/talon_one/models/reserve_coupon_effect_props.py
+++ b/talon_one/models/reserve_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReserveCouponEffectProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class ReserveCouponEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["couponValue", "profileIntegrationId", "isNewReservation"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/response_content_object.py b/talon_one/models/response_content_object.py
index 56111ab..37d1a47 100644
--- a/talon_one/models/response_content_object.py
+++ b/talon_one/models/response_content_object.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ResponseContentObject(BaseModel):
"""
@@ -41,7 +42,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/return_integration_request.py b/talon_one/models/return_integration_request.py
index bee24da..be1d360 100644
--- a/talon_one/models/return_integration_request.py
+++ b/talon_one/models/return_integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.new_return import NewReturn
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReturnIntegrationRequest(BaseModel):
"""
@@ -43,7 +44,8 @@ def response_content_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/returned_cart_item.py b/talon_one/models/returned_cart_item.py
index e321b50..4df9e52 100644
--- a/talon_one/models/returned_cart_item.py
+++ b/talon_one/models/returned_cart_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ReturnedCartItem(BaseModel):
"""
@@ -33,7 +34,8 @@ class ReturnedCartItem(BaseModel):
__properties: ClassVar[List[str]] = ["position", "quantity", "sku"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/revision.py b/talon_one/models/revision.py
index 5650ca7..adacdf0 100644
--- a/talon_one/models/revision.py
+++ b/talon_one/models/revision.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.revision_version import RevisionVersion
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Revision(BaseModel):
"""
@@ -41,7 +42,8 @@ class Revision(BaseModel):
__properties: ClassVar[List[str]] = ["id", "activateAt", "accountId", "applicationId", "campaignId", "created", "createdBy", "activatedAt", "activatedBy", "currentVersion"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/revision_activation.py b/talon_one/models/revision_activation.py
index ec21be4..8df863e 100644
--- a/talon_one/models/revision_activation.py
+++ b/talon_one/models/revision_activation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RevisionActivation(BaseModel):
"""
@@ -31,7 +32,8 @@ class RevisionActivation(BaseModel):
__properties: ClassVar[List[str]] = ["activateAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/revision_activation_request.py b/talon_one/models/revision_activation_request.py
index 730208c..4780256 100644
--- a/talon_one/models/revision_activation_request.py
+++ b/talon_one/models/revision_activation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RevisionActivationRequest(BaseModel):
"""
@@ -33,7 +34,8 @@ class RevisionActivationRequest(BaseModel):
__properties: ClassVar[List[str]] = ["userIds", "activateAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/revision_version.py b/talon_one/models/revision_version.py
index 9909b6a..be1657e 100644
--- a/talon_one/models/revision_version.py
+++ b/talon_one/models/revision_version.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RevisionVersion(BaseModel):
"""
@@ -43,6 +44,7 @@ class RevisionVersion(BaseModel):
limits: Optional[List[LimitConfig]] = Field(default=None, description="The set of limits that will operate for this campaign version.")
reevaluate_on_return: Optional[StrictBool] = Field(default=None, description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: Optional[List[StrictStr]] = Field(default=None, description="A list of features for the campaign.")
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
account_id: StrictInt = Field(alias="accountId")
application_id: StrictInt = Field(alias="applicationId")
campaign_id: StrictInt = Field(alias="campaignId")
@@ -50,7 +52,7 @@ class RevisionVersion(BaseModel):
created_by: StrictInt = Field(alias="createdBy")
revision_id: StrictInt = Field(alias="revisionId")
version: StrictInt
- __properties: ClassVar[List[str]] = ["id", "name", "startTime", "endTime", "attributes", "description", "activeRulesetId", "tags", "couponSettings", "referralSettings", "limits", "reevaluateOnReturn", "features", "accountId", "applicationId", "campaignId", "created", "createdBy", "revisionId", "version"]
+ __properties: ClassVar[List[str]] = ["id", "name", "startTime", "endTime", "attributes", "description", "activeRulesetId", "tags", "couponSettings", "referralSettings", "limits", "reevaluateOnReturn", "features", "couponAttributes", "accountId", "applicationId", "campaignId", "created", "createdBy", "revisionId", "version"]
@field_validator('features')
def features_validate_enum(cls, value):
@@ -64,7 +66,8 @@ def features_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -76,8 +79,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -140,6 +142,7 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"limits": [LimitConfig.from_dict(_item) for _item in obj["limits"]] if obj.get("limits") is not None else None,
"reevaluateOnReturn": obj.get("reevaluateOnReturn"),
"features": obj.get("features"),
+ "couponAttributes": obj.get("couponAttributes"),
"accountId": obj.get("accountId"),
"applicationId": obj.get("applicationId"),
"campaignId": obj.get("campaignId"),
diff --git a/talon_one/models/role.py b/talon_one/models/role.py
index 94273c6..091d471 100644
--- a/talon_one/models/role.py
+++ b/talon_one/models/role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Role(BaseModel):
"""
@@ -39,7 +40,8 @@ class Role(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "modified", "accountId", "campaignGroupID", "name", "description", "members", "acl"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_assign.py b/talon_one/models/role_assign.py
index ba29ed2..44f1e89 100644
--- a/talon_one/models/role_assign.py
+++ b/talon_one/models/role_assign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleAssign(BaseModel):
"""
@@ -31,7 +32,8 @@ class RoleAssign(BaseModel):
__properties: ClassVar[List[str]] = ["users", "roles"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_membership.py b/talon_one/models/role_membership.py
index 43cfbd0..ca8a515 100644
--- a/talon_one/models/role_membership.py
+++ b/talon_one/models/role_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleMembership(BaseModel):
"""
@@ -31,7 +32,8 @@ class RoleMembership(BaseModel):
__properties: ClassVar[List[str]] = ["RoleID", "UserID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2.py b/talon_one/models/role_v2.py
index 809f5e5..6f3fbc6 100644
--- a/talon_one/models/role_v2.py
+++ b/talon_one/models/role_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.role_v2_permissions import RoleV2Permissions
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2(BaseModel):
"""
@@ -40,7 +41,8 @@ class RoleV2(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "modified", "accountId", "name", "description", "permissions", "members", "isReadonly"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2_application_details.py b/talon_one/models/role_v2_application_details.py
index 2b082ad..3eaed31 100644
--- a/talon_one/models/role_v2_application_details.py
+++ b/talon_one/models/role_v2_application_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -19,8 +19,10 @@
from pydantic import BaseModel, ConfigDict, Field, StrictStr
from typing import Any, ClassVar, Dict, List, Optional
+from talon_one.models.roles_v2_thresholds import RolesV2Thresholds
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2ApplicationDetails(BaseModel):
"""
@@ -30,10 +32,12 @@ class RoleV2ApplicationDetails(BaseModel):
campaign: Optional[StrictStr] = Field(default=None, description="Name of the campaign-related permission set for the given Application.")
draft_campaign: Optional[StrictStr] = Field(default=None, description="Name of the draft campaign-related permission set for the given Application.", alias="draftCampaign")
tools: Optional[StrictStr] = Field(default=None, description="Name of the tools-related permission set.")
- __properties: ClassVar[List[str]] = ["application", "campaign", "draftCampaign", "tools"]
+ thresholds: Optional[RolesV2Thresholds] = Field(default=None, description="Support user limits for actions that require admin approval within the given application.")
+ __properties: ClassVar[List[str]] = ["application", "campaign", "draftCampaign", "tools", "thresholds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -71,6 +74,9 @@ def to_dict(self) -> Dict[str, Any]:
exclude=excluded_fields,
exclude_none=True,
)
+ # override the default output from pydantic by calling `to_dict()` of thresholds
+ if self.thresholds:
+ _dict['thresholds'] = self.thresholds.to_dict()
return _dict
@classmethod
@@ -86,7 +92,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"application": obj.get("application"),
"campaign": obj.get("campaign"),
"draftCampaign": obj.get("draftCampaign"),
- "tools": obj.get("tools")
+ "tools": obj.get("tools"),
+ "thresholds": RolesV2Thresholds.from_dict(obj["thresholds"]) if obj.get("thresholds") is not None else None
})
return _obj
diff --git a/talon_one/models/role_v2_base.py b/talon_one/models/role_v2_base.py
index 4a499e9..6b6ff8d 100644
--- a/talon_one/models/role_v2_base.py
+++ b/talon_one/models/role_v2_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.role_v2_permissions import RoleV2Permissions
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2Base(BaseModel):
"""
@@ -34,7 +35,8 @@ class RoleV2Base(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "permissions", "members"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2_permission_set.py b/talon_one/models/role_v2_permission_set.py
index 8c2509f..b45f6e1 100644
--- a/talon_one/models/role_v2_permission_set.py
+++ b/talon_one/models/role_v2_permission_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2PermissionSet(BaseModel):
"""
@@ -32,7 +33,8 @@ class RoleV2PermissionSet(BaseModel):
__properties: ClassVar[List[str]] = ["name", "logicalOperations"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2_permissions.py b/talon_one/models/role_v2_permissions.py
index 8b23ca2..6468deb 100644
--- a/talon_one/models/role_v2_permissions.py
+++ b/talon_one/models/role_v2_permissions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.role_v2_roles_group import RoleV2RolesGroup
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2Permissions(BaseModel):
"""
@@ -34,7 +35,8 @@ class RoleV2Permissions(BaseModel):
__properties: ClassVar[List[str]] = ["permissionSets", "roles"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2_readonly.py b/talon_one/models/role_v2_readonly.py
index 815aa4f..2bdc70c 100644
--- a/talon_one/models/role_v2_readonly.py
+++ b/talon_one/models/role_v2_readonly.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2Readonly(BaseModel):
"""
@@ -30,7 +31,8 @@ class RoleV2Readonly(BaseModel):
__properties: ClassVar[List[str]] = ["isReadonly"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/role_v2_roles_group.py b/talon_one/models/role_v2_roles_group.py
index a956cf0..2467781 100644
--- a/talon_one/models/role_v2_roles_group.py
+++ b/talon_one/models/role_v2_roles_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.role_v2_application_details import RoleV2ApplicationDetails
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RoleV2RolesGroup(BaseModel):
"""
@@ -34,7 +35,8 @@ class RoleV2RolesGroup(BaseModel):
__properties: ClassVar[List[str]] = ["applications", "loyaltyPrograms", "campaignAccessGroups", "account"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/roles_v2_thresholds.py b/talon_one/models/roles_v2_thresholds.py
new file mode 100644
index 0000000..6d5af83
--- /dev/null
+++ b/talon_one/models/roles_v2_thresholds.py
@@ -0,0 +1,88 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictInt
+from typing import Any, ClassVar, Dict, List, Optional
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class RolesV2Thresholds(BaseModel):
+ """
+ RolesV2Thresholds
+ """ # noqa: E501
+ loyalty_points_limit: Optional[StrictInt] = Field(default=None, description="Maximum number of loyalty points a support user can award without approval.", alias="loyaltyPointsLimit")
+ __properties: ClassVar[List[str]] = ["loyaltyPointsLimit"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of RolesV2Thresholds from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of RolesV2Thresholds from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "loyaltyPointsLimit": obj.get("loyaltyPointsLimit")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/rollback_added_loyalty_points_effect_props.py b/talon_one/models/rollback_added_loyalty_points_effect_props.py
index 93895a8..5516890 100644
--- a/talon_one/models/rollback_added_loyalty_points_effect_props.py
+++ b/talon_one/models/rollback_added_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackAddedLoyaltyPointsEffectProps(BaseModel):
"""
@@ -48,7 +49,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -60,8 +62,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rollback_coupon_effect_props.py b/talon_one/models/rollback_coupon_effect_props.py
index 4b04b9c..e663aba 100644
--- a/talon_one/models/rollback_coupon_effect_props.py
+++ b/talon_one/models/rollback_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackCouponEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class RollbackCouponEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rollback_deducted_loyalty_points_effect_props.py b/talon_one/models/rollback_deducted_loyalty_points_effect_props.py
index 2f469c3..3f664e5 100644
--- a/talon_one/models/rollback_deducted_loyalty_points_effect_props.py
+++ b/talon_one/models/rollback_deducted_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackDeductedLoyaltyPointsEffectProps(BaseModel):
"""
@@ -49,7 +50,8 @@ def card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -61,8 +63,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rollback_discount_effect_props.py b/talon_one/models/rollback_discount_effect_props.py
index a16aee8..cae27ec 100644
--- a/talon_one/models/rollback_discount_effect_props.py
+++ b/talon_one/models/rollback_discount_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackDiscountEffectProps(BaseModel):
"""
@@ -36,7 +37,8 @@ class RollbackDiscountEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value", "cartItemPosition", "cartItemSubPosition", "additionalCostId", "additionalCost", "scope"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rollback_increased_achievement_progress_effect_props.py b/talon_one/models/rollback_increased_achievement_progress_effect_props.py
index 141c743..d061a2d 100644
--- a/talon_one/models/rollback_increased_achievement_progress_effect_props.py
+++ b/talon_one/models/rollback_increased_achievement_progress_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackIncreasedAchievementProgressEffectProps(BaseModel):
"""
@@ -35,7 +36,8 @@ class RollbackIncreasedAchievementProgressEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["achievementId", "achievementName", "progressTrackerId", "decreaseProgressBy", "currentProgress", "target"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rollback_referral_effect_props.py b/talon_one/models/rollback_referral_effect_props.py
index 5b73545..4784c90 100644
--- a/talon_one/models/rollback_referral_effect_props.py
+++ b/talon_one/models/rollback_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RollbackReferralEffectProps(BaseModel):
"""
@@ -30,7 +31,8 @@ class RollbackReferralEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rule.py b/talon_one/models/rule.py
index 2894c88..a1104ad 100644
--- a/talon_one/models/rule.py
+++ b/talon_one/models/rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.binding import Binding
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Rule(BaseModel):
"""
@@ -39,7 +40,8 @@ class Rule(BaseModel):
__properties: ClassVar[List[str]] = ["id", "parentId", "title", "description", "bindings", "condition", "effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rule_failure_reason.py b/talon_one/models/rule_failure_reason.py
index 131cb03..8676a09 100644
--- a/talon_one/models/rule_failure_reason.py
+++ b/talon_one/models/rule_failure_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class RuleFailureReason(BaseModel):
"""
@@ -43,7 +44,8 @@ class RuleFailureReason(BaseModel):
__properties: ClassVar[List[str]] = ["campaignID", "campaignName", "rulesetID", "couponID", "couponValue", "referralID", "referralValue", "ruleIndex", "ruleName", "conditionIndex", "effectIndex", "details", "evaluationGroupID", "evaluationGroupMode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/rule_metadata.py b/talon_one/models/rule_metadata.py
new file mode 100644
index 0000000..ce05d33
--- /dev/null
+++ b/talon_one/models/rule_metadata.py
@@ -0,0 +1,94 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictStr
+from typing import Any, ClassVar, Dict, List, Optional
+from typing import Optional, Set
+from typing_extensions import Self
+from pydantic_core import to_jsonable_python
+
+class RuleMetadata(BaseModel):
+ """
+ RuleMetadata
+ """ # noqa: E501
+ title: StrictStr = Field(description="A short description of the rule.")
+ display_name: Optional[StrictStr] = Field(default=None, description="A customer-facing name used to identify the reward defined within the rule.", alias="displayName")
+ display_description: Optional[StrictStr] = Field(default=None, description="A customer-facing description of the reward defined in the rule. For example, this property can contain details about eligibility requirements, reward timelines, or terms and conditions. ", alias="displayDescription")
+ related_data: Optional[StrictStr] = Field(default=None, description="Data related to the reward, such as a vendor name, an image URL, or a content management system (CMS) ID. ", alias="relatedData")
+ __properties: ClassVar[List[str]] = ["title", "displayName", "displayDescription", "relatedData"]
+
+ model_config = ConfigDict(
+ validate_by_name=True,
+ validate_by_alias=True,
+ validate_assignment=True,
+ protected_namespaces=(),
+ )
+
+
+ def to_str(self) -> str:
+ """Returns the string representation of the model using alias"""
+ return pprint.pformat(self.model_dump(by_alias=True))
+
+ def to_json(self) -> str:
+ """Returns the JSON representation of the model using alias"""
+ return json.dumps(to_jsonable_python(self.to_dict()))
+
+ @classmethod
+ def from_json(cls, json_str: str) -> Optional[Self]:
+ """Create an instance of RuleMetadata from a JSON string"""
+ return cls.from_dict(json.loads(json_str))
+
+ def to_dict(self) -> Dict[str, Any]:
+ """Return the dictionary representation of the model using alias.
+
+ This has the following differences from calling pydantic's
+ `self.model_dump(by_alias=True)`:
+
+ * `None` is only added to the output dict for nullable fields that
+ were set at model initialization. Other fields with value `None`
+ are ignored.
+ """
+ excluded_fields: Set[str] = set([
+ ])
+
+ _dict = self.model_dump(
+ by_alias=True,
+ exclude=excluded_fields,
+ exclude_none=True,
+ )
+ return _dict
+
+ @classmethod
+ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+ """Create an instance of RuleMetadata from a dict"""
+ if obj is None:
+ return None
+
+ if not isinstance(obj, dict):
+ return cls.model_validate(obj)
+
+ _obj = cls.model_validate({
+ "title": obj.get("title"),
+ "displayName": obj.get("displayName"),
+ "displayDescription": obj.get("displayDescription"),
+ "relatedData": obj.get("relatedData")
+ })
+ return _obj
+
+
diff --git a/talon_one/models/ruleset.py b/talon_one/models/ruleset.py
index d1271ad..cd52428 100644
--- a/talon_one/models/ruleset.py
+++ b/talon_one/models/ruleset.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.rule import Rule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Ruleset(BaseModel):
"""
@@ -43,7 +44,8 @@ class Ruleset(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "userId", "rules", "strikethroughRules", "bindings", "rbVersion", "activate", "campaignId", "templateId", "activatedAt"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/saml_connection.py b/talon_one/models/saml_connection.py
index 68986d6..e612dbc 100644
--- a/talon_one/models/saml_connection.py
+++ b/talon_one/models/saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SamlConnection(BaseModel):
"""
@@ -42,7 +43,8 @@ class SamlConnection(BaseModel):
__properties: ClassVar[List[str]] = ["accountId", "name", "enabled", "issuer", "signOnURL", "signOutURL", "metadataURL", "audienceURI", "id", "created", "assertionConsumerServiceURL"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/saml_connection_internal.py b/talon_one/models/saml_connection_internal.py
index 19a7d49..f51d783 100644
--- a/talon_one/models/saml_connection_internal.py
+++ b/talon_one/models/saml_connection_internal.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SamlConnectionInternal(BaseModel):
"""
@@ -32,7 +33,8 @@ class SamlConnectionInternal(BaseModel):
__properties: ClassVar[List[str]] = ["name", "metadataDocument"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/saml_connection_metadata.py b/talon_one/models/saml_connection_metadata.py
index 14e5f3f..248c823 100644
--- a/talon_one/models/saml_connection_metadata.py
+++ b/talon_one/models/saml_connection_metadata.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SamlConnectionMetadata(BaseModel):
"""
@@ -34,7 +35,8 @@ class SamlConnectionMetadata(BaseModel):
__properties: ClassVar[List[str]] = ["name", "enabled", "accountId", "metadataDocument"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/saml_login_endpoint.py b/talon_one/models/saml_login_endpoint.py
index 73d640b..8c77f4e 100644
--- a/talon_one/models/saml_login_endpoint.py
+++ b/talon_one/models/saml_login_endpoint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SamlLoginEndpoint(BaseModel):
"""
@@ -33,7 +34,8 @@ class SamlLoginEndpoint(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "loginURL"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_base_group.py b/talon_one/models/scim_base_group.py
index 666e609..d599bd2 100644
--- a/talon_one/models/scim_base_group.py
+++ b/talon_one/models/scim_base_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_group_member import ScimGroupMember
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimBaseGroup(BaseModel):
"""
@@ -32,7 +33,8 @@ class ScimBaseGroup(BaseModel):
__properties: ClassVar[List[str]] = ["displayName", "members"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_base_user.py b/talon_one/models/scim_base_user.py
index be0daab..c09dd06 100644
--- a/talon_one/models/scim_base_user.py
+++ b/talon_one/models/scim_base_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_base_user_name import ScimBaseUserName
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimBaseUser(BaseModel):
"""
@@ -34,7 +35,8 @@ class ScimBaseUser(BaseModel):
__properties: ClassVar[List[str]] = ["active", "displayName", "userName", "name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_base_user_name.py b/talon_one/models/scim_base_user_name.py
index 668239c..ae6b887 100644
--- a/talon_one/models/scim_base_user_name.py
+++ b/talon_one/models/scim_base_user_name.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimBaseUserName(BaseModel):
"""
@@ -30,7 +31,8 @@ class ScimBaseUserName(BaseModel):
__properties: ClassVar[List[str]] = ["formatted"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_group.py b/talon_one/models/scim_group.py
index 286f9b2..f4b407f 100644
--- a/talon_one/models/scim_group.py
+++ b/talon_one/models/scim_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_group_member import ScimGroupMember
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimGroup(BaseModel):
"""
@@ -33,7 +34,8 @@ class ScimGroup(BaseModel):
__properties: ClassVar[List[str]] = ["displayName", "members", "id"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_group_member.py b/talon_one/models/scim_group_member.py
index 8b70833..9ced5ec 100644
--- a/talon_one/models/scim_group_member.py
+++ b/talon_one/models/scim_group_member.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimGroupMember(BaseModel):
"""
@@ -31,7 +32,8 @@ class ScimGroupMember(BaseModel):
__properties: ClassVar[List[str]] = ["value", "display"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_groups_list_response.py b/talon_one/models/scim_groups_list_response.py
index 5f17802..f97dc2f 100644
--- a/talon_one/models/scim_groups_list_response.py
+++ b/talon_one/models/scim_groups_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_group import ScimGroup
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimGroupsListResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class ScimGroupsListResponse(BaseModel):
__properties: ClassVar[List[str]] = ["Resources", "schemas", "totalResults"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_new_user.py b/talon_one/models/scim_new_user.py
index 05e17ee..6f56e30 100644
--- a/talon_one/models/scim_new_user.py
+++ b/talon_one/models/scim_new_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_base_user_name import ScimBaseUserName
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimNewUser(BaseModel):
"""
@@ -34,7 +35,8 @@ class ScimNewUser(BaseModel):
__properties: ClassVar[List[str]] = ["active", "displayName", "userName", "name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_patch_operation.py b/talon_one/models/scim_patch_operation.py
index 4a8fa6c..5a239b6 100644
--- a/talon_one/models/scim_patch_operation.py
+++ b/talon_one/models/scim_patch_operation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimPatchOperation(BaseModel):
"""
@@ -39,7 +40,8 @@ def op_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_patch_request.py b/talon_one/models/scim_patch_request.py
index db9ed7f..3f33dcb 100644
--- a/talon_one/models/scim_patch_request.py
+++ b/talon_one/models/scim_patch_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_patch_operation import ScimPatchOperation
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimPatchRequest(BaseModel):
"""
@@ -32,7 +33,8 @@ class ScimPatchRequest(BaseModel):
__properties: ClassVar[List[str]] = ["schemas", "Operations"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_resource.py b/talon_one/models/scim_resource.py
index c41f9eb..34d81c5 100644
--- a/talon_one/models/scim_resource.py
+++ b/talon_one/models/scim_resource.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimResource(BaseModel):
"""
@@ -32,7 +33,8 @@ class ScimResource(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_resource_types_list_response.py b/talon_one/models/scim_resource_types_list_response.py
index b3a7471..569cbc6 100644
--- a/talon_one/models/scim_resource_types_list_response.py
+++ b/talon_one/models/scim_resource_types_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_resource import ScimResource
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimResourceTypesListResponse(BaseModel):
"""
@@ -31,7 +32,8 @@ class ScimResourceTypesListResponse(BaseModel):
__properties: ClassVar[List[str]] = ["Resources"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_schema_resource.py b/talon_one/models/scim_schema_resource.py
index d3a9e74..5dbd9a0 100644
--- a/talon_one/models/scim_schema_resource.py
+++ b/talon_one/models/scim_schema_resource.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimSchemaResource(BaseModel):
"""
@@ -33,7 +34,8 @@ class ScimSchemaResource(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "description", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_schemas_list_response.py b/talon_one/models/scim_schemas_list_response.py
index 70a1a08..efee254 100644
--- a/talon_one/models/scim_schemas_list_response.py
+++ b/talon_one/models/scim_schemas_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_schema_resource import ScimSchemaResource
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimSchemasListResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class ScimSchemasListResponse(BaseModel):
__properties: ClassVar[List[str]] = ["Resources", "schemas", "totalResults"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response.py b/talon_one/models/scim_service_provider_config_response.py
index 0eb1476..1ebbb45 100644
--- a/talon_one/models/scim_service_provider_config_response.py
+++ b/talon_one/models/scim_service_provider_config_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -26,6 +26,7 @@
from talon_one.models.scim_service_provider_config_response_sort import ScimServiceProviderConfigResponseSort
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponse(BaseModel):
"""
@@ -41,7 +42,8 @@ class ScimServiceProviderConfigResponse(BaseModel):
__properties: ClassVar[List[str]] = ["bulk", "changePassword", "documentationUri", "filter", "patch", "schemas", "sort"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response_bulk.py b/talon_one/models/scim_service_provider_config_response_bulk.py
index dba2500..f862310 100644
--- a/talon_one/models/scim_service_provider_config_response_bulk.py
+++ b/talon_one/models/scim_service_provider_config_response_bulk.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponseBulk(BaseModel):
"""
@@ -32,7 +33,8 @@ class ScimServiceProviderConfigResponseBulk(BaseModel):
__properties: ClassVar[List[str]] = ["maxOperations", "maxPayloadSize", "supported"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response_change_password.py b/talon_one/models/scim_service_provider_config_response_change_password.py
index 19786b1..a244437 100644
--- a/talon_one/models/scim_service_provider_config_response_change_password.py
+++ b/talon_one/models/scim_service_provider_config_response_change_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponseChangePassword(BaseModel):
"""
@@ -30,7 +31,8 @@ class ScimServiceProviderConfigResponseChangePassword(BaseModel):
__properties: ClassVar[List[str]] = ["supported"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response_filter.py b/talon_one/models/scim_service_provider_config_response_filter.py
index a617f65..994e0b2 100644
--- a/talon_one/models/scim_service_provider_config_response_filter.py
+++ b/talon_one/models/scim_service_provider_config_response_filter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponseFilter(BaseModel):
"""
@@ -31,7 +32,8 @@ class ScimServiceProviderConfigResponseFilter(BaseModel):
__properties: ClassVar[List[str]] = ["maxResults", "supported"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response_patch.py b/talon_one/models/scim_service_provider_config_response_patch.py
index c05164a..24a7b77 100644
--- a/talon_one/models/scim_service_provider_config_response_patch.py
+++ b/talon_one/models/scim_service_provider_config_response_patch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponsePatch(BaseModel):
"""
@@ -30,7 +31,8 @@ class ScimServiceProviderConfigResponsePatch(BaseModel):
__properties: ClassVar[List[str]] = ["supported"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_service_provider_config_response_sort.py b/talon_one/models/scim_service_provider_config_response_sort.py
index ad3acbe..8c2bfcb 100644
--- a/talon_one/models/scim_service_provider_config_response_sort.py
+++ b/talon_one/models/scim_service_provider_config_response_sort.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimServiceProviderConfigResponseSort(BaseModel):
"""
@@ -30,7 +31,8 @@ class ScimServiceProviderConfigResponseSort(BaseModel):
__properties: ClassVar[List[str]] = ["supported"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_user.py b/talon_one/models/scim_user.py
index 1722d30..b3f0efe 100644
--- a/talon_one/models/scim_user.py
+++ b/talon_one/models/scim_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_base_user_name import ScimBaseUserName
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimUser(BaseModel):
"""
@@ -35,7 +36,8 @@ class ScimUser(BaseModel):
__properties: ClassVar[List[str]] = ["active", "displayName", "userName", "name", "id"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/scim_users_list_response.py b/talon_one/models/scim_users_list_response.py
index 3514549..8f45afa 100644
--- a/talon_one/models/scim_users_list_response.py
+++ b/talon_one/models/scim_users_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.scim_user import ScimUser
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ScimUsersListResponse(BaseModel):
"""
@@ -33,7 +34,8 @@ class ScimUsersListResponse(BaseModel):
__properties: ClassVar[List[str]] = ["Resources", "schemas", "totalResults"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/secondary_deployment.py b/talon_one/models/secondary_deployment.py
index cd83150..e0851ae 100644
--- a/talon_one/models/secondary_deployment.py
+++ b/talon_one/models/secondary_deployment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SecondaryDeployment(BaseModel):
"""
@@ -53,7 +54,8 @@ def status_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/session.py b/talon_one/models/session.py
index fa93f0b..2da0dc0 100644
--- a/talon_one/models/session.py
+++ b/talon_one/models/session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Session(BaseModel):
"""
@@ -33,7 +34,8 @@ class Session(BaseModel):
__properties: ClassVar[List[str]] = ["userId", "token", "created"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/set_discount_effect_props.py b/talon_one/models/set_discount_effect_props.py
index 0df528b..503c7e2 100644
--- a/talon_one/models/set_discount_effect_props.py
+++ b/talon_one/models/set_discount_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SetDiscountEffectProps(BaseModel):
"""
@@ -33,7 +34,8 @@ class SetDiscountEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value", "scope", "desiredValue"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/set_discount_per_additional_cost_effect_props.py b/talon_one/models/set_discount_per_additional_cost_effect_props.py
index 061aa27..3e19d44 100644
--- a/talon_one/models/set_discount_per_additional_cost_effect_props.py
+++ b/talon_one/models/set_discount_per_additional_cost_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SetDiscountPerAdditionalCostEffectProps(BaseModel):
"""
@@ -34,7 +35,8 @@ class SetDiscountPerAdditionalCostEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "additionalCostId", "additionalCost", "value", "desiredValue"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/set_discount_per_additional_cost_per_item_effect_props.py b/talon_one/models/set_discount_per_additional_cost_per_item_effect_props.py
index c65e4d0..d26966f 100644
--- a/talon_one/models/set_discount_per_additional_cost_per_item_effect_props.py
+++ b/talon_one/models/set_discount_per_additional_cost_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SetDiscountPerAdditionalCostPerItemEffectProps(BaseModel):
"""
@@ -36,7 +37,8 @@ class SetDiscountPerAdditionalCostPerItemEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "additionalCostId", "value", "position", "subPosition", "additionalCost", "desiredValue"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/set_discount_per_item_effect_props.py b/talon_one/models/set_discount_per_item_effect_props.py
index ec6aa0b..fc37404 100644
--- a/talon_one/models/set_discount_per_item_effect_props.py
+++ b/talon_one/models/set_discount_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SetDiscountPerItemEffectProps(BaseModel):
"""
@@ -41,7 +42,8 @@ class SetDiscountPerItemEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value", "position", "subPosition", "desiredValue", "scope", "totalDiscount", "desiredTotalDiscount", "bundleIndex", "bundleName", "targetedItemPosition", "targetedItemSubPosition"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/set_loyalty_points_expiry_date_effect_props.py b/talon_one/models/set_loyalty_points_expiry_date_effect_props.py
index b6d3e42..d5d1276 100644
--- a/talon_one/models/set_loyalty_points_expiry_date_effect_props.py
+++ b/talon_one/models/set_loyalty_points_expiry_date_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.loyalty_ledger_entry_expiry_date_change import LoyaltyLedgerEntryExpiryDateChange
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SetLoyaltyPointsExpiryDateEffectProps(BaseModel):
"""
@@ -35,7 +36,8 @@ class SetLoyaltyPointsExpiryDateEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["programId", "subLedgerId", "newExpiryDate", "affectedTransactions"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/show_bundle_metadata_effect_props.py b/talon_one/models/show_bundle_metadata_effect_props.py
index 7104514..900892c 100644
--- a/talon_one/models/show_bundle_metadata_effect_props.py
+++ b/talon_one/models/show_bundle_metadata_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ShowBundleMetadataEffectProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class ShowBundleMetadataEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["description", "bundleAttributes", "itemsIndices"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/show_notification_effect_props.py b/talon_one/models/show_notification_effect_props.py
index 1f8d02f..190073c 100644
--- a/talon_one/models/show_notification_effect_props.py
+++ b/talon_one/models/show_notification_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ShowNotificationEffectProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class ShowNotificationEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["notificationType", "title", "body"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/sku_unit_analytics.py b/talon_one/models/sku_unit_analytics.py
index e3381e8..1ca6fb4 100644
--- a/talon_one/models/sku_unit_analytics.py
+++ b/talon_one/models/sku_unit_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.sku_unit_analytics_data_point import SkuUnitAnalyticsDataPoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SkuUnitAnalytics(BaseModel):
"""
@@ -33,7 +34,8 @@ class SkuUnitAnalytics(BaseModel):
__properties: ClassVar[List[str]] = ["data", "totals"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/sku_unit_analytics_data_point.py b/talon_one/models/sku_unit_analytics_data_point.py
index c24e861..d9ca2cc 100644
--- a/talon_one/models/sku_unit_analytics_data_point.py
+++ b/talon_one/models/sku_unit_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.analytics_data_point_with_trend import AnalyticsDataPointWithTrend
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SkuUnitAnalyticsDataPoint(BaseModel):
"""
@@ -35,7 +36,8 @@ class SkuUnitAnalyticsDataPoint(BaseModel):
__properties: ClassVar[List[str]] = ["startTime", "endTime", "unitsSold", "sku"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/slot_def.py b/talon_one/models/slot_def.py
index f96ee1d..6eb0cfe 100644
--- a/talon_one/models/slot_def.py
+++ b/talon_one/models/slot_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SlotDef(BaseModel):
"""
@@ -35,7 +36,8 @@ class SlotDef(BaseModel):
__properties: ClassVar[List[str]] = ["name", "type", "title", "description", "help", "writable"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/sso_config.py b/talon_one/models/sso_config.py
index 5d52a7c..458e278 100644
--- a/talon_one/models/sso_config.py
+++ b/talon_one/models/sso_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SSOConfig(BaseModel):
"""
@@ -31,7 +32,8 @@ class SSOConfig(BaseModel):
__properties: ClassVar[List[str]] = ["enforced", "newAcsUrl"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/store.py b/talon_one/models/store.py
index 3fe9d40..7901e53 100644
--- a/talon_one/models/store.py
+++ b/talon_one/models/store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Store(BaseModel):
"""
@@ -40,7 +41,8 @@ class Store(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "name", "description", "attributes", "integrationId", "applicationId", "updated", "linkedCampaignIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_changed_item.py b/talon_one/models/strikethrough_changed_item.py
index d2785a9..2e4ce33 100644
--- a/talon_one/models/strikethrough_changed_item.py
+++ b/talon_one/models/strikethrough_changed_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.strikethrough_effect import StrikethroughEffect
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughChangedItem(BaseModel):
"""
@@ -41,7 +42,8 @@ class StrikethroughChangedItem(BaseModel):
__properties: ClassVar[List[str]] = ["id", "catalogId", "sku", "version", "price", "prices", "evaluatedAt", "effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_custom_effect_per_item_props.py b/talon_one/models/strikethrough_custom_effect_per_item_props.py
index 4b230b8..54e9422 100644
--- a/talon_one/models/strikethrough_custom_effect_per_item_props.py
+++ b/talon_one/models/strikethrough_custom_effect_per_item_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughCustomEffectPerItemProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class StrikethroughCustomEffectPerItemProps(BaseModel):
__properties: ClassVar[List[str]] = ["effectId", "name", "payload"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_debug_response.py b/talon_one/models/strikethrough_debug_response.py
index 3ceb79c..2de424a 100644
--- a/talon_one/models/strikethrough_debug_response.py
+++ b/talon_one/models/strikethrough_debug_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.strikethrough_effect import StrikethroughEffect
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughDebugResponse(BaseModel):
"""
@@ -32,7 +33,8 @@ class StrikethroughDebugResponse(BaseModel):
__properties: ClassVar[List[str]] = ["campaignsIDs", "effects"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_effect.py b/talon_one/models/strikethrough_effect.py
index c5c9969..b19978d 100644
--- a/talon_one/models/strikethrough_effect.py
+++ b/talon_one/models/strikethrough_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughEffect(BaseModel):
"""
@@ -42,7 +43,8 @@ class StrikethroughEffect(BaseModel):
__properties: ClassVar[List[str]] = ["campaignId", "rulesetId", "ruleIndex", "ruleName", "type", "props", "startTime", "endTime", "selectedPriceType", "selectedPrice", "adjustmentReferenceId", "targets"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_labeling_notification.py b/talon_one/models/strikethrough_labeling_notification.py
index 8f0cf18..8640962 100644
--- a/talon_one/models/strikethrough_labeling_notification.py
+++ b/talon_one/models/strikethrough_labeling_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.strikethrough_trigger import StrikethroughTrigger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughLabelingNotification(BaseModel):
"""
@@ -58,7 +59,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -70,8 +72,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_set_discount_per_item_effect_props.py b/talon_one/models/strikethrough_set_discount_per_item_effect_props.py
index e6709ff..4b7132f 100644
--- a/talon_one/models/strikethrough_set_discount_per_item_effect_props.py
+++ b/talon_one/models/strikethrough_set_discount_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughSetDiscountPerItemEffectProps(BaseModel):
"""
@@ -32,7 +33,8 @@ class StrikethroughSetDiscountPerItemEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value", "excludeFromBestPriorPriceHistory"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_set_discount_per_item_member_effect_props.py b/talon_one/models/strikethrough_set_discount_per_item_member_effect_props.py
index 64302b1..d9db432 100644
--- a/talon_one/models/strikethrough_set_discount_per_item_member_effect_props.py
+++ b/talon_one/models/strikethrough_set_discount_per_item_member_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughSetDiscountPerItemMemberEffectProps(BaseModel):
"""
@@ -31,7 +32,8 @@ class StrikethroughSetDiscountPerItemMemberEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["name", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/strikethrough_trigger.py b/talon_one/models/strikethrough_trigger.py
index bddcdc6..38748e9 100644
--- a/talon_one/models/strikethrough_trigger.py
+++ b/talon_one/models/strikethrough_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class StrikethroughTrigger(BaseModel):
"""
@@ -35,7 +36,8 @@ class StrikethroughTrigger(BaseModel):
__properties: ClassVar[List[str]] = ["id", "type", "triggeredAt", "totalAffectedItems", "payload"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/summarize_campaign_store_budget200_response.py b/talon_one/models/summarize_campaign_store_budget200_response.py
index 3c33d0a..36ddfb5 100644
--- a/talon_one/models/summarize_campaign_store_budget200_response.py
+++ b/talon_one/models/summarize_campaign_store_budget200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.summary_campaign_store_budget import SummaryCampaignStoreBudget
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SummarizeCampaignStoreBudget200Response(BaseModel):
"""
@@ -31,7 +32,8 @@ class SummarizeCampaignStoreBudget200Response(BaseModel):
__properties: ClassVar[List[str]] = ["data"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/summary_campaign_store_budget.py b/talon_one/models/summary_campaign_store_budget.py
index e96fa18..c124780 100644
--- a/talon_one/models/summary_campaign_store_budget.py
+++ b/talon_one/models/summary_campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class SummaryCampaignStoreBudget(BaseModel):
"""
@@ -50,7 +51,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/talang_attribute.py b/talon_one/models/talang_attribute.py
index e5a500c..2c05a41 100644
--- a/talon_one/models/talang_attribute.py
+++ b/talon_one/models/talang_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TalangAttribute(BaseModel):
"""
@@ -55,7 +56,8 @@ def kind_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -67,8 +69,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/talang_attribute_visibility.py b/talon_one/models/talang_attribute_visibility.py
index 65a51c9..545da1a 100644
--- a/talon_one/models/talang_attribute_visibility.py
+++ b/talon_one/models/talang_attribute_visibility.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TalangAttributeVisibility(BaseModel):
"""
@@ -31,7 +32,8 @@ class TalangAttributeVisibility(BaseModel):
__properties: ClassVar[List[str]] = ["invisible", "visible"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/template_arg_def.py b/talon_one/models/template_arg_def.py
index 9741615..5944afd 100644
--- a/talon_one/models/template_arg_def.py
+++ b/talon_one/models/template_arg_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TemplateArgDef(BaseModel):
"""
@@ -44,7 +45,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -56,8 +58,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/template_def.py b/talon_one/models/template_def.py
index cd3c717..c934410 100644
--- a/talon_one/models/template_def.py
+++ b/talon_one/models/template_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TemplateDef(BaseModel):
"""
@@ -43,7 +44,8 @@ class TemplateDef(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "applicationId", "title", "description", "help", "category", "expr", "args", "expose", "name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/template_limit_config.py b/talon_one/models/template_limit_config.py
index 1d0fbf8..b056277 100644
--- a/talon_one/models/template_limit_config.py
+++ b/talon_one/models/template_limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TemplateLimitConfig(BaseModel):
"""
@@ -52,7 +53,8 @@ def entities_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -64,8 +66,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier.py b/talon_one/models/tier.py
index 0d0a9ad..3de292c 100644
--- a/talon_one/models/tier.py
+++ b/talon_one/models/tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Tier(BaseModel):
"""
@@ -45,7 +46,8 @@ def downgrade_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_downgrade_data.py b/talon_one/models/tier_downgrade_data.py
index 3acabd5..190b9f9 100644
--- a/talon_one/models/tier_downgrade_data.py
+++ b/talon_one/models/tier_downgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierDowngradeData(BaseModel):
"""
@@ -39,7 +40,8 @@ class TierDowngradeData(BaseModel):
__properties: ClassVar[List[str]] = ["CustomerProfileID", "LoyaltyProgramID", "SubledgerID", "CurrentTier", "CurrentPoints", "OldTier", "TierExpirationDate", "TimestampOfTierChange"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_downgrade_notification.py b/talon_one/models/tier_downgrade_notification.py
index b09769b..43a294f 100644
--- a/talon_one/models/tier_downgrade_notification.py
+++ b/talon_one/models/tier_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.tier_downgrade_data import TierDowngradeData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierDowngradeNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_downgrade_notification_policy.py b/talon_one/models/tier_downgrade_notification_policy.py
index 41cfdc5..f78ba51 100644
--- a/talon_one/models/tier_downgrade_notification_policy.py
+++ b/talon_one/models/tier_downgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierDowngradeNotificationPolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class TierDowngradeNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_upgrade_data.py b/talon_one/models/tier_upgrade_data.py
index d8c274d..25a739d 100644
--- a/talon_one/models/tier_upgrade_data.py
+++ b/talon_one/models/tier_upgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierUpgradeData(BaseModel):
"""
@@ -41,7 +42,8 @@ class TierUpgradeData(BaseModel):
__properties: ClassVar[List[str]] = ["CustomerProfileID", "LoyaltyProgramID", "SubledgerID", "CurrentTier", "CurrentPoints", "OldTier", "PointsRequiredToTheNextTier", "NextTier", "TierExpirationDate", "TimestampOfTierChange"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -53,8 +55,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_upgrade_notification.py b/talon_one/models/tier_upgrade_notification.py
index 9e4b034..e7596a4 100644
--- a/talon_one/models/tier_upgrade_notification.py
+++ b/talon_one/models/tier_upgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.tier_upgrade_data import TierUpgradeData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierUpgradeNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_upgrade_notification_policy.py b/talon_one/models/tier_upgrade_notification_policy.py
index 7021543..3c5c698 100644
--- a/talon_one/models/tier_upgrade_notification_policy.py
+++ b/talon_one/models/tier_upgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierUpgradeNotificationPolicy(BaseModel):
"""
@@ -33,7 +34,8 @@ class TierUpgradeNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "batchingEnabled", "batchSize"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_will_downgrade_data.py b/talon_one/models/tier_will_downgrade_data.py
index e91fd49..945fa1a 100644
--- a/talon_one/models/tier_will_downgrade_data.py
+++ b/talon_one/models/tier_will_downgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierWillDowngradeData(BaseModel):
"""
@@ -39,7 +40,8 @@ class TierWillDowngradeData(BaseModel):
__properties: ClassVar[List[str]] = ["CustomerProfileID", "LoyaltyProgramID", "SubledgerID", "CurrentTier", "CurrentPoints", "PointsRequiredToRemain", "NextTier", "TierExpirationDate"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_will_downgrade_notification.py b/talon_one/models/tier_will_downgrade_notification.py
index 966863a..dcddda2 100644
--- a/talon_one/models/tier_will_downgrade_notification.py
+++ b/talon_one/models/tier_will_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.tier_will_downgrade_data import TierWillDowngradeData
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierWillDowngradeNotification(BaseModel):
"""
@@ -40,7 +41,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_will_downgrade_notification_policy.py b/talon_one/models/tier_will_downgrade_notification_policy.py
index 55ac1bd..e53bd46 100644
--- a/talon_one/models/tier_will_downgrade_notification_policy.py
+++ b/talon_one/models/tier_will_downgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.tier_will_downgrade_notification_trigger import TierWillDowngradeNotificationTrigger
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierWillDowngradeNotificationPolicy(BaseModel):
"""
@@ -35,7 +36,8 @@ class TierWillDowngradeNotificationPolicy(BaseModel):
__properties: ClassVar[List[str]] = ["name", "batchingEnabled", "batchSize", "triggers"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/tier_will_downgrade_notification_trigger.py b/talon_one/models/tier_will_downgrade_notification_trigger.py
index 85dc1b5..c753698 100644
--- a/talon_one/models/tier_will_downgrade_notification_trigger.py
+++ b/talon_one/models/tier_will_downgrade_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TierWillDowngradeNotificationTrigger(BaseModel):
"""
@@ -38,7 +39,8 @@ def period_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/time_point.py b/talon_one/models/time_point.py
index 7ea8610..e7b53be 100644
--- a/talon_one/models/time_point.py
+++ b/talon_one/models/time_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TimePoint(BaseModel):
"""
@@ -36,7 +37,8 @@ class TimePoint(BaseModel):
__properties: ClassVar[List[str]] = ["month", "dayOfMonth", "dayOfWeek", "hour", "minute", "second"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/transfer_loyalty_card.py b/talon_one/models/transfer_loyalty_card.py
index e167696..ea8f5b5 100644
--- a/talon_one/models/transfer_loyalty_card.py
+++ b/talon_one/models/transfer_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TransferLoyaltyCard(BaseModel):
"""
@@ -39,7 +40,8 @@ def new_card_identifier_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/trigger_webhook_effect_props.py b/talon_one/models/trigger_webhook_effect_props.py
index 662f21d..b08158d 100644
--- a/talon_one/models/trigger_webhook_effect_props.py
+++ b/talon_one/models/trigger_webhook_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Union
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TriggerWebhookEffectProps(BaseModel):
"""
@@ -31,7 +32,8 @@ class TriggerWebhookEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["webhookId", "webhookName"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/two_fa_config.py b/talon_one/models/two_fa_config.py
index 201bb5f..340421e 100644
--- a/talon_one/models/two_fa_config.py
+++ b/talon_one/models/two_fa_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class TwoFAConfig(BaseModel):
"""
@@ -31,7 +32,8 @@ class TwoFAConfig(BaseModel):
__properties: ClassVar[List[str]] = ["enabled", "requireEverySignIn"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_account.py b/talon_one/models/update_account.py
index 981906e..fb4d072 100644
--- a/talon_one/models/update_account.py
+++ b/talon_one/models/update_account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateAccount(BaseModel):
"""
@@ -46,7 +47,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_achievement.py b/talon_one/models/update_achievement.py
index 10e64be..74f7923 100644
--- a/talon_one/models/update_achievement.py
+++ b/talon_one/models/update_achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.time_point import TimePoint
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateAchievement(BaseModel):
"""
@@ -73,7 +74,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -85,8 +87,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_achievement_v2.py b/talon_one/models/update_achievement_v2.py
index 42a5c09..5564efa 100644
--- a/talon_one/models/update_achievement_v2.py
+++ b/talon_one/models/update_achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateAchievementV2(BaseModel):
"""
@@ -74,7 +75,8 @@ def activation_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -86,8 +88,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_application.py b/talon_one/models/update_application.py
index c97eb8c..7b72a8e 100644
--- a/talon_one/models/update_application.py
+++ b/talon_one/models/update_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateApplication(BaseModel):
"""
@@ -79,7 +80,8 @@ def default_discount_additional_cost_per_item_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -91,8 +93,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_application_api_key.py b/talon_one/models/update_application_api_key.py
index 26482ea..d108732 100644
--- a/talon_one/models/update_application_api_key.py
+++ b/talon_one/models/update_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateApplicationAPIKey(BaseModel):
"""
@@ -30,7 +31,8 @@ class UpdateApplicationAPIKey(BaseModel):
__properties: ClassVar[List[str]] = ["timeOffset"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_application_cif.py b/talon_one/models/update_application_cif.py
index 8fb3724..464ab7d 100644
--- a/talon_one/models/update_application_cif.py
+++ b/talon_one/models/update_application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateApplicationCIF(BaseModel):
"""
@@ -34,7 +35,8 @@ class UpdateApplicationCIF(BaseModel):
__properties: ClassVar[List[str]] = ["description", "activeExpressionId", "modifiedBy", "modified"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_attribute_effect_props.py b/talon_one/models/update_attribute_effect_props.py
index 6a93d0b..e747b7a 100644
--- a/talon_one/models/update_attribute_effect_props.py
+++ b/talon_one/models/update_attribute_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateAttributeEffectProps(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateAttributeEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["path", "value"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_audience.py b/talon_one/models/update_audience.py
index 3e66dcf..50df29f 100644
--- a/talon_one/models/update_audience.py
+++ b/talon_one/models/update_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateAudience(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateAudience(BaseModel):
__properties: ClassVar[List[str]] = ["name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_blueprint.py b/talon_one/models/update_blueprint.py
index 476eb11..e9d64a1 100644
--- a/talon_one/models/update_blueprint.py
+++ b/talon_one/models/update_blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.catalog_rule import CatalogRule
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateBlueprint(BaseModel):
"""
@@ -46,7 +47,8 @@ def category_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -58,8 +60,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_campaign.py b/talon_one/models/update_campaign.py
index 4364b04..73d81cd 100644
--- a/talon_one/models/update_campaign.py
+++ b/talon_one/models/update_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCampaign(BaseModel):
"""
@@ -36,7 +37,7 @@ class UpdateCampaign(BaseModel):
end_time: Optional[datetime] = Field(default=None, description="Timestamp when the campaign will become inactive.", alias="endTime")
attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with this campaign.")
state: Optional[StrictStr] = Field(default='enabled', description="A disabled or archived campaign is not evaluated for rules or coupons. ")
- active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
+ active_ruleset_id: Optional[StrictInt] = Field(default=None, description="[ID of Ruleset](https://docs.talon.one/management-api#tag/Campaigns/operation/getRulesets) this campaign applies on customer session evaluation. ", alias="activeRulesetId")
tags: Annotated[List[Annotated[str, Field(min_length=1, strict=True, max_length=50)]], Field(max_length=50)] = Field(description="A list of tags for the campaign.")
reevaluate_on_return: Optional[StrictBool] = Field(default=None, description="Indicates whether this campaign should be reevaluated when a customer returns an item.", alias="reevaluateOnReturn")
features: List[StrictStr] = Field(description="A list of features for the campaign.")
@@ -46,8 +47,9 @@ class UpdateCampaign(BaseModel):
campaign_groups: Optional[List[StrictInt]] = Field(default=None, description="The IDs of the [campaign groups](https://docs.talon.one/docs/product/account/account-settings/managing-campaign-groups) this campaign belongs to. ", alias="campaignGroups")
evaluation_group_id: Optional[StrictInt] = Field(default=None, description="The ID of the campaign evaluation group the campaign belongs to.", alias="evaluationGroupId")
type: Optional[StrictStr] = Field(default='advanced', description="The campaign type. Possible type values: - `cartItem`: Type of campaign that can apply effects only to cart items. - `advanced`: Type of campaign that can apply effects to customer sessions and cart items. ")
- linked_store_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of store IDs that you want to link to the campaign. **Note:** - Campaigns with linked store IDs will only be evaluated when there is a [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) that references a linked store. - If you linked stores to the campaign by uploading a CSV file, you cannot use this property and it should be empty. - Use of this property is limited to 50 stores. To link more than 50 stores, upload them via a CSV file. ", alias="linkedStoreIds")
- __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "evaluationGroupId", "type", "linkedStoreIds"]
+ linked_store_ids: Optional[List[StrictInt]] = Field(default=None, description="A list of store IDs that you want to link to the campaign. > [!note] **Note** > - Campaigns with linked store IDs will only be evaluated when there is a > [customer session update](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) > that references a linked store. > - If you linked stores to the campaign by uploading a CSV file, you cannot use this property and it should be empty. > - Use of this property is limited to 50 stores. To link more than 50 stores, upload them via a CSV file. ", alias="linkedStoreIds")
+ coupon_attributes: Optional[Dict[str, Any]] = Field(default=None, description="Arbitrary properties associated with coupons in this campaign.", alias="couponAttributes")
+ __properties: ClassVar[List[str]] = ["name", "description", "startTime", "endTime", "attributes", "state", "activeRulesetId", "tags", "reevaluateOnReturn", "features", "couponSettings", "referralSettings", "limits", "campaignGroups", "evaluationGroupId", "type", "linkedStoreIds", "couponAttributes"]
@field_validator('state')
def state_validate_enum(cls, value):
@@ -78,7 +80,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -90,8 +93,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
@@ -157,7 +159,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
"campaignGroups": obj.get("campaignGroups"),
"evaluationGroupId": obj.get("evaluationGroupId"),
"type": obj.get("type") if obj.get("type") is not None else 'advanced',
- "linkedStoreIds": obj.get("linkedStoreIds")
+ "linkedStoreIds": obj.get("linkedStoreIds"),
+ "couponAttributes": obj.get("couponAttributes")
})
return _obj
diff --git a/talon_one/models/update_campaign_collection.py b/talon_one/models/update_campaign_collection.py
index 2b2d4fa..8229b4b 100644
--- a/talon_one/models/update_campaign_collection.py
+++ b/talon_one/models/update_campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCampaignCollection(BaseModel):
"""
@@ -30,7 +31,8 @@ class UpdateCampaignCollection(BaseModel):
__properties: ClassVar[List[str]] = ["description"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_campaign_evaluation_group.py b/talon_one/models/update_campaign_evaluation_group.py
index 8650993..f565c40 100644
--- a/talon_one/models/update_campaign_evaluation_group.py
+++ b/talon_one/models/update_campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCampaignEvaluationGroup(BaseModel):
"""
@@ -50,7 +51,8 @@ def evaluation_scope_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -62,8 +64,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_campaign_group.py b/talon_one/models/update_campaign_group.py
index 58bf261..e1596a3 100644
--- a/talon_one/models/update_campaign_group.py
+++ b/talon_one/models/update_campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCampaignGroup(BaseModel):
"""
@@ -34,7 +35,8 @@ class UpdateCampaignGroup(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "subscribedApplicationsIds", "campaignIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_campaign_template.py b/talon_one/models/update_campaign_template.py
index d5137df..5c33197 100644
--- a/talon_one/models/update_campaign_template.py
+++ b/talon_one/models/update_campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -27,6 +27,7 @@
from talon_one.models.template_limit_config import TemplateLimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCampaignTemplate(BaseModel):
"""
@@ -82,7 +83,8 @@ def campaign_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -94,8 +96,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_catalog.py b/talon_one/models/update_catalog.py
index 11f9690..1ffef27 100644
--- a/talon_one/models/update_catalog.py
+++ b/talon_one/models/update_catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCatalog(BaseModel):
"""
@@ -32,7 +33,8 @@ class UpdateCatalog(BaseModel):
__properties: ClassVar[List[str]] = ["description", "name", "subscribedApplicationsIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_collection.py b/talon_one/models/update_collection.py
index 6133364..9a7d0d5 100644
--- a/talon_one/models/update_collection.py
+++ b/talon_one/models/update_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCollection(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateCollection(BaseModel):
__properties: ClassVar[List[str]] = ["description", "subscribedApplicationsIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_coupon.py b/talon_one/models/update_coupon.py
index 654a7e1..1fd15a5 100644
--- a/talon_one/models/update_coupon.py
+++ b/talon_one/models/update_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.limit_config import LimitConfig
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCoupon(BaseModel):
"""
@@ -42,7 +43,8 @@ class UpdateCoupon(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "limits", "recipientIntegrationId", "attributes", "isReservationMandatory", "implicitlyReserved"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -54,8 +56,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_coupon_batch.py b/talon_one/models/update_coupon_batch.py
index 8482a43..a6c00d7 100644
--- a/talon_one/models/update_coupon_batch.py
+++ b/talon_one/models/update_coupon_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCouponBatch(BaseModel):
"""
@@ -38,7 +39,8 @@ class UpdateCouponBatch(BaseModel):
__properties: ClassVar[List[str]] = ["usageLimit", "discountLimit", "reservationLimit", "startDate", "expiryDate", "attributes", "batchID"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -50,8 +52,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_coupons_data.py b/talon_one/models/update_coupons_data.py
index 33f9f92..0482224 100644
--- a/talon_one/models/update_coupons_data.py
+++ b/talon_one/models/update_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCouponsData(BaseModel):
"""
@@ -43,7 +44,8 @@ def notification_type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -55,8 +57,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_custom_effect.py b/talon_one/models/update_custom_effect.py
index 8149303..44fb14b 100644
--- a/talon_one/models/update_custom_effect.py
+++ b/talon_one/models/update_custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCustomEffect(BaseModel):
"""
@@ -53,7 +54,8 @@ def title_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -65,8 +67,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_customer_profile_v2409_response.py b/talon_one/models/update_customer_profile_v2409_response.py
index a08914e..45d8442 100644
--- a/talon_one/models/update_customer_profile_v2409_response.py
+++ b/talon_one/models/update_customer_profile_v2409_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCustomerProfileV2409Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class UpdateCustomerProfileV2409Response(BaseModel):
__properties: ClassVar[List[str]] = ["message", "errors", "StatusCode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_customer_session_v2409_response.py b/talon_one/models/update_customer_session_v2409_response.py
index 739f5ec..2a6a5ae 100644
--- a/talon_one/models/update_customer_session_v2409_response.py
+++ b/talon_one/models/update_customer_session_v2409_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateCustomerSessionV2409Response(BaseModel):
"""
@@ -32,7 +33,8 @@ class UpdateCustomerSessionV2409Response(BaseModel):
__properties: ClassVar[List[str]] = ["message", "errors", "StatusCode"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_experiment.py b/talon_one/models/update_experiment.py
index 16b5b4b..115d298 100644
--- a/talon_one/models/update_experiment.py
+++ b/talon_one/models/update_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.update_campaign import UpdateCampaign
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateExperiment(BaseModel):
"""
@@ -32,7 +33,8 @@ class UpdateExperiment(BaseModel):
__properties: ClassVar[List[str]] = ["isVariantAssignmentExternal", "campaign"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_experiment_variant.py b/talon_one/models/update_experiment_variant.py
index 3a59cde..dca3d13 100644
--- a/talon_one/models/update_experiment_variant.py
+++ b/talon_one/models/update_experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.new_ruleset import NewRuleset
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateExperimentVariant(BaseModel):
"""
@@ -35,7 +36,8 @@ class UpdateExperimentVariant(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "ruleset", "weight"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -47,8 +49,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_experiment_variant_array.py b/talon_one/models/update_experiment_variant_array.py
index 79862a3..1486906 100644
--- a/talon_one/models/update_experiment_variant_array.py
+++ b/talon_one/models/update_experiment_variant_array.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from talon_one.models.update_experiment_variant import UpdateExperimentVariant
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateExperimentVariantArray(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateExperimentVariantArray(BaseModel):
__properties: ClassVar[List[str]] = ["variants"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_experiment_variant_name.py b/talon_one/models/update_experiment_variant_name.py
index 28dba6a..2dc87a9 100644
--- a/talon_one/models/update_experiment_variant_name.py
+++ b/talon_one/models/update_experiment_variant_name.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateExperimentVariantName(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateExperimentVariantName(BaseModel):
__properties: ClassVar[List[str]] = ["name"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_loyalty_card.py b/talon_one/models/update_loyalty_card.py
index f8f9af4..708df48 100644
--- a/talon_one/models/update_loyalty_card.py
+++ b/talon_one/models/update_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateLoyaltyCard(BaseModel):
"""
@@ -31,7 +32,8 @@ class UpdateLoyaltyCard(BaseModel):
__properties: ClassVar[List[str]] = ["status", "blockReason"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_loyalty_card_request.py b/talon_one/models/update_loyalty_card_request.py
index a0e846d..3266f83 100644
--- a/talon_one/models/update_loyalty_card_request.py
+++ b/talon_one/models/update_loyalty_card_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateLoyaltyCardRequest(BaseModel):
"""
@@ -30,7 +31,8 @@ class UpdateLoyaltyCardRequest(BaseModel):
__properties: ClassVar[List[str]] = ["status"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_loyalty_program.py b/talon_one/models/update_loyalty_program.py
index f8bf7c2..3741b9f 100644
--- a/talon_one/models/update_loyalty_program.py
+++ b/talon_one/models/update_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -25,6 +25,7 @@
from talon_one.models.new_loyalty_tier import NewLoyaltyTier
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateLoyaltyProgram(BaseModel):
"""
@@ -89,7 +90,8 @@ def return_policy_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -101,8 +103,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_loyalty_program_tier.py b/talon_one/models/update_loyalty_program_tier.py
index 12bc4cd..6a77c99 100644
--- a/talon_one/models/update_loyalty_program_tier.py
+++ b/talon_one/models/update_loyalty_program_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateLoyaltyProgramTier(BaseModel):
"""
@@ -33,7 +34,8 @@ class UpdateLoyaltyProgramTier(BaseModel):
__properties: ClassVar[List[str]] = ["id", "name", "minPoints"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_picklist.py b/talon_one/models/update_picklist.py
index 191c14b..30a44d5 100644
--- a/talon_one/models/update_picklist.py
+++ b/talon_one/models/update_picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdatePicklist(BaseModel):
"""
@@ -39,7 +40,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -51,8 +53,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_price_type.py b/talon_one/models/update_price_type.py
index f13ebc4..72e9bdb 100644
--- a/talon_one/models/update_price_type.py
+++ b/talon_one/models/update_price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdatePriceType(BaseModel):
"""
@@ -32,7 +33,8 @@ class UpdatePriceType(BaseModel):
__properties: ClassVar[List[str]] = ["title", "description", "targetedAudiencesIds"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -44,8 +46,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_referral.py b/talon_one/models/update_referral.py
index 3375cae..da5023a 100644
--- a/talon_one/models/update_referral.py
+++ b/talon_one/models/update_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateReferral(BaseModel):
"""
@@ -36,7 +37,8 @@ class UpdateReferral(BaseModel):
__properties: ClassVar[List[str]] = ["friendProfileIntegrationId", "startDate", "expiryDate", "usageLimit", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_referral_batch.py b/talon_one/models/update_referral_batch.py
index 644b79e..d7c35cd 100644
--- a/talon_one/models/update_referral_batch.py
+++ b/talon_one/models/update_referral_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateReferralBatch(BaseModel):
"""
@@ -36,7 +37,8 @@ class UpdateReferralBatch(BaseModel):
__properties: ClassVar[List[str]] = ["attributes", "batchID", "startDate", "expiryDate", "usageLimit"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -48,8 +50,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_role.py b/talon_one/models/update_role.py
index 6d3d716..153eceb 100644
--- a/talon_one/models/update_role.py
+++ b/talon_one/models/update_role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateRole(BaseModel):
"""
@@ -33,7 +34,8 @@ class UpdateRole(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "acl", "members"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_store.py b/talon_one/models/update_store.py
index d201482..fc256c0 100644
--- a/talon_one/models/update_store.py
+++ b/talon_one/models/update_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateStore(BaseModel):
"""
@@ -33,7 +34,8 @@ class UpdateStore(BaseModel):
__properties: ClassVar[List[str]] = ["name", "description", "attributes"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/update_user.py b/talon_one/models/update_user.py
index 032d334..08c006c 100644
--- a/talon_one/models/update_user.py
+++ b/talon_one/models/update_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UpdateUser(BaseModel):
"""
@@ -45,7 +46,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -57,8 +59,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/user.py b/talon_one/models/user.py
index 4e629c5..d2e9da5 100644
--- a/talon_one/models/user.py
+++ b/talon_one/models/user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class User(BaseModel):
"""
@@ -54,7 +55,8 @@ def state_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -66,8 +68,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/user_entity.py b/talon_one/models/user_entity.py
index 545527e..d913c35 100644
--- a/talon_one/models/user_entity.py
+++ b/talon_one/models/user_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class UserEntity(BaseModel):
"""
@@ -30,7 +31,8 @@ class UserEntity(BaseModel):
__properties: ClassVar[List[str]] = ["userId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/value_map.py b/talon_one/models/value_map.py
index ed83c0b..b358bd1 100644
--- a/talon_one/models/value_map.py
+++ b/talon_one/models/value_map.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing import Any, ClassVar, Dict, List, Optional
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class ValueMap(BaseModel):
"""
@@ -34,7 +35,8 @@ class ValueMap(BaseModel):
__properties: ClassVar[List[str]] = ["id", "created", "createdBy", "campaignId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -46,8 +48,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook.py b/talon_one/models/webhook.py
index 3b7f423..191f491 100644
--- a/talon_one/models/webhook.py
+++ b/talon_one/models/webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class Webhook(BaseModel):
"""
@@ -60,7 +61,8 @@ def verb_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -72,8 +74,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook_authentication.py b/talon_one/models/webhook_authentication.py
index e77862e..4a24364 100644
--- a/talon_one/models/webhook_authentication.py
+++ b/talon_one/models/webhook_authentication.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -23,6 +23,7 @@
from talon_one.models.webhook_authentication_webhook_ref import WebhookAuthenticationWebhookRef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WebhookAuthentication(BaseModel):
"""
@@ -47,7 +48,8 @@ def type_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -59,8 +61,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook_authentication_data_basic.py b/talon_one/models/webhook_authentication_data_basic.py
index 871997f..ee9d6de 100644
--- a/talon_one/models/webhook_authentication_data_basic.py
+++ b/talon_one/models/webhook_authentication_data_basic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WebhookAuthenticationDataBasic(BaseModel):
"""
@@ -31,7 +32,8 @@ class WebhookAuthenticationDataBasic(BaseModel):
__properties: ClassVar[List[str]] = ["username", "password"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -43,8 +45,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook_authentication_data_custom.py b/talon_one/models/webhook_authentication_data_custom.py
index 59d1158..081a8b0 100644
--- a/talon_one/models/webhook_authentication_data_custom.py
+++ b/talon_one/models/webhook_authentication_data_custom.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -21,6 +21,7 @@
from typing import Any, ClassVar, Dict, List
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WebhookAuthenticationDataCustom(BaseModel):
"""
@@ -30,7 +31,8 @@ class WebhookAuthenticationDataCustom(BaseModel):
__properties: ClassVar[List[str]] = ["headers"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -42,8 +44,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook_authentication_webhook_ref.py b/talon_one/models/webhook_authentication_webhook_ref.py
index 55e4c32..b9988b3 100644
--- a/talon_one/models/webhook_authentication_webhook_ref.py
+++ b/talon_one/models/webhook_authentication_webhook_ref.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WebhookAuthenticationWebhookRef(BaseModel):
"""
@@ -40,7 +41,8 @@ def title_validate_regular_expression(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -52,8 +54,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/webhook_with_outgoing_integration_details.py b/talon_one/models/webhook_with_outgoing_integration_details.py
index 87ebd7d..34ce8b6 100644
--- a/talon_one/models/webhook_with_outgoing_integration_details.py
+++ b/talon_one/models/webhook_with_outgoing_integration_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -24,6 +24,7 @@
from talon_one.models.template_arg_def import TemplateArgDef
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WebhookWithOutgoingIntegrationDetails(BaseModel):
"""
@@ -63,7 +64,8 @@ def verb_validate_enum(cls, value):
return value
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -75,8 +77,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/models/will_award_giveaway_effect_props.py b/talon_one/models/will_award_giveaway_effect_props.py
index 7e519ea..c901c5b 100644
--- a/talon_one/models/will_award_giveaway_effect_props.py
+++ b/talon_one/models/will_award_giveaway_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -22,6 +22,7 @@
from typing_extensions import Annotated
from typing import Optional, Set
from typing_extensions import Self
+from pydantic_core import to_jsonable_python
class WillAwardGiveawayEffectProps(BaseModel):
"""
@@ -33,7 +34,8 @@ class WillAwardGiveawayEffectProps(BaseModel):
__properties: ClassVar[List[str]] = ["poolId", "poolName", "recipientIntegrationId"]
model_config = ConfigDict(
- populate_by_name=True,
+ validate_by_name=True,
+ validate_by_alias=True,
validate_assignment=True,
protected_namespaces=(),
)
@@ -45,8 +47,7 @@ def to_str(self) -> str:
def to_json(self) -> str:
"""Returns the JSON representation of the model using alias"""
- # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
- return json.dumps(self.to_dict())
+ return json.dumps(to_jsonable_python(self.to_dict()))
@classmethod
def from_json(cls, json_str: str) -> Optional[Self]:
diff --git a/talon_one/rest.py b/talon_one/rest.py
index eb556ce..d5441fa 100644
--- a/talon_one/rest.py
+++ b/talon_one/rest.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_accept_coupon_effect_props.py b/test/test_accept_coupon_effect_props.py
index d97f61d..6ee5937 100644
--- a/test/test_accept_coupon_effect_props.py
+++ b/test/test_accept_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_accept_referral_effect_props.py b/test/test_accept_referral_effect_props.py
index 82562d2..5c93204 100644
--- a/test/test_accept_referral_effect_props.py
+++ b/test/test_accept_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_access_log_entry.py b/test/test_access_log_entry.py
index 89ef187..3c12ec8 100644
--- a/test/test_access_log_entry.py
+++ b/test/test_access_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account.py b/test/test_account.py
index fd0256f..72c2a7a 100644
--- a/test/test_account.py
+++ b/test/test_account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_additional_cost.py b/test/test_account_additional_cost.py
index 80dd793..9f2893a 100644
--- a/test/test_account_additional_cost.py
+++ b/test/test_account_additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_analytics.py b/test/test_account_analytics.py
index 1525645..eecab39 100644
--- a/test/test_account_analytics.py
+++ b/test/test_account_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic.py b/test/test_account_dashboard_statistic.py
index 14e1257..119493c 100644
--- a/test/test_account_dashboard_statistic.py
+++ b/test/test_account_dashboard_statistic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic_campaigns.py b/test/test_account_dashboard_statistic_campaigns.py
index 217916c..a34c8c5 100644
--- a/test/test_account_dashboard_statistic_campaigns.py
+++ b/test/test_account_dashboard_statistic_campaigns.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic_discount.py b/test/test_account_dashboard_statistic_discount.py
index e10b107..40d7c94 100644
--- a/test/test_account_dashboard_statistic_discount.py
+++ b/test/test_account_dashboard_statistic_discount.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic_loyalty_points.py b/test/test_account_dashboard_statistic_loyalty_points.py
index 8d9ffe2..14e4371 100644
--- a/test/test_account_dashboard_statistic_loyalty_points.py
+++ b/test/test_account_dashboard_statistic_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic_referrals.py b/test/test_account_dashboard_statistic_referrals.py
index 539a1be..8edf694 100644
--- a/test/test_account_dashboard_statistic_referrals.py
+++ b/test/test_account_dashboard_statistic_referrals.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_dashboard_statistic_revenue.py b/test/test_account_dashboard_statistic_revenue.py
index 58f6004..f600578 100644
--- a/test/test_account_dashboard_statistic_revenue.py
+++ b/test/test_account_dashboard_statistic_revenue.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_entity.py b/test/test_account_entity.py
index a9cf8c4..ddfb3a8 100644
--- a/test/test_account_entity.py
+++ b/test/test_account_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_account_limits.py b/test/test_account_limits.py
index 6c5542b..830a34c 100644
--- a/test/test_account_limits.py
+++ b/test/test_account_limits.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement.py b/test/test_achievement.py
index a5ee42c..01785b2 100644
--- a/test/test_achievement.py
+++ b/test/test_achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_additional_properties.py b/test/test_achievement_additional_properties.py
index 5e10ff1..d37d195 100644
--- a/test/test_achievement_additional_properties.py
+++ b/test/test_achievement_additional_properties.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_additional_properties_v2.py b/test/test_achievement_additional_properties_v2.py
index d8f7db2..fbe7413 100644
--- a/test/test_achievement_additional_properties_v2.py
+++ b/test/test_achievement_additional_properties_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_base.py b/test/test_achievement_base.py
index d031b37..5a4f503 100644
--- a/test/test_achievement_base.py
+++ b/test/test_achievement_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_base_v2.py b/test/test_achievement_base_v2.py
index f1da416..644cc79 100644
--- a/test/test_achievement_base_v2.py
+++ b/test/test_achievement_base_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_progress.py b/test/test_achievement_progress.py
index 505a5b3..d3229d0 100644
--- a/test/test_achievement_progress.py
+++ b/test/test_achievement_progress.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_progress_with_definition.py b/test/test_achievement_progress_with_definition.py
index d94fd44..6218e38 100644
--- a/test/test_achievement_progress_with_definition.py
+++ b/test/test_achievement_progress_with_definition.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_reference.py b/test/test_achievement_reference.py
index 0ffb444..fc412ec 100644
--- a/test/test_achievement_reference.py
+++ b/test/test_achievement_reference.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_status_entry.py b/test/test_achievement_status_entry.py
index 78a8106..04898de 100644
--- a/test/test_achievement_status_entry.py
+++ b/test/test_achievement_status_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_achievement_v2.py b/test/test_achievement_v2.py
index 82aaa3a..77d3e30 100644
--- a/test/test_achievement_v2.py
+++ b/test/test_achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_activate_loyalty_points.py b/test/test_activate_loyalty_points.py
index 3a535e9..5e2b325 100644
--- a/test/test_activate_loyalty_points.py
+++ b/test/test_activate_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -35,10 +35,8 @@ def make_instance(self, include_optional) -> ActivateLoyaltyPoints:
model = ActivateLoyaltyPoints()
if include_optional:
return ActivateLoyaltyPoints(
- transaction_uuids = [
- ''
- ],
- session_id = '0'
+ transaction_uuids = [8f1a8d7c-9c3e-4a5e-9f0d-2c5f7a3b1cde],
+ session_id = 'ac08cc3c43470426591ad75b2d685ec04_v2'
)
else:
return ActivateLoyaltyPoints(
diff --git a/test/test_activate_loyalty_points_response.py b/test/test_activate_loyalty_points_response.py
index f7ed659..180d518 100644
--- a/test/test_activate_loyalty_points_response.py
+++ b/test/test_activate_loyalty_points_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_activate_user_request.py b/test/test_activate_user_request.py
index 0e054e7..ae5ba10 100644
--- a/test/test_activate_user_request.py
+++ b/test/test_activate_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_free_item_effect_props.py b/test/test_add_free_item_effect_props.py
index ea4d9aa..b5d5e9e 100644
--- a/test/test_add_free_item_effect_props.py
+++ b/test/test_add_free_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_item_catalog_action.py b/test/test_add_item_catalog_action.py
index c9eaa87..e04980a 100644
--- a/test/test_add_item_catalog_action.py
+++ b/test/test_add_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_loyalty_points.py b/test/test_add_loyalty_points.py
index ed29b68..a228792 100644
--- a/test/test_add_loyalty_points.py
+++ b/test/test_add_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_loyalty_points_effect_props.py b/test/test_add_loyalty_points_effect_props.py
index d7e503d..ae222a1 100644
--- a/test/test_add_loyalty_points_effect_props.py
+++ b/test/test_add_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_price_adjustment_catalog_action.py b/test/test_add_price_adjustment_catalog_action.py
index cda9c28..4c50515 100644
--- a/test/test_add_price_adjustment_catalog_action.py
+++ b/test/test_add_price_adjustment_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_add_to_audience_effect_props.py b/test/test_add_to_audience_effect_props.py
index d0c70a6..e970086 100644
--- a/test/test_add_to_audience_effect_props.py
+++ b/test/test_add_to_audience_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_added_deducted_points_balances_action.py b/test/test_added_deducted_points_balances_action.py
index c5da8b6..4b1d4e1 100644
--- a/test/test_added_deducted_points_balances_action.py
+++ b/test/test_added_deducted_points_balances_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_added_deducted_points_balances_notification.py b/test/test_added_deducted_points_balances_notification.py
index c36d66c..ee47996 100644
--- a/test/test_added_deducted_points_balances_notification.py
+++ b/test/test_added_deducted_points_balances_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_added_deducted_points_balances_notification_policy.py b/test/test_added_deducted_points_balances_notification_policy.py
index 0cd5b32..7cd480e 100644
--- a/test/test_added_deducted_points_balances_notification_policy.py
+++ b/test/test_added_deducted_points_balances_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_added_deducted_points_notification.py b/test/test_added_deducted_points_notification.py
index 4624d82..53a22bf 100644
--- a/test/test_added_deducted_points_notification.py
+++ b/test/test_added_deducted_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_added_deducted_points_notification_policy.py b/test/test_added_deducted_points_notification_policy.py
index 731818b..f3b0a54 100644
--- a/test/test_added_deducted_points_notification_policy.py
+++ b/test/test_added_deducted_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_additional_campaign_properties.py b/test/test_additional_campaign_properties.py
index c7f7d87..585778e 100644
--- a/test/test_additional_campaign_properties.py
+++ b/test/test_additional_campaign_properties.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_additional_cost.py b/test/test_additional_cost.py
index b6012f8..f820112 100644
--- a/test/test_additional_cost.py
+++ b/test/test_additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_adjustment_details.py b/test/test_adjustment_details.py
index 86c76d8..7cd642e 100644
--- a/test/test_adjustment_details.py
+++ b/test/test_adjustment_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_data_point.py b/test/test_analytics_data_point.py
index 3fb280f..d0589c4 100644
--- a/test/test_analytics_data_point.py
+++ b/test/test_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_data_point_with_trend.py b/test/test_analytics_data_point_with_trend.py
index 5d21357..c096f3c 100644
--- a/test/test_analytics_data_point_with_trend.py
+++ b/test/test_analytics_data_point_with_trend.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_data_point_with_trend_and_influenced_rate.py b/test/test_analytics_data_point_with_trend_and_influenced_rate.py
index 641786e..b326037 100644
--- a/test/test_analytics_data_point_with_trend_and_influenced_rate.py
+++ b/test/test_analytics_data_point_with_trend_and_influenced_rate.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_data_point_with_trend_and_uplift.py b/test/test_analytics_data_point_with_trend_and_uplift.py
index ecf04b2..418f50d 100644
--- a/test/test_analytics_data_point_with_trend_and_uplift.py
+++ b/test/test_analytics_data_point_with_trend_and_uplift.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_product.py b/test/test_analytics_product.py
index 1a5d018..1a67472 100644
--- a/test/test_analytics_product.py
+++ b/test/test_analytics_product.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_analytics_sku.py b/test/test_analytics_sku.py
index 0167286..56feeb9 100644
--- a/test/test_analytics_sku.py
+++ b/test/test_analytics_sku.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_api_error.py b/test/test_api_error.py
index 9052f77..fe6172a 100644
--- a/test/test_api_error.py
+++ b/test/test_api_error.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application.py b/test/test_application.py
index d2999a4..7bf8d33 100644
--- a/test/test_application.py
+++ b/test/test_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_analytics_data_point.py b/test/test_application_analytics_data_point.py
index 119f058..1c52894 100644
--- a/test/test_application_analytics_data_point.py
+++ b/test/test_application_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_api_health.py b/test/test_application_api_health.py
index b9ef458..f0d6da9 100644
--- a/test/test_application_api_health.py
+++ b/test/test_application_api_health.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_api_key.py b/test/test_application_api_key.py
index c732604..bec67cd 100644
--- a/test/test_application_api_key.py
+++ b/test/test_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_campaign_analytics.py b/test/test_application_campaign_analytics.py
index 938fd59..1a14919 100644
--- a/test/test_application_campaign_analytics.py
+++ b/test/test_application_campaign_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_campaign_stats.py b/test/test_application_campaign_stats.py
index c98c300..e6ad715 100644
--- a/test/test_application_campaign_stats.py
+++ b/test/test_application_campaign_stats.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_cif.py b/test/test_application_cif.py
index d7dfac1..c59aea5 100644
--- a/test/test_application_cif.py
+++ b/test/test_application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_cif_expression.py b/test/test_application_cif_expression.py
index b3de83e..ed24e15 100644
--- a/test/test_application_cif_expression.py
+++ b/test/test_application_cif_expression.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_cif_references.py b/test/test_application_cif_references.py
index fdeafb9..317c824 100644
--- a/test/test_application_cif_references.py
+++ b/test/test_application_cif_references.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_customer.py b/test/test_application_customer.py
index 580dd08..d6d8bac 100644
--- a/test/test_application_customer.py
+++ b/test/test_application_customer.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_customer_entity.py b/test/test_application_customer_entity.py
index 9cfa0f4..25e04b5 100644
--- a/test/test_application_customer_entity.py
+++ b/test/test_application_customer_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_entity.py b/test/test_application_entity.py
index 53ed83b..c651102 100644
--- a/test/test_application_entity.py
+++ b/test/test_application_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_event.py b/test/test_application_event.py
index d9a8687..9f89d85 100644
--- a/test/test_application_event.py
+++ b/test/test_application_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_notification.py b/test/test_application_notification.py
index 171e0cc..95d1974 100644
--- a/test/test_application_notification.py
+++ b/test/test_application_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_referee.py b/test/test_application_referee.py
index 752d0c7..9fe198e 100644
--- a/test/test_application_referee.py
+++ b/test/test_application_referee.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_session.py b/test/test_application_session.py
index f3e3b6b..ddcbf1d 100644
--- a/test/test_application_session.py
+++ b/test/test_application_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_session_entity.py b/test/test_application_session_entity.py
index e6e480a..364cb61 100644
--- a/test/test_application_session_entity.py
+++ b/test/test_application_session_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_application_store_entity.py b/test/test_application_store_entity.py
index d02c7f0..772434f 100644
--- a/test/test_application_store_entity.py
+++ b/test/test_application_store_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_async_coupon_creation_response.py b/test/test_async_coupon_creation_response.py
index 0fac936..b3dff7d 100644
--- a/test/test_async_coupon_creation_response.py
+++ b/test/test_async_coupon_creation_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_async_coupon_deletion_job_response.py b/test/test_async_coupon_deletion_job_response.py
index 878df2f..07d3125 100644
--- a/test/test_async_coupon_deletion_job_response.py
+++ b/test/test_async_coupon_deletion_job_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_async_coupons_data.py b/test/test_async_coupons_data.py
index b4a644b..3e358a4 100644
--- a/test/test_async_coupons_data.py
+++ b/test/test_async_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_attribute.py b/test/test_attribute.py
index 5fbae9b..00508d6 100644
--- a/test/test_attribute.py
+++ b/test/test_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_attributes_mandatory.py b/test/test_attributes_mandatory.py
index 4b8b710..569831a 100644
--- a/test/test_attributes_mandatory.py
+++ b/test/test_attributes_mandatory.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_attributes_settings.py b/test/test_attributes_settings.py
index 458b5d7..99477cc 100644
--- a/test/test_attributes_settings.py
+++ b/test/test_attributes_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience.py b/test/test_audience.py
index dd2941c..de8009f 100644
--- a/test/test_audience.py
+++ b/test/test_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience_analytics.py b/test/test_audience_analytics.py
index 874887c..a42cfe6 100644
--- a/test/test_audience_analytics.py
+++ b/test/test_audience_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience_customer.py b/test/test_audience_customer.py
index 6eca6dc..24bd619 100644
--- a/test/test_audience_customer.py
+++ b/test/test_audience_customer.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience_integration_id.py b/test/test_audience_integration_id.py
index aba1586..8fb026f 100644
--- a/test/test_audience_integration_id.py
+++ b/test/test_audience_integration_id.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience_membership.py b/test/test_audience_membership.py
index e4cf67a..8013d40 100644
--- a/test/test_audience_membership.py
+++ b/test/test_audience_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_audience_reference.py b/test/test_audience_reference.py
index c24acca..ff1990c 100644
--- a/test/test_audience_reference.py
+++ b/test/test_audience_reference.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_award_giveaway_effect_props.py b/test/test_award_giveaway_effect_props.py
index 628b811..fcf95ae 100644
--- a/test/test_award_giveaway_effect_props.py
+++ b/test/test_award_giveaway_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_campaign.py b/test/test_base_campaign.py
index e22186f..4d426b3 100644
--- a/test/test_base_campaign.py
+++ b/test/test_base_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -60,7 +60,8 @@ def make_instance(self, include_optional) -> BaseCampaign:
],
campaign_groups = [1, 3],
type = 'advanced',
- linked_store_ids = [1, 2, 3]
+ linked_store_ids = [1, 2, 3],
+ coupon_attributes = None
)
else:
return BaseCampaign(
diff --git a/test/test_base_loyalty_program.py b/test/test_base_loyalty_program.py
index 6b6ad7b..c59668c 100644
--- a/test/test_base_loyalty_program.py
+++ b/test/test_base_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_notification.py b/test/test_base_notification.py
index 9c7001e..d269232 100644
--- a/test/test_base_notification.py
+++ b/test/test_base_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_notification_entity.py b/test/test_base_notification_entity.py
index 00f08eb..5521698 100644
--- a/test/test_base_notification_entity.py
+++ b/test/test_base_notification_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_notification_webhook.py b/test/test_base_notification_webhook.py
index 7eec4d0..d79f6c5 100644
--- a/test/test_base_notification_webhook.py
+++ b/test/test_base_notification_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_notifications.py b/test/test_base_notifications.py
index b2d8ff4..ba348af 100644
--- a/test/test_base_notifications.py
+++ b/test/test_base_notifications.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_base_saml_connection.py b/test/test_base_saml_connection.py
index 8a25523..c06d496 100644
--- a/test/test_base_saml_connection.py
+++ b/test/test_base_saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_best_prior_price.py b/test/test_best_prior_price.py
index 225b561..4a1f652 100644
--- a/test/test_best_prior_price.py
+++ b/test/test_best_prior_price.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_best_prior_price_metadata.py b/test/test_best_prior_price_metadata.py
index 5311d9c..0a97608 100644
--- a/test/test_best_prior_price_metadata.py
+++ b/test/test_best_prior_price_metadata.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_best_prior_price_request.py b/test/test_best_prior_price_request.py
index 94028a6..622b954 100644
--- a/test/test_best_prior_price_request.py
+++ b/test/test_best_prior_price_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_best_prior_target.py b/test/test_best_prior_target.py
index 8e46815..8d6a8f7 100644
--- a/test/test_best_prior_target.py
+++ b/test/test_best_prior_target.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_binding.py b/test/test_binding.py
index bc6eb45..d7392f5 100644
--- a/test/test_binding.py
+++ b/test/test_binding.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_blueprint.py b/test/test_blueprint.py
index 38c521a..aec6b4e 100644
--- a/test/test_blueprint.py
+++ b/test/test_blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_bulk_application_notification.py b/test/test_bulk_application_notification.py
index 30d4856..7b97b1b 100644
--- a/test/test_bulk_application_notification.py
+++ b/test/test_bulk_application_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_bulk_operation_on_campaigns.py b/test/test_bulk_operation_on_campaigns.py
index 85adf7d..d3919a4 100644
--- a/test/test_bulk_operation_on_campaigns.py
+++ b/test/test_bulk_operation_on_campaigns.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign.py b/test/test_campaign.py
index a0fb463..6243a68 100644
--- a/test/test_campaign.py
+++ b/test/test_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -65,6 +65,7 @@ def make_instance(self, include_optional) -> Campaign:
campaign_groups = [1, 3],
type = 'advanced',
linked_store_ids = [1, 2, 3],
+ coupon_attributes = talon_one.models.coupon_attributes.couponAttributes(),
budgets = [
talon_one.models.campaign_budget.CampaignBudget(
action = 'createCoupon',
diff --git a/test/test_campaign_activation_request.py b/test/test_campaign_activation_request.py
index 4af9d63..5216ed2 100644
--- a/test/test_campaign_activation_request.py
+++ b/test/test_campaign_activation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_analytics.py b/test/test_campaign_analytics.py
index a26f6e4..456512c 100644
--- a/test/test_campaign_analytics.py
+++ b/test/test_campaign_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_budget.py b/test/test_campaign_budget.py
index 6f59c0b..299fd9d 100644
--- a/test/test_campaign_budget.py
+++ b/test/test_campaign_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_collection.py b/test/test_campaign_collection.py
index 90367cc..849412f 100644
--- a/test/test_campaign_collection.py
+++ b/test/test_campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_collection_edited_notification.py b/test/test_campaign_collection_edited_notification.py
index abaca9f..d9d6f75 100644
--- a/test/test_campaign_collection_edited_notification.py
+++ b/test/test_campaign_collection_edited_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_collection_edited_notification_item.py b/test/test_campaign_collection_edited_notification_item.py
index f9f6946..48a026e 100644
--- a/test/test_campaign_collection_edited_notification_item.py
+++ b/test/test_campaign_collection_edited_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_collection_without_payload.py b/test/test_campaign_collection_without_payload.py
index 24f5857..7642705 100644
--- a/test/test_campaign_collection_without_payload.py
+++ b/test/test_campaign_collection_without_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_copy.py b/test/test_campaign_copy.py
index 9469ebd..384264e 100644
--- a/test/test_campaign_copy.py
+++ b/test/test_campaign_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_created_notification.py b/test/test_campaign_created_notification.py
index d6f1e69..859cce3 100644
--- a/test/test_campaign_created_notification.py
+++ b/test/test_campaign_created_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_created_notification_item.py b/test/test_campaign_created_notification_item.py
index 4379f48..c7ef809 100644
--- a/test/test_campaign_created_notification_item.py
+++ b/test/test_campaign_created_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_deactivation_request.py b/test/test_campaign_deactivation_request.py
index af3c508..b63918e 100644
--- a/test/test_campaign_deactivation_request.py
+++ b/test/test_campaign_deactivation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_deleted_notification.py b/test/test_campaign_deleted_notification.py
index 4ed8a3c..6c004cc 100644
--- a/test/test_campaign_deleted_notification.py
+++ b/test/test_campaign_deleted_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_deleted_notification_item.py b/test/test_campaign_deleted_notification_item.py
index 8ad36f2..3f8c004 100644
--- a/test/test_campaign_deleted_notification_item.py
+++ b/test/test_campaign_deleted_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_detail.py b/test/test_campaign_detail.py
index d7d62ba..9ac4f15 100644
--- a/test/test_campaign_detail.py
+++ b/test/test_campaign_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_edited_notification.py b/test/test_campaign_edited_notification.py
index 2e9ed40..1c27d8c 100644
--- a/test/test_campaign_edited_notification.py
+++ b/test/test_campaign_edited_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_edited_notification_item.py b/test/test_campaign_edited_notification_item.py
index 0b6756f..90391e4 100644
--- a/test/test_campaign_edited_notification_item.py
+++ b/test/test_campaign_edited_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_entity.py b/test/test_campaign_entity.py
index 20097a9..13baa4e 100644
--- a/test/test_campaign_entity.py
+++ b/test/test_campaign_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_evaluation_group.py b/test/test_campaign_evaluation_group.py
index bc2bbc5..2fe18f1 100644
--- a/test/test_campaign_evaluation_group.py
+++ b/test/test_campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_evaluation_position.py b/test/test_campaign_evaluation_position.py
index 3fedfc3..25c858c 100644
--- a/test/test_campaign_evaluation_position.py
+++ b/test/test_campaign_evaluation_position.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_evaluation_tree_changed_message.py b/test/test_campaign_evaluation_tree_changed_message.py
index 94de817..69bbc42 100644
--- a/test/test_campaign_evaluation_tree_changed_message.py
+++ b/test/test_campaign_evaluation_tree_changed_message.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_evaluation_tree_changed_notification.py b/test/test_campaign_evaluation_tree_changed_notification.py
index 4796b16..027f3e9 100644
--- a/test/test_campaign_evaluation_tree_changed_notification.py
+++ b/test/test_campaign_evaluation_tree_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_group.py b/test/test_campaign_group.py
index bd25ac1..aabc7c7 100644
--- a/test/test_campaign_group.py
+++ b/test/test_campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_group_entity.py b/test/test_campaign_group_entity.py
index f74810e..68b83fc 100644
--- a/test/test_campaign_group_entity.py
+++ b/test/test_campaign_group_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_log_summary.py b/test/test_campaign_log_summary.py
index 1bf2a7a..35d644e 100644
--- a/test/test_campaign_log_summary.py
+++ b/test/test_campaign_log_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_notification_base.py b/test/test_campaign_notification_base.py
index 574a6f1..9ca6b91 100644
--- a/test/test_campaign_notification_base.py
+++ b/test/test_campaign_notification_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_notification_generic.py b/test/test_campaign_notification_generic.py
index 175ec39..8b0889d 100644
--- a/test/test_campaign_notification_generic.py
+++ b/test/test_campaign_notification_generic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_notification_item_base.py b/test/test_campaign_notification_item_base.py
index b27e60a..c38f6d1 100644
--- a/test/test_campaign_notification_item_base.py
+++ b/test/test_campaign_notification_item_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_notification_policy.py b/test/test_campaign_notification_policy.py
index 8bfa11c..025f984 100644
--- a/test/test_campaign_notification_policy.py
+++ b/test/test_campaign_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_ruleset_changed_notification.py b/test/test_campaign_ruleset_changed_notification.py
index 8e07546..e2cd770 100644
--- a/test/test_campaign_ruleset_changed_notification.py
+++ b/test/test_campaign_ruleset_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_ruleset_changed_notification_item.py b/test/test_campaign_ruleset_changed_notification_item.py
index 07a4418..3212d4d 100644
--- a/test/test_campaign_ruleset_changed_notification_item.py
+++ b/test/test_campaign_ruleset_changed_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_search.py b/test/test_campaign_search.py
index ccd8647..a7ae586 100644
--- a/test/test_campaign_search.py
+++ b/test/test_campaign_search.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_set.py b/test/test_campaign_set.py
index 3f8054f..cf59436 100644
--- a/test/test_campaign_set.py
+++ b/test/test_campaign_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_set_branch_node.py b/test/test_campaign_set_branch_node.py
index 4f48844..2a73fb1 100644
--- a/test/test_campaign_set_branch_node.py
+++ b/test/test_campaign_set_branch_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_set_leaf_node.py b/test/test_campaign_set_leaf_node.py
index c25f0e3..e5449ef 100644
--- a/test/test_campaign_set_leaf_node.py
+++ b/test/test_campaign_set_leaf_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_set_node.py b/test/test_campaign_set_node.py
index d23fefa..7255650 100644
--- a/test/test_campaign_set_node.py
+++ b/test/test_campaign_set_node.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_state_changed_notification.py b/test/test_campaign_state_changed_notification.py
index 55bc147..fc591b8 100644
--- a/test/test_campaign_state_changed_notification.py
+++ b/test/test_campaign_state_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_state_changed_notification_item.py b/test/test_campaign_state_changed_notification_item.py
index d3f3ccf..cb0f415 100644
--- a/test/test_campaign_state_changed_notification_item.py
+++ b/test/test_campaign_state_changed_notification_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_store_budget.py b/test/test_campaign_store_budget.py
index fe7c7dd..8dcb1a4 100644
--- a/test/test_campaign_store_budget.py
+++ b/test/test_campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_store_budget_limit_config.py b/test/test_campaign_store_budget_limit_config.py
index 596fef9..52663fe 100644
--- a/test/test_campaign_store_budget_limit_config.py
+++ b/test/test_campaign_store_budget_limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_template.py b/test/test_campaign_template.py
index c0f72d3..aecccaa 100644
--- a/test/test_campaign_template.py
+++ b/test/test_campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_template_collection.py b/test/test_campaign_template_collection.py
index 6a7231f..a4e8b7d 100644
--- a/test/test_campaign_template_collection.py
+++ b/test/test_campaign_template_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_template_coupon_reservation_settings.py b/test/test_campaign_template_coupon_reservation_settings.py
index 63b75cb..6664315 100644
--- a/test/test_campaign_template_coupon_reservation_settings.py
+++ b/test/test_campaign_template_coupon_reservation_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_template_params.py b/test/test_campaign_template_params.py
index 17707b4..a510caa 100644
--- a/test/test_campaign_template_params.py
+++ b/test/test_campaign_template_params.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_campaign_versions.py b/test/test_campaign_versions.py
index 2468f87..4f1711f 100644
--- a/test/test_campaign_versions.py
+++ b/test/test_campaign_versions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_added_deducted_points_balances_notification.py b/test/test_card_added_deducted_points_balances_notification.py
index 01770f1..0182d38 100644
--- a/test/test_card_added_deducted_points_balances_notification.py
+++ b/test/test_card_added_deducted_points_balances_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_added_deducted_points_balances_notification_policy.py b/test/test_card_added_deducted_points_balances_notification_policy.py
index 842d071..fd604b8 100644
--- a/test/test_card_added_deducted_points_balances_notification_policy.py
+++ b/test/test_card_added_deducted_points_balances_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_added_deducted_points_notification.py b/test/test_card_added_deducted_points_notification.py
index c74c22d..430df26 100644
--- a/test/test_card_added_deducted_points_notification.py
+++ b/test/test_card_added_deducted_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_added_deducted_points_notification_policy.py b/test/test_card_added_deducted_points_notification_policy.py
index 94a8d99..53419f0 100644
--- a/test/test_card_added_deducted_points_notification_policy.py
+++ b/test/test_card_added_deducted_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_expiring_points_notification_policy.py b/test/test_card_expiring_points_notification_policy.py
index 6fa6470..34842c5 100644
--- a/test/test_card_expiring_points_notification_policy.py
+++ b/test/test_card_expiring_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_expiring_points_notification_trigger.py b/test/test_card_expiring_points_notification_trigger.py
index 9a46dec..f233f27 100644
--- a/test/test_card_expiring_points_notification_trigger.py
+++ b/test/test_card_expiring_points_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_ledger_points_entry_integration_api.py b/test/test_card_ledger_points_entry_integration_api.py
index 99f9626..3adbaa7 100644
--- a/test/test_card_ledger_points_entry_integration_api.py
+++ b/test/test_card_ledger_points_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_ledger_transaction_log_entry.py b/test/test_card_ledger_transaction_log_entry.py
index fbb2112..bba8568 100644
--- a/test/test_card_ledger_transaction_log_entry.py
+++ b/test/test_card_ledger_transaction_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_card_ledger_transaction_log_entry_integration_api.py b/test/test_card_ledger_transaction_log_entry_integration_api.py
index e354f6c..23db292 100644
--- a/test/test_card_ledger_transaction_log_entry_integration_api.py
+++ b/test/test_card_ledger_transaction_log_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_cart_item.py b/test/test_cart_item.py
index 646a105..135334b 100644
--- a/test/test_cart_item.py
+++ b/test/test_cart_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_cart_item_filter_template.py b/test/test_cart_item_filter_template.py
index f38c1e8..95cb0ef 100644
--- a/test/test_cart_item_filter_template.py
+++ b/test/test_cart_item_filter_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalog.py b/test/test_catalog.py
index 7d319ab..110e2dc 100644
--- a/test/test_catalog.py
+++ b/test/test_catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalog_action_filter.py b/test/test_catalog_action_filter.py
index a2eb661..6e6b6ba 100644
--- a/test/test_catalog_action_filter.py
+++ b/test/test_catalog_action_filter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalog_item.py b/test/test_catalog_item.py
index f985e0c..b56ec22 100644
--- a/test/test_catalog_item.py
+++ b/test/test_catalog_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalog_rule.py b/test/test_catalog_rule.py
index efc88c0..714eeef 100644
--- a/test/test_catalog_rule.py
+++ b/test/test_catalog_rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalog_sync_request.py b/test/test_catalog_sync_request.py
index 44085ec..4e8e878 100644
--- a/test/test_catalog_sync_request.py
+++ b/test/test_catalog_sync_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_catalogs_strikethrough_notification_policy.py b/test/test_catalogs_strikethrough_notification_policy.py
index 55029a8..2f8ddc8 100644
--- a/test/test_catalogs_strikethrough_notification_policy.py
+++ b/test/test_catalogs_strikethrough_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_change.py b/test/test_change.py
index 5c3507a..b71a0bc 100644
--- a/test/test_change.py
+++ b/test/test_change.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_change_loyalty_tier_level_effect_props.py b/test/test_change_loyalty_tier_level_effect_props.py
index ca64e51..a3823bc 100644
--- a/test/test_change_loyalty_tier_level_effect_props.py
+++ b/test/test_change_loyalty_tier_level_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_change_profile_password.py b/test/test_change_profile_password.py
index 716a976..d6d1ee1 100644
--- a/test/test_change_profile_password.py
+++ b/test/test_change_profile_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_code_generator_settings.py b/test/test_code_generator_settings.py
index e464f7a..43d2b91 100644
--- a/test/test_code_generator_settings.py
+++ b/test/test_code_generator_settings.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_collection.py b/test/test_collection.py
index 10ce41a..9c6a2c0 100644
--- a/test/test_collection.py
+++ b/test/test_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_collection_item.py b/test/test_collection_item.py
index 68b7a9d..7e16d3f 100644
--- a/test/test_collection_item.py
+++ b/test/test_collection_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_collection_without_payload.py b/test/test_collection_without_payload.py
index 479fe2c..fb16cd1 100644
--- a/test/test_collection_without_payload.py
+++ b/test/test_collection_without_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon.py b/test/test_coupon.py
index 152ec5f..dd97e6f 100644
--- a/test/test_coupon.py
+++ b/test/test_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_constraints.py b/test/test_coupon_constraints.py
index 9ee429e..8e12c7b 100644
--- a/test/test_coupon_constraints.py
+++ b/test/test_coupon_constraints.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_created_effect_props.py b/test/test_coupon_created_effect_props.py
index 809547c..33d9861 100644
--- a/test/test_coupon_created_effect_props.py
+++ b/test/test_coupon_created_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_creation_job.py b/test/test_coupon_creation_job.py
index 1175000..b6beb48 100644
--- a/test/test_coupon_creation_job.py
+++ b/test/test_coupon_creation_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_deletion_filters.py b/test/test_coupon_deletion_filters.py
index 36d961e..67cce30 100644
--- a/test/test_coupon_deletion_filters.py
+++ b/test/test_coupon_deletion_filters.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_deletion_job.py b/test/test_coupon_deletion_job.py
index 41d544b..619fd2b 100644
--- a/test/test_coupon_deletion_job.py
+++ b/test/test_coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_entity.py b/test/test_coupon_entity.py
index 4d99492..2aa5d0f 100644
--- a/test/test_coupon_entity.py
+++ b/test/test_coupon_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_failure_summary.py b/test/test_coupon_failure_summary.py
index 3b2f3d8..a33f058 100644
--- a/test/test_coupon_failure_summary.py
+++ b/test/test_coupon_failure_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_limit_configs.py b/test/test_coupon_limit_configs.py
index eb2e160..0ac25d9 100644
--- a/test/test_coupon_limit_configs.py
+++ b/test/test_coupon_limit_configs.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_rejection_reason.py b/test/test_coupon_rejection_reason.py
index 3a738ea..ac1b183 100644
--- a/test/test_coupon_rejection_reason.py
+++ b/test/test_coupon_rejection_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_reservations.py b/test/test_coupon_reservations.py
index 9c77400..9cf9c9e 100644
--- a/test/test_coupon_reservations.py
+++ b/test/test_coupon_reservations.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_search.py b/test/test_coupon_search.py
index 91f9920..6a40b4e 100644
--- a/test/test_coupon_search.py
+++ b/test/test_coupon_search.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_value.py b/test/test_coupon_value.py
index f5f1a24..207b30b 100644
--- a/test/test_coupon_value.py
+++ b/test/test_coupon_value.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupon_with_application.py b/test/test_coupon_with_application.py
index b7c8271..795ec7e 100644
--- a/test/test_coupon_with_application.py
+++ b/test/test_coupon_with_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupons_notification_data.py b/test/test_coupons_notification_data.py
index a0bfec3..d055ffa 100644
--- a/test/test_coupons_notification_data.py
+++ b/test/test_coupons_notification_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_coupons_notification_policy.py b/test/test_coupons_notification_policy.py
index c40be0f..e2ebe4e 100644
--- a/test/test_coupons_notification_policy.py
+++ b/test/test_coupons_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_achievement.py b/test/test_create_achievement.py
index 460349b..48b1e32 100644
--- a/test/test_create_achievement.py
+++ b/test/test_create_achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_achievement_v2.py b/test/test_create_achievement_v2.py
index 58cd593..5c4b417 100644
--- a/test/test_create_achievement_v2.py
+++ b/test/test_create_achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_application_api_key.py b/test/test_create_application_api_key.py
index 088d440..c3ad0f5 100644
--- a/test/test_create_application_api_key.py
+++ b/test/test_create_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_coupon_data.py b/test/test_create_coupon_data.py
index 3178daa..935d25a 100644
--- a/test/test_create_coupon_data.py
+++ b/test/test_create_coupon_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_coupons200_response.py b/test/test_create_coupons200_response.py
index f7a5d24..896d741 100644
--- a/test/test_create_coupons200_response.py
+++ b/test/test_create_coupons200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_management_key.py b/test/test_create_management_key.py
index c1d83c2..448ac58 100644
--- a/test/test_create_management_key.py
+++ b/test/test_create_management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_referrals_for_multiple_advocates201_response.py b/test/test_create_referrals_for_multiple_advocates201_response.py
index 5ffccec..a04e390 100644
--- a/test/test_create_referrals_for_multiple_advocates201_response.py
+++ b/test/test_create_referrals_for_multiple_advocates201_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_template_campaign.py b/test/test_create_template_campaign.py
index 47a85eb..8177e62 100644
--- a/test/test_create_template_campaign.py
+++ b/test/test_create_template_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_create_template_campaign_response.py b/test/test_create_template_campaign_response.py
index 4e9c5f7..d717cac 100644
--- a/test/test_create_template_campaign_response.py
+++ b/test/test_create_template_campaign_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_custom_effect.py b/test/test_custom_effect.py
index 4564a9f..eb6e5da 100644
--- a/test/test_custom_effect.py
+++ b/test/test_custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_custom_effect_props.py b/test/test_custom_effect_props.py
index 491e0ec..21f7738 100644
--- a/test/test_custom_effect_props.py
+++ b/test/test_custom_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_activity_report.py b/test/test_customer_activity_report.py
index a876fc8..6335fc7 100644
--- a/test/test_customer_activity_report.py
+++ b/test/test_customer_activity_report.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_analytics.py b/test/test_customer_analytics.py
index 741ef89..b3f8dd1 100644
--- a/test/test_customer_analytics.py
+++ b/test/test_customer_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_inventory.py b/test/test_customer_inventory.py
index e899a20..8201202 100644
--- a/test/test_customer_inventory.py
+++ b/test/test_customer_inventory.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile.py b/test/test_customer_profile.py
index 2a864f7..773e3fe 100644
--- a/test/test_customer_profile.py
+++ b/test/test_customer_profile.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_audience_request.py b/test/test_customer_profile_audience_request.py
index 2aa2a7c..ba671e7 100644
--- a/test/test_customer_profile_audience_request.py
+++ b/test/test_customer_profile_audience_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_audience_request_item.py b/test/test_customer_profile_audience_request_item.py
index bca0e1c..7191060 100644
--- a/test/test_customer_profile_audience_request_item.py
+++ b/test/test_customer_profile_audience_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_entity.py b/test/test_customer_profile_entity.py
index f2deee0..b9f506a 100644
--- a/test/test_customer_profile_entity.py
+++ b/test/test_customer_profile_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_integration_request_v2.py b/test/test_customer_profile_integration_request_v2.py
index d1b85dc..3962898 100644
--- a/test/test_customer_profile_integration_request_v2.py
+++ b/test/test_customer_profile_integration_request_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_integration_response_v2.py b/test/test_customer_profile_integration_response_v2.py
index 9eb28bd..ba7a709 100644
--- a/test/test_customer_profile_integration_response_v2.py
+++ b/test/test_customer_profile_integration_response_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_search_query.py b/test/test_customer_profile_search_query.py
index 85b8023..708e827 100644
--- a/test/test_customer_profile_search_query.py
+++ b/test/test_customer_profile_search_query.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_profile_update_v2_response.py b/test/test_customer_profile_update_v2_response.py
index ed87bc6..1a3e025 100644
--- a/test/test_customer_profile_update_v2_response.py
+++ b/test/test_customer_profile_update_v2_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_session.py b/test/test_customer_session.py
index 292f606..7bbf94f 100644
--- a/test/test_customer_session.py
+++ b/test/test_customer_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_customer_session_v2.py b/test/test_customer_session_v2.py
index feb3a85..5ead26f 100644
--- a/test/test_customer_session_v2.py
+++ b/test/test_customer_session_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_deactivate_user_request.py b/test/test_deactivate_user_request.py
index aa3565a..0e31710 100644
--- a/test/test_deactivate_user_request.py
+++ b/test/test_deactivate_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_deduct_loyalty_points.py b/test/test_deduct_loyalty_points.py
index 22fbcd3..1ccd8ba 100644
--- a/test/test_deduct_loyalty_points.py
+++ b/test/test_deduct_loyalty_points.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_deduct_loyalty_points_effect_props.py b/test/test_deduct_loyalty_points_effect_props.py
index e4618a8..c7e2502 100644
--- a/test/test_deduct_loyalty_points_effect_props.py
+++ b/test/test_deduct_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_delete_coupons_data.py b/test/test_delete_coupons_data.py
index cdd6e48..005c811 100644
--- a/test/test_delete_coupons_data.py
+++ b/test/test_delete_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_delete_loyalty_transactions_request.py b/test/test_delete_loyalty_transactions_request.py
index dbe8fd6..b3153da 100644
--- a/test/test_delete_loyalty_transactions_request.py
+++ b/test/test_delete_loyalty_transactions_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_delete_user_request.py b/test/test_delete_user_request.py
index 1665179..fff9a8f 100644
--- a/test/test_delete_user_request.py
+++ b/test/test_delete_user_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_effect.py b/test/test_effect.py
index 277deaf..69e83f6 100644
--- a/test/test_effect.py
+++ b/test/test_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_effect_entity.py b/test/test_effect_entity.py
index 9f45106..16b368b 100644
--- a/test/test_effect_entity.py
+++ b/test/test_effect_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_email_entity.py b/test/test_email_entity.py
index 8cdd611..4fd51b3 100644
--- a/test/test_email_entity.py
+++ b/test/test_email_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_embedded_analytics_configuration.py b/test/test_embedded_analytics_configuration.py
new file mode 100644
index 0000000..ded2050
--- /dev/null
+++ b/test/test_embedded_analytics_configuration.py
@@ -0,0 +1,54 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.embedded_analytics_configuration import EmbeddedAnalyticsConfiguration
+
+class TestEmbeddedAnalyticsConfiguration(unittest.TestCase):
+ """EmbeddedAnalyticsConfiguration unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> EmbeddedAnalyticsConfiguration:
+ """Test EmbeddedAnalyticsConfiguration
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `EmbeddedAnalyticsConfiguration`
+ """
+ model = EmbeddedAnalyticsConfiguration()
+ if include_optional:
+ return EmbeddedAnalyticsConfiguration(
+ dashboards = talon_one.models.embedded_analytics_configuration_dashboards.EmbeddedAnalyticsConfiguration_dashboards(
+ campaign_insights = null, )
+ )
+ else:
+ return EmbeddedAnalyticsConfiguration(
+ dashboards = talon_one.models.embedded_analytics_configuration_dashboards.EmbeddedAnalyticsConfiguration_dashboards(
+ campaign_insights = null, ),
+ )
+ """
+
+ def testEmbeddedAnalyticsConfiguration(self):
+ """Test EmbeddedAnalyticsConfiguration"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_embedded_analytics_configuration_dashboards.py b/test/test_embedded_analytics_configuration_dashboards.py
new file mode 100644
index 0000000..3249efc
--- /dev/null
+++ b/test/test_embedded_analytics_configuration_dashboards.py
@@ -0,0 +1,53 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.embedded_analytics_configuration_dashboards import EmbeddedAnalyticsConfigurationDashboards
+
+class TestEmbeddedAnalyticsConfigurationDashboards(unittest.TestCase):
+ """EmbeddedAnalyticsConfigurationDashboards unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> EmbeddedAnalyticsConfigurationDashboards:
+ """Test EmbeddedAnalyticsConfigurationDashboards
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `EmbeddedAnalyticsConfigurationDashboards`
+ """
+ model = EmbeddedAnalyticsConfigurationDashboards()
+ if include_optional:
+ return EmbeddedAnalyticsConfigurationDashboards(
+ campaign_insights = talon_one.models.embedded_dashboard_configuration.EmbeddedDashboardConfiguration(
+ workspace_id = 'main_workspace',
+ dashboard_id = 'campaign_insights_metrics', )
+ )
+ else:
+ return EmbeddedAnalyticsConfigurationDashboards(
+ )
+ """
+
+ def testEmbeddedAnalyticsConfigurationDashboards(self):
+ """Test EmbeddedAnalyticsConfigurationDashboards"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_embedded_dashboard_configuration.py b/test/test_embedded_dashboard_configuration.py
new file mode 100644
index 0000000..796a319
--- /dev/null
+++ b/test/test_embedded_dashboard_configuration.py
@@ -0,0 +1,54 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.embedded_dashboard_configuration import EmbeddedDashboardConfiguration
+
+class TestEmbeddedDashboardConfiguration(unittest.TestCase):
+ """EmbeddedDashboardConfiguration unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> EmbeddedDashboardConfiguration:
+ """Test EmbeddedDashboardConfiguration
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `EmbeddedDashboardConfiguration`
+ """
+ model = EmbeddedDashboardConfiguration()
+ if include_optional:
+ return EmbeddedDashboardConfiguration(
+ workspace_id = 'main_workspace',
+ dashboard_id = 'campaign_insights_metrics'
+ )
+ else:
+ return EmbeddedDashboardConfiguration(
+ workspace_id = 'main_workspace',
+ dashboard_id = 'campaign_insights_metrics',
+ )
+ """
+
+ def testEmbeddedDashboardConfiguration(self):
+ """Test EmbeddedDashboardConfiguration"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_endpoint.py b/test/test_endpoint.py
index 29b3eb0..5ed3b45 100644
--- a/test/test_endpoint.py
+++ b/test/test_endpoint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_entity.py b/test/test_entity.py
index 408ab67..5196fcc 100644
--- a/test/test_entity.py
+++ b/test/test_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_entity_with_talang_visible_id.py b/test/test_entity_with_talang_visible_id.py
index c26e667..f18947c 100644
--- a/test/test_entity_with_talang_visible_id.py
+++ b/test/test_entity_with_talang_visible_id.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_environment.py b/test/test_environment.py
index 2f00145..66d67f4 100644
--- a/test/test_environment.py
+++ b/test/test_environment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_error_effect_props.py b/test/test_error_effect_props.py
index 87ae3c4..5c5f2da 100644
--- a/test/test_error_effect_props.py
+++ b/test/test_error_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_error_response.py b/test/test_error_response.py
index ac768c3..770b9c5 100644
--- a/test/test_error_response.py
+++ b/test/test_error_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_error_response_with_status.py b/test/test_error_response_with_status.py
index d10eab0..9479d02 100644
--- a/test/test_error_response_with_status.py
+++ b/test/test_error_response_with_status.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_error_source.py b/test/test_error_source.py
index 7dd88b5..5ccea0d 100644
--- a/test/test_error_source.py
+++ b/test/test_error_source.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_evaluable_campaign_ids.py b/test/test_evaluable_campaign_ids.py
index b4aa758..ce96a7f 100644
--- a/test/test_evaluable_campaign_ids.py
+++ b/test/test_evaluable_campaign_ids.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_event.py b/test/test_event.py
index 6486ae4..f59664d 100644
--- a/test/test_event.py
+++ b/test/test_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_event_attributes_entity.py b/test/test_event_attributes_entity.py
index 792a4a6..b5b2a0b 100644
--- a/test/test_event_attributes_entity.py
+++ b/test/test_event_attributes_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_event_type.py b/test/test_event_type.py
index c6a7088..40faf61 100644
--- a/test/test_event_type.py
+++ b/test/test_event_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_event_v2.py b/test/test_event_v2.py
index 854e133..7269c9b 100644
--- a/test/test_event_v2.py
+++ b/test/test_event_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_event_v3.py b/test/test_event_v3.py
index 7a71aaf..eb1a852 100644
--- a/test/test_event_v3.py
+++ b/test/test_event_v3.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment.py b/test/test_experiment.py
index d95178c..8bd316f 100644
--- a/test/test_experiment.py
+++ b/test/test_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_campaign_copy.py b/test/test_experiment_campaign_copy.py
index 7f16858..2d5323f 100644
--- a/test/test_experiment_campaign_copy.py
+++ b/test/test_experiment_campaign_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_copy.py b/test/test_experiment_copy.py
index 8b3d255..dbfb0dd 100644
--- a/test/test_experiment_copy.py
+++ b/test/test_experiment_copy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_copy_experiment.py b/test/test_experiment_copy_experiment.py
index 5d0e664..9b34152 100644
--- a/test/test_experiment_copy_experiment.py
+++ b/test/test_experiment_copy_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_list_results.py b/test/test_experiment_list_results.py
new file mode 100644
index 0000000..e45be02
--- /dev/null
+++ b/test/test_experiment_list_results.py
@@ -0,0 +1,53 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.experiment_list_results import ExperimentListResults
+
+class TestExperimentListResults(unittest.TestCase):
+ """ExperimentListResults unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> ExperimentListResults:
+ """Test ExperimentListResults
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `ExperimentListResults`
+ """
+ model = ExperimentListResults()
+ if include_optional:
+ return ExperimentListResults(
+ results = [
+ null
+ ]
+ )
+ else:
+ return ExperimentListResults(
+ )
+ """
+
+ def testExperimentListResults(self):
+ """Test ExperimentListResults"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_experiment_list_results_request.py b/test/test_experiment_list_results_request.py
new file mode 100644
index 0000000..f768c30
--- /dev/null
+++ b/test/test_experiment_list_results_request.py
@@ -0,0 +1,56 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.experiment_list_results_request import ExperimentListResultsRequest
+
+class TestExperimentListResultsRequest(unittest.TestCase):
+ """ExperimentListResultsRequest unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> ExperimentListResultsRequest:
+ """Test ExperimentListResultsRequest
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `ExperimentListResultsRequest`
+ """
+ model = ExperimentListResultsRequest()
+ if include_optional:
+ return ExperimentListResultsRequest(
+ experiment_ids = [
+ 56
+ ]
+ )
+ else:
+ return ExperimentListResultsRequest(
+ experiment_ids = [
+ 56
+ ],
+ )
+ """
+
+ def testExperimentListResultsRequest(self):
+ """Test ExperimentListResultsRequest"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_experiment_result.py b/test/test_experiment_result.py
new file mode 100644
index 0000000..47267b1
--- /dev/null
+++ b/test/test_experiment_result.py
@@ -0,0 +1,88 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.experiment_result import ExperimentResult
+
+class TestExperimentResult(unittest.TestCase):
+ """ExperimentResult unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> ExperimentResult:
+ """Test ExperimentResult
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `ExperimentResult`
+ """
+ model = ExperimentResult()
+ if include_optional:
+ return ExperimentResult(
+ variants = [
+ talon_one.models.experiment_variant_result.ExperimentVariantResult(
+ variant_id = 1,
+ variant_name = 'Variant A',
+ variant_weight = 50,
+ is_winner = True,
+ total_revenue = 100,
+ sessions_count = 100,
+ avg_items_per_session = 100,
+ avg_session_value = 100,
+ avg_discounted_session_value = 100,
+ total_discounts = 10,
+ coupons_count = 12, )
+ ],
+ confidence = talon_one.models.experiment_variant_result_confidence.ExperimentVariantResultConfidence(
+ avg_session_value = 100,
+ avg_discounted_session_value = 100,
+ avg_items_per_session = 100, ),
+ experiment_id = 1
+ )
+ else:
+ return ExperimentResult(
+ variants = [
+ talon_one.models.experiment_variant_result.ExperimentVariantResult(
+ variant_id = 1,
+ variant_name = 'Variant A',
+ variant_weight = 50,
+ is_winner = True,
+ total_revenue = 100,
+ sessions_count = 100,
+ avg_items_per_session = 100,
+ avg_session_value = 100,
+ avg_discounted_session_value = 100,
+ total_discounts = 10,
+ coupons_count = 12, )
+ ],
+ confidence = talon_one.models.experiment_variant_result_confidence.ExperimentVariantResultConfidence(
+ avg_session_value = 100,
+ avg_discounted_session_value = 100,
+ avg_items_per_session = 100, ),
+ experiment_id = 1,
+ )
+ """
+
+ def testExperimentResult(self):
+ """Test ExperimentResult"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_experiment_results.py b/test/test_experiment_results.py
index 563f0e7..c0ee380 100644
--- a/test/test_experiment_results.py
+++ b/test/test_experiment_results.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -40,6 +40,7 @@ def make_instance(self, include_optional) -> ExperimentResults:
variant_id = 1,
variant_name = 'Variant A',
variant_weight = 50,
+ is_winner = True,
total_revenue = 100,
sessions_count = 100,
avg_items_per_session = 100,
@@ -55,6 +56,20 @@ def make_instance(self, include_optional) -> ExperimentResults:
)
else:
return ExperimentResults(
+ variants = [
+ talon_one.models.experiment_variant_result.ExperimentVariantResult(
+ variant_id = 1,
+ variant_name = 'Variant A',
+ variant_weight = 50,
+ is_winner = True,
+ total_revenue = 100,
+ sessions_count = 100,
+ avg_items_per_session = 100,
+ avg_session_value = 100,
+ avg_discounted_session_value = 100,
+ total_discounts = 10,
+ coupons_count = 12, )
+ ],
confidence = talon_one.models.experiment_variant_result_confidence.ExperimentVariantResultConfidence(
avg_session_value = 100,
avg_discounted_session_value = 100,
diff --git a/test/test_experiment_variant.py b/test/test_experiment_variant.py
index aac37be..c8baf75 100644
--- a/test/test_experiment_variant.py
+++ b/test/test_experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_variant_allocation.py b/test/test_experiment_variant_allocation.py
index a881929..7cc1d5b 100644
--- a/test/test_experiment_variant_allocation.py
+++ b/test/test_experiment_variant_allocation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_experiment_variant_result.py b/test/test_experiment_variant_result.py
index ffbf1c8..38709ab 100644
--- a/test/test_experiment_variant_result.py
+++ b/test/test_experiment_variant_result.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -38,6 +38,7 @@ def make_instance(self, include_optional) -> ExperimentVariantResult:
variant_id = 1,
variant_name = 'Variant A',
variant_weight = 50,
+ is_winner = True,
total_revenue = 100,
sessions_count = 100,
avg_items_per_session = 100,
diff --git a/test/test_experiment_variant_result_confidence.py b/test/test_experiment_variant_result_confidence.py
index 24270bf..2e39760 100644
--- a/test/test_experiment_variant_result_confidence.py
+++ b/test/test_experiment_variant_result_confidence.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_card_points_data.py b/test/test_expiring_card_points_data.py
index 538311a..9fa26cb 100644
--- a/test/test_expiring_card_points_data.py
+++ b/test/test_expiring_card_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_card_points_notification.py b/test/test_expiring_card_points_notification.py
index 4cac91a..88c845a 100644
--- a/test/test_expiring_card_points_notification.py
+++ b/test/test_expiring_card_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_coupons_data.py b/test/test_expiring_coupons_data.py
index 9aac286..c101a24 100644
--- a/test/test_expiring_coupons_data.py
+++ b/test/test_expiring_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_coupons_notification.py b/test/test_expiring_coupons_notification.py
index cec9c49..7a75de3 100644
--- a/test/test_expiring_coupons_notification.py
+++ b/test/test_expiring_coupons_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_coupons_notification_policy.py b/test/test_expiring_coupons_notification_policy.py
index bdb1267..eae5c9a 100644
--- a/test/test_expiring_coupons_notification_policy.py
+++ b/test/test_expiring_coupons_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_coupons_notification_trigger.py b/test/test_expiring_coupons_notification_trigger.py
index b304c41..623e1b2 100644
--- a/test/test_expiring_coupons_notification_trigger.py
+++ b/test/test_expiring_coupons_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_points_data.py b/test/test_expiring_points_data.py
index db1ca4d..2a40781 100644
--- a/test/test_expiring_points_data.py
+++ b/test/test_expiring_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_points_notification.py b/test/test_expiring_points_notification.py
index 438f17a..69f9b04 100644
--- a/test/test_expiring_points_notification.py
+++ b/test/test_expiring_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_points_notification_policy.py b/test/test_expiring_points_notification_policy.py
index 7937eeb..98bb442 100644
--- a/test/test_expiring_points_notification_policy.py
+++ b/test/test_expiring_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_expiring_points_notification_trigger.py b/test/test_expiring_points_notification_trigger.py
index 7fabea9..b7ac34f 100644
--- a/test/test_expiring_points_notification_trigger.py
+++ b/test/test_expiring_points_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_export.py b/test/test_export.py
index e12f906..1c12c58 100644
--- a/test/test_export.py
+++ b/test/test_export.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_extend_loyalty_points_expiry_date_effect_props.py b/test/test_extend_loyalty_points_expiry_date_effect_props.py
index 15efafe..e36ab79 100644
--- a/test/test_extend_loyalty_points_expiry_date_effect_props.py
+++ b/test/test_extend_loyalty_points_expiry_date_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_extended_coupon.py b/test/test_extended_coupon.py
index dfa19f9..78269e7 100644
--- a/test/test_extended_coupon.py
+++ b/test/test_extended_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_feature_flag.py b/test/test_feature_flag.py
index d3cdd57..2925a63 100644
--- a/test/test_feature_flag.py
+++ b/test/test_feature_flag.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_features_feed.py b/test/test_features_feed.py
index 602227b..c2204d4 100644
--- a/test/test_features_feed.py
+++ b/test/test_features_feed.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_func_arg_def.py b/test/test_func_arg_def.py
index ed1c6be..b020ef2 100644
--- a/test/test_func_arg_def.py
+++ b/test/test_func_arg_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_function_def.py b/test/test_function_def.py
index 8a177d8..1c2b600 100644
--- a/test/test_function_def.py
+++ b/test/test_function_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_audit_log_summary.py b/test/test_generate_audit_log_summary.py
index bb3bc62..6a355e6 100644
--- a/test/test_generate_audit_log_summary.py
+++ b/test/test_generate_audit_log_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_campaign_description.py b/test/test_generate_campaign_description.py
index 6174655..f84ce55 100644
--- a/test/test_generate_campaign_description.py
+++ b/test/test_generate_campaign_description.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_campaign_summary.py b/test/test_generate_campaign_summary.py
index c03c785..fc41f14 100644
--- a/test/test_generate_campaign_summary.py
+++ b/test/test_generate_campaign_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_campaign_tags.py b/test/test_generate_campaign_tags.py
index eef78ac..f78bcc1 100644
--- a/test/test_generate_campaign_tags.py
+++ b/test/test_generate_campaign_tags.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_coupon_failure_detailed_summary.py b/test/test_generate_coupon_failure_detailed_summary.py
index 8aa52f7..54ca2fa 100644
--- a/test/test_generate_coupon_failure_detailed_summary.py
+++ b/test/test_generate_coupon_failure_detailed_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_coupon_failure_summary.py b/test/test_generate_coupon_failure_summary.py
index 513c1d3..44c7d57 100644
--- a/test/test_generate_coupon_failure_summary.py
+++ b/test/test_generate_coupon_failure_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_coupon_rejections200_response.py b/test/test_generate_coupon_rejections200_response.py
index 6734504..095e0a6 100644
--- a/test/test_generate_coupon_rejections200_response.py
+++ b/test/test_generate_coupon_rejections200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_item_filter_description.py b/test/test_generate_item_filter_description.py
index 9335525..7f63190 100644
--- a/test/test_generate_item_filter_description.py
+++ b/test/test_generate_item_filter_description.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_loyalty_card.py b/test/test_generate_loyalty_card.py
index 55a8bcd..4f5b69f 100644
--- a/test/test_generate_loyalty_card.py
+++ b/test/test_generate_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_rule_title.py b/test/test_generate_rule_title.py
index 3e78543..856dce1 100644
--- a/test/test_generate_rule_title.py
+++ b/test/test_generate_rule_title.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_rule_title_rule.py b/test/test_generate_rule_title_rule.py
index bf1e53b..aab6b9c 100644
--- a/test/test_generate_rule_title_rule.py
+++ b/test/test_generate_rule_title_rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_generate_user_session_summary.py b/test/test_generate_user_session_summary.py
index 70733ea..b5d2339 100644
--- a/test/test_generate_user_session_summary.py
+++ b/test/test_generate_user_session_summary.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_access_logs_without_total_count200_response.py b/test/test_get_access_logs_without_total_count200_response.py
index 490d360..dc3ae2d 100644
--- a/test/test_get_access_logs_without_total_count200_response.py
+++ b/test/test_get_access_logs_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_additional_costs200_response.py b/test/test_get_additional_costs200_response.py
index 0efd166..9ddf1a7 100644
--- a/test/test_get_additional_costs200_response.py
+++ b/test/test_get_additional_costs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_customer_friends200_response.py b/test/test_get_application_customer_friends200_response.py
index f0b9ca7..d1379a5 100644
--- a/test/test_get_application_customer_friends200_response.py
+++ b/test/test_get_application_customer_friends200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_customers200_response.py b/test/test_get_application_customers200_response.py
index 6a36d88..0316264 100644
--- a/test/test_get_application_customers200_response.py
+++ b/test/test_get_application_customers200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_customers_by_attributes200_response.py b/test/test_get_application_customers_by_attributes200_response.py
index 6e24457..dafdbf1 100644
--- a/test/test_get_application_customers_by_attributes200_response.py
+++ b/test/test_get_application_customers_by_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_event_types200_response.py b/test/test_get_application_event_types200_response.py
index b63f941..5f1fd52 100644
--- a/test/test_get_application_event_types200_response.py
+++ b/test/test_get_application_event_types200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_events_without_total_count200_response.py b/test/test_get_application_events_without_total_count200_response.py
index 8b2b958..e9fb318 100644
--- a/test/test_get_application_events_without_total_count200_response.py
+++ b/test/test_get_application_events_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_application_sessions200_response.py b/test/test_get_application_sessions200_response.py
index 5d8cb72..2194f06 100644
--- a/test/test_get_application_sessions200_response.py
+++ b/test/test_get_application_sessions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_applications200_response.py b/test/test_get_applications200_response.py
index 370c681..e283ec5 100644
--- a/test/test_get_applications200_response.py
+++ b/test/test_get_applications200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_attributes200_response.py b/test/test_get_attributes200_response.py
index d673154..2fefb8e 100644
--- a/test/test_get_attributes200_response.py
+++ b/test/test_get_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_audience_memberships200_response.py b/test/test_get_audience_memberships200_response.py
index 4624593..470dc24 100644
--- a/test/test_get_audience_memberships200_response.py
+++ b/test/test_get_audience_memberships200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_audiences200_response.py b/test/test_get_audiences200_response.py
index c78fb44..e4d3ba9 100644
--- a/test/test_get_audiences200_response.py
+++ b/test/test_get_audiences200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_audiences_analytics200_response.py b/test/test_get_audiences_analytics200_response.py
index 6996f29..bb17a2c 100644
--- a/test/test_get_audiences_analytics200_response.py
+++ b/test/test_get_audiences_analytics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_campaign_analytics200_response.py b/test/test_get_campaign_analytics200_response.py
index c99937e..2090afa 100644
--- a/test/test_get_campaign_analytics200_response.py
+++ b/test/test_get_campaign_analytics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_campaign_groups200_response.py b/test/test_get_campaign_groups200_response.py
index 8021541..7b1c4be 100644
--- a/test/test_get_campaign_groups200_response.py
+++ b/test/test_get_campaign_groups200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_campaign_templates200_response.py b/test/test_get_campaign_templates200_response.py
index be1cdce..2f5227e 100644
--- a/test/test_get_campaign_templates200_response.py
+++ b/test/test_get_campaign_templates200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_campaigns200_response.py b/test/test_get_campaigns200_response.py
index b8dd1cc..a93013f 100644
--- a/test/test_get_campaigns200_response.py
+++ b/test/test_get_campaigns200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_changes200_response.py b/test/test_get_changes200_response.py
index b574837..11bf29c 100644
--- a/test/test_get_changes200_response.py
+++ b/test/test_get_changes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_collection_items200_response.py b/test/test_get_collection_items200_response.py
index 8fcba3a..03dbc19 100644
--- a/test/test_get_collection_items200_response.py
+++ b/test/test_get_collection_items200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_coupons_without_total_count200_response.py b/test/test_get_coupons_without_total_count200_response.py
index 542ff6d..6465ce7 100644
--- a/test/test_get_coupons_without_total_count200_response.py
+++ b/test/test_get_coupons_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customer_achievement_history200_response.py b/test/test_get_customer_achievement_history200_response.py
index eb12d70..fdda475 100644
--- a/test/test_get_customer_achievement_history200_response.py
+++ b/test/test_get_customer_achievement_history200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customer_achievements200_response.py b/test/test_get_customer_achievements200_response.py
index 53b7570..2bfc1e7 100644
--- a/test/test_get_customer_achievements200_response.py
+++ b/test/test_get_customer_achievements200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customer_activity_reports_without_total_count200_response.py b/test/test_get_customer_activity_reports_without_total_count200_response.py
index 5c0b5a7..067f94c 100644
--- a/test/test_get_customer_activity_reports_without_total_count200_response.py
+++ b/test/test_get_customer_activity_reports_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customer_profile_achievement_progress200_response.py b/test/test_get_customer_profile_achievement_progress200_response.py
index f85ab63..be9e7b4 100644
--- a/test/test_get_customer_profile_achievement_progress200_response.py
+++ b/test/test_get_customer_profile_achievement_progress200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customer_profiles200_response.py b/test/test_get_customer_profiles200_response.py
index 965fbe1..7e7c166 100644
--- a/test/test_get_customer_profiles200_response.py
+++ b/test/test_get_customer_profiles200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_customers_by_attributes200_response.py b/test/test_get_customers_by_attributes200_response.py
index 69e3270..1e317a2 100644
--- a/test/test_get_customers_by_attributes200_response.py
+++ b/test/test_get_customers_by_attributes200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_dashboard_statistics200_response.py b/test/test_get_dashboard_statistics200_response.py
index 38a3410..fa125a1 100644
--- a/test/test_get_dashboard_statistics200_response.py
+++ b/test/test_get_dashboard_statistics200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_event_types200_response.py b/test/test_get_event_types200_response.py
index c6b1405..23766ff 100644
--- a/test/test_get_event_types200_response.py
+++ b/test/test_get_event_types200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_exports200_response.py b/test/test_get_exports200_response.py
index 3f78ae2..87054c1 100644
--- a/test/test_get_exports200_response.py
+++ b/test/test_get_exports200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_integration_coupon_request.py b/test/test_get_integration_coupon_request.py
index 01fd61c..c55c62b 100644
--- a/test/test_get_integration_coupon_request.py
+++ b/test/test_get_integration_coupon_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_card_points200_response.py b/test/test_get_loyalty_card_points200_response.py
index a8edcb9..fe2baaf 100644
--- a/test/test_get_loyalty_card_points200_response.py
+++ b/test/test_get_loyalty_card_points200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_card_transaction_logs200_response.py b/test/test_get_loyalty_card_transaction_logs200_response.py
index ece680a..c1ba39d 100644
--- a/test/test_get_loyalty_card_transaction_logs200_response.py
+++ b/test/test_get_loyalty_card_transaction_logs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_card_transactions200_response.py b/test/test_get_loyalty_card_transactions200_response.py
index 74b4fbb..d7df818 100644
--- a/test/test_get_loyalty_card_transactions200_response.py
+++ b/test/test_get_loyalty_card_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_cards200_response.py b/test/test_get_loyalty_cards200_response.py
index bb9eb3c..2625591 100644
--- a/test/test_get_loyalty_cards200_response.py
+++ b/test/test_get_loyalty_cards200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_program_profile_points200_response.py b/test/test_get_loyalty_program_profile_points200_response.py
index 5ef5e2b..3fae1b7 100644
--- a/test/test_get_loyalty_program_profile_points200_response.py
+++ b/test/test_get_loyalty_program_profile_points200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_program_profile_transactions200_response.py b/test/test_get_loyalty_program_profile_transactions200_response.py
index 3e214b6..a690365 100644
--- a/test/test_get_loyalty_program_profile_transactions200_response.py
+++ b/test/test_get_loyalty_program_profile_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_program_transactions200_response.py b/test/test_get_loyalty_program_transactions200_response.py
index 9f04cf1..d87aa32 100644
--- a/test/test_get_loyalty_program_transactions200_response.py
+++ b/test/test_get_loyalty_program_transactions200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_loyalty_programs200_response.py b/test/test_get_loyalty_programs200_response.py
index 91577ad..7f3cc7b 100644
--- a/test/test_get_loyalty_programs200_response.py
+++ b/test/test_get_loyalty_programs200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_referrals_without_total_count200_response.py b/test/test_get_referrals_without_total_count200_response.py
index 45b81fe..d9566f6 100644
--- a/test/test_get_referrals_without_total_count200_response.py
+++ b/test/test_get_referrals_without_total_count200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_reserved_customers200_response.py b/test/test_get_reserved_customers200_response.py
index 2e48cca..aee0052 100644
--- a/test/test_get_reserved_customers200_response.py
+++ b/test/test_get_reserved_customers200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_rulesets200_response.py b/test/test_get_rulesets200_response.py
index 49385eb..6b60f54 100644
--- a/test/test_get_rulesets200_response.py
+++ b/test/test_get_rulesets200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_users200_response.py b/test/test_get_users200_response.py
index 1a047cb..db5319a 100644
--- a/test/test_get_users200_response.py
+++ b/test/test_get_users200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_get_webhooks200_response.py b/test/test_get_webhooks200_response.py
index da19d60..357823c 100644
--- a/test/test_get_webhooks200_response.py
+++ b/test/test_get_webhooks200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_giveaway.py b/test/test_giveaway.py
index 2130a86..211ba0c 100644
--- a/test/test_giveaway.py
+++ b/test/test_giveaway.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_giveaway_pool_notification.py b/test/test_giveaway_pool_notification.py
new file mode 100644
index 0000000..ce5b6bd
--- /dev/null
+++ b/test/test_giveaway_pool_notification.py
@@ -0,0 +1,80 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.giveaway_pool_notification import GiveawayPoolNotification
+
+class TestGiveawayPoolNotification(unittest.TestCase):
+ """GiveawayPoolNotification unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> GiveawayPoolNotification:
+ """Test GiveawayPoolNotification
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `GiveawayPoolNotification`
+ """
+ model = GiveawayPoolNotification()
+ if include_optional:
+ return GiveawayPoolNotification(
+ total_result_size = 1,
+ data = [
+ talon_one.models.giveaway_pool_notification_data.GiveawayPoolNotificationData(
+ event = 'giveaway_codes_low',
+ pool_id = 5,
+ pool_name = 'Summer Giveaway',
+ pool_description = 'Summer giveaway codes',
+ account_id = 10,
+ application_id = 42,
+ total_codes = 1000,
+ used_codes = 920,
+ remaining_codes = 80,
+ threshold_percent = 10, )
+ ],
+ notification_type = 'GiveawayPoolNotification'
+ )
+ else:
+ return GiveawayPoolNotification(
+ total_result_size = 1,
+ data = [
+ talon_one.models.giveaway_pool_notification_data.GiveawayPoolNotificationData(
+ event = 'giveaway_codes_low',
+ pool_id = 5,
+ pool_name = 'Summer Giveaway',
+ pool_description = 'Summer giveaway codes',
+ account_id = 10,
+ application_id = 42,
+ total_codes = 1000,
+ used_codes = 920,
+ remaining_codes = 80,
+ threshold_percent = 10, )
+ ],
+ notification_type = 'GiveawayPoolNotification',
+ )
+ """
+
+ def testGiveawayPoolNotification(self):
+ """Test GiveawayPoolNotification"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_giveaway_pool_notification_data.py b/test/test_giveaway_pool_notification_data.py
new file mode 100644
index 0000000..3a8f8d8
--- /dev/null
+++ b/test/test_giveaway_pool_notification_data.py
@@ -0,0 +1,70 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.giveaway_pool_notification_data import GiveawayPoolNotificationData
+
+class TestGiveawayPoolNotificationData(unittest.TestCase):
+ """GiveawayPoolNotificationData unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> GiveawayPoolNotificationData:
+ """Test GiveawayPoolNotificationData
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `GiveawayPoolNotificationData`
+ """
+ model = GiveawayPoolNotificationData()
+ if include_optional:
+ return GiveawayPoolNotificationData(
+ event = 'giveaway_codes_low',
+ pool_id = 5,
+ pool_name = 'Summer Giveaway',
+ pool_description = 'Summer giveaway codes',
+ account_id = 10,
+ application_id = 42,
+ total_codes = 1000,
+ used_codes = 920,
+ remaining_codes = 80,
+ threshold_percent = 10
+ )
+ else:
+ return GiveawayPoolNotificationData(
+ event = 'giveaway_codes_low',
+ pool_id = 5,
+ pool_name = 'Summer Giveaway',
+ pool_description = 'Summer giveaway codes',
+ account_id = 10,
+ application_id = 42,
+ total_codes = 1000,
+ used_codes = 920,
+ remaining_codes = 80,
+ threshold_percent = 10,
+ )
+ """
+
+ def testGiveawayPoolNotificationData(self):
+ """Test GiveawayPoolNotificationData"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_giveaways_pool.py b/test/test_giveaways_pool.py
index 1b64f9f..09d02f5 100644
--- a/test/test_giveaways_pool.py
+++ b/test/test_giveaways_pool.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_hidden_conditions_effects.py b/test/test_hidden_conditions_effects.py
index ef8f1b6..84be57c 100644
--- a/test/test_hidden_conditions_effects.py
+++ b/test/test_hidden_conditions_effects.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_history.py b/test/test_history.py
index 733f5e1..aa0ed56 100644
--- a/test/test_history.py
+++ b/test/test_history.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_identifiable_entity.py b/test/test_identifiable_entity.py
index 2caa802..240e6d1 100644
--- a/test/test_identifiable_entity.py
+++ b/test/test_identifiable_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_import_entity.py b/test/test_import_entity.py
index 2009e5d..6d9e5c8 100644
--- a/test/test_import_entity.py
+++ b/test/test_import_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_increase_achievement_progress_effect_props.py b/test/test_increase_achievement_progress_effect_props.py
index 4af2aa1..4e6eb2b 100644
--- a/test/test_increase_achievement_progress_effect_props.py
+++ b/test/test_increase_achievement_progress_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_influencing_campaign_details.py b/test/test_influencing_campaign_details.py
index 4cfe49c..3d6e9bf 100644
--- a/test/test_influencing_campaign_details.py
+++ b/test/test_influencing_campaign_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_api.py b/test/test_integration_api.py
index 6e1e7f6..adf0f0e 100644
--- a/test/test_integration_api.py
+++ b/test/test_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -194,13 +194,6 @@ def test_link_loyalty_card_to_profile(self) -> None:
"""
pass
- def test_price_history(self) -> None:
- """Test case for price_history
-
- Get summary of price history
- """
- pass
-
def test_reopen_customer_session(self) -> None:
"""Test case for reopen_customer_session
diff --git a/test/test_integration_campaign.py b/test/test_integration_campaign.py
index 6fac9b5..1572764 100644
--- a/test/test_integration_campaign.py
+++ b/test/test_integration_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_coupon.py b/test/test_integration_coupon.py
index 49e1d6e..6b8d33a 100644
--- a/test/test_integration_coupon.py
+++ b/test/test_integration_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_customer_profile_audience_request.py b/test/test_integration_customer_profile_audience_request.py
index b5c1e04..1c65052 100644
--- a/test/test_integration_customer_profile_audience_request.py
+++ b/test/test_integration_customer_profile_audience_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_customer_profile_audience_request_item.py b/test/test_integration_customer_profile_audience_request_item.py
index 53064d5..7b793e5 100644
--- a/test/test_integration_customer_profile_audience_request_item.py
+++ b/test/test_integration_customer_profile_audience_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_customer_session_response.py b/test/test_integration_customer_session_response.py
index a12de9f..b5f865d 100644
--- a/test/test_integration_customer_session_response.py
+++ b/test/test_integration_customer_session_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_entity.py b/test/test_integration_entity.py
index d10a24a..8482668 100644
--- a/test/test_integration_entity.py
+++ b/test/test_integration_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_event.py b/test/test_integration_event.py
index 97bd66c..352a1d7 100644
--- a/test/test_integration_event.py
+++ b/test/test_integration_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_event_v2_request.py b/test/test_integration_event_v2_request.py
index 3ac446a..57f734b 100644
--- a/test/test_integration_event_v2_request.py
+++ b/test/test_integration_event_v2_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_event_v2_response.py b/test/test_integration_event_v2_response.py
index 8a38be9..93cee0f 100644
--- a/test/test_integration_event_v2_response.py
+++ b/test/test_integration_event_v2_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_event_v3_request.py b/test/test_integration_event_v3_request.py
index 08d2049..9818473 100644
--- a/test/test_integration_event_v3_request.py
+++ b/test/test_integration_event_v3_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_event_v3_response.py b/test/test_integration_event_v3_response.py
index e6a30d2..204d010 100644
--- a/test/test_integration_event_v3_response.py
+++ b/test/test_integration_event_v3_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_config.py b/test/test_integration_hub_config.py
index cbedf5f..eb74693 100644
--- a/test/test_integration_hub_config.py
+++ b/test/test_integration_hub_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_coupon_based_notifications.py b/test/test_integration_hub_event_payload_coupon_based_notifications.py
index 84a7b5c..334c3ff 100644
--- a/test/test_integration_hub_event_payload_coupon_based_notifications.py
+++ b/test/test_integration_hub_event_payload_coupon_based_notifications.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_coupon_based_notifications_limits.py b/test/test_integration_hub_event_payload_coupon_based_notifications_limits.py
index 6b2ef1d..a38ab88 100644
--- a/test/test_integration_hub_event_payload_coupon_based_notifications_limits.py
+++ b/test/test_integration_hub_event_payload_coupon_based_notifications_limits.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_loyalty_profile_based_notification.py b/test/test_integration_hub_event_payload_loyalty_profile_based_notification.py
index a356e48..4570455 100644
--- a/test/test_integration_hub_event_payload_loyalty_profile_based_notification.py
+++ b/test/test_integration_hub_event_payload_loyalty_profile_based_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py b/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
index e475b5e..39b5bd5 100644
--- a/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
+++ b/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py b/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
index 8dcfcd1..c4009eb 100644
--- a/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
+++ b/test/test_integration_hub_event_payload_loyalty_profile_based_points_changed_notification_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py b/test/test_integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
index 89d0b8a..a0e944a 100644
--- a/test/test_integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
+++ b/test/test_integration_hub_event_payload_loyalty_profile_based_tier_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py b/test/test_integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
index e3e6598..8e52c76 100644
--- a/test/test_integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
+++ b/test/test_integration_hub_event_payload_loyalty_profile_based_tier_upgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_event_record.py b/test/test_integration_hub_event_record.py
index 1e3222f..c2c9891 100644
--- a/test/test_integration_hub_event_record.py
+++ b/test/test_integration_hub_event_record.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_flow.py b/test/test_integration_hub_flow.py
index 527aff5..3328460 100644
--- a/test/test_integration_hub_flow.py
+++ b/test/test_integration_hub_flow.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_flow_config.py b/test/test_integration_hub_flow_config.py
index 13a0326..d2f6323 100644
--- a/test/test_integration_hub_flow_config.py
+++ b/test/test_integration_hub_flow_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_flow_config_response.py b/test/test_integration_hub_flow_config_response.py
index 3c10c53..e17312b 100644
--- a/test/test_integration_hub_flow_config_response.py
+++ b/test/test_integration_hub_flow_config_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_flow_response.py b/test/test_integration_hub_flow_response.py
index b719ff4..0dc34f4 100644
--- a/test/test_integration_hub_flow_response.py
+++ b/test/test_integration_hub_flow_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_flow_with_config.py b/test/test_integration_hub_flow_with_config.py
index d79fee4..a79311a 100644
--- a/test/test_integration_hub_flow_with_config.py
+++ b/test/test_integration_hub_flow_with_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_hub_paginated_event_payload.py b/test/test_integration_hub_paginated_event_payload.py
index 5ccdede..f278bf5 100644
--- a/test/test_integration_hub_paginated_event_payload.py
+++ b/test/test_integration_hub_paginated_event_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_profile_entity.py b/test/test_integration_profile_entity.py
index fa3bf40..b46f25d 100644
--- a/test/test_integration_profile_entity.py
+++ b/test/test_integration_profile_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_profile_entity_v3.py b/test/test_integration_profile_entity_v3.py
index a7ecece..c09d0aa 100644
--- a/test/test_integration_profile_entity_v3.py
+++ b/test/test_integration_profile_entity_v3.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_request.py b/test/test_integration_request.py
index b05cb23..0f7e1a1 100644
--- a/test/test_integration_request.py
+++ b/test/test_integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_response.py b/test/test_integration_response.py
index 1ea2dd3..0354da3 100644
--- a/test/test_integration_response.py
+++ b/test/test_integration_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_state.py b/test/test_integration_state.py
index 553dcad..6b21fd8 100644
--- a/test/test_integration_state.py
+++ b/test/test_integration_state.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_state_v2.py b/test/test_integration_state_v2.py
index c9e3bea..ae71a41 100644
--- a/test/test_integration_state_v2.py
+++ b/test/test_integration_state_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_integration_store_entity.py b/test/test_integration_store_entity.py
index 07b619b..486e086 100644
--- a/test/test_integration_store_entity.py
+++ b/test/test_integration_store_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_inventory_coupon.py b/test/test_inventory_coupon.py
index d8cb6b5..c8338cf 100644
--- a/test/test_inventory_coupon.py
+++ b/test/test_inventory_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_inventory_referral.py b/test/test_inventory_referral.py
index 1204277..5db924f 100644
--- a/test/test_inventory_referral.py
+++ b/test/test_inventory_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_item_attribute.py b/test/test_item_attribute.py
index daa377e..ca027eb 100644
--- a/test/test_item_attribute.py
+++ b/test/test_item_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_label_target_audience.py b/test/test_label_target_audience.py
index 00faad3..0581b03 100644
--- a/test/test_label_target_audience.py
+++ b/test/test_label_target_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_label_target_none.py b/test/test_label_target_none.py
index fea127d..9a9ab0e 100644
--- a/test/test_label_target_none.py
+++ b/test/test_label_target_none.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_ledger_entry.py b/test/test_ledger_entry.py
index 497f6d4..ab1ad04 100644
--- a/test/test_ledger_entry.py
+++ b/test/test_ledger_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_ledger_info.py b/test/test_ledger_info.py
index a87de6e..d91d56f 100644
--- a/test/test_ledger_info.py
+++ b/test/test_ledger_info.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_ledger_points_entry_integration_api.py b/test/test_ledger_points_entry_integration_api.py
index 752a6b8..ecad4d2 100644
--- a/test/test_ledger_points_entry_integration_api.py
+++ b/test/test_ledger_points_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_ledger_transaction_log_entry_integration_api.py b/test/test_ledger_transaction_log_entry_integration_api.py
index 77e6016..d069132 100644
--- a/test/test_ledger_transaction_log_entry_integration_api.py
+++ b/test/test_ledger_transaction_log_entry_integration_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_library_attribute.py b/test/test_library_attribute.py
index c431c3b..7c4d778 100644
--- a/test/test_library_attribute.py
+++ b/test/test_library_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_limit_config.py b/test/test_limit_config.py
index 0462442..247351e 100644
--- a/test/test_limit_config.py
+++ b/test/test_limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_limit_counter.py b/test/test_limit_counter.py
index a547654..e439948 100644
--- a/test/test_limit_counter.py
+++ b/test/test_limit_counter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_account_collections200_response.py b/test/test_list_account_collections200_response.py
index c84b77c..a90dac4 100644
--- a/test/test_list_account_collections200_response.py
+++ b/test/test_list_account_collections200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_achievements200_response.py b/test/test_list_achievements200_response.py
index c854bf3..fbd0dd1 100644
--- a/test/test_list_achievements200_response.py
+++ b/test/test_list_achievements200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_all_roles_v2200_response.py b/test/test_list_all_roles_v2200_response.py
index 9055a5b..2912a24 100644
--- a/test/test_list_all_roles_v2200_response.py
+++ b/test/test_list_all_roles_v2200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_campaign_store_budget_limits200_response.py b/test/test_list_campaign_store_budget_limits200_response.py
index 1def0ab..63e6d80 100644
--- a/test/test_list_campaign_store_budget_limits200_response.py
+++ b/test/test_list_campaign_store_budget_limits200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_campaign_store_budgets.py b/test/test_list_campaign_store_budgets.py
index d63e717..2859c2a 100644
--- a/test/test_list_campaign_store_budgets.py
+++ b/test/test_list_campaign_store_budgets.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_campaign_store_budgets_store.py b/test/test_list_campaign_store_budgets_store.py
index 53f2c9b..0ed7c64 100644
--- a/test/test_list_campaign_store_budgets_store.py
+++ b/test/test_list_campaign_store_budgets_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_catalog_items200_response.py b/test/test_list_catalog_items200_response.py
index c9a7215..1c50f1f 100644
--- a/test/test_list_catalog_items200_response.py
+++ b/test/test_list_catalog_items200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_experiments200_response.py b/test/test_list_experiments200_response.py
index ea1c451..b9c218c 100644
--- a/test/test_list_experiments200_response.py
+++ b/test/test_list_experiments200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_list_stores200_response.py b/test/test_list_stores200_response.py
index 3afb99c..e8b5f37 100644
--- a/test/test_list_stores200_response.py
+++ b/test/test_list_stores200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_login_params.py b/test/test_login_params.py
index 8e31990..e4aad85 100644
--- a/test/test_login_params.py
+++ b/test/test_login_params.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty.py b/test/test_loyalty.py
index 85a3fad..452be7b 100644
--- a/test/test_loyalty.py
+++ b/test/test_loyalty.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_balance.py b/test/test_loyalty_balance.py
index a4897d2..9bdde67 100644
--- a/test/test_loyalty_balance.py
+++ b/test/test_loyalty_balance.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_balance_with_tier.py b/test/test_loyalty_balance_with_tier.py
index 54fe71f..022e124 100644
--- a/test/test_loyalty_balance_with_tier.py
+++ b/test/test_loyalty_balance_with_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_balances.py b/test/test_loyalty_balances.py
index 9b133dd..1a99ac5 100644
--- a/test/test_loyalty_balances.py
+++ b/test/test_loyalty_balances.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_balances_with_tiers.py b/test/test_loyalty_balances_with_tiers.py
index 5636791..940f169 100644
--- a/test/test_loyalty_balances_with_tiers.py
+++ b/test/test_loyalty_balances_with_tiers.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card.py b/test/test_loyalty_card.py
index 99e26b8..4285b8d 100644
--- a/test/test_loyalty_card.py
+++ b/test/test_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card_balances.py b/test/test_loyalty_card_balances.py
index 688848a..371844f 100644
--- a/test/test_loyalty_card_balances.py
+++ b/test/test_loyalty_card_balances.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card_batch.py b/test/test_loyalty_card_batch.py
index cffa304..963a185 100644
--- a/test/test_loyalty_card_batch.py
+++ b/test/test_loyalty_card_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card_batch_response.py b/test/test_loyalty_card_batch_response.py
index 26654f8..ed16e52 100644
--- a/test/test_loyalty_card_batch_response.py
+++ b/test/test_loyalty_card_batch_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card_profile_registration.py b/test/test_loyalty_card_profile_registration.py
index 7f10d12..bd2987b 100644
--- a/test/test_loyalty_card_profile_registration.py
+++ b/test/test_loyalty_card_profile_registration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_card_registration.py b/test/test_loyalty_card_registration.py
index 798b791..f0c3a90 100644
--- a/test/test_loyalty_card_registration.py
+++ b/test/test_loyalty_card_registration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_dashboard_data.py b/test/test_loyalty_dashboard_data.py
index 533f3ff..e92d8ef 100644
--- a/test/test_loyalty_dashboard_data.py
+++ b/test/test_loyalty_dashboard_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_dashboard_points_breakdown.py b/test/test_loyalty_dashboard_points_breakdown.py
index 3eca41e..9c9bf08 100644
--- a/test/test_loyalty_dashboard_points_breakdown.py
+++ b/test/test_loyalty_dashboard_points_breakdown.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_ledger.py b/test/test_loyalty_ledger.py
index 5d3c348..b0b4f24 100644
--- a/test/test_loyalty_ledger.py
+++ b/test/test_loyalty_ledger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_ledger_entry.py b/test/test_loyalty_ledger_entry.py
index 8f56a71..2b21015 100644
--- a/test/test_loyalty_ledger_entry.py
+++ b/test/test_loyalty_ledger_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_ledger_entry_expiry_date_change.py b/test/test_loyalty_ledger_entry_expiry_date_change.py
index 7d3920a..6f8f3c3 100644
--- a/test/test_loyalty_ledger_entry_expiry_date_change.py
+++ b/test/test_loyalty_ledger_entry_expiry_date_change.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_ledger_entry_flags.py b/test/test_loyalty_ledger_entry_flags.py
index 60c420e..a9a1425 100644
--- a/test/test_loyalty_ledger_entry_flags.py
+++ b/test/test_loyalty_ledger_entry_flags.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_ledger_transactions.py b/test/test_loyalty_ledger_transactions.py
index b8287b5..051e30f 100644
--- a/test/test_loyalty_ledger_transactions.py
+++ b/test/test_loyalty_ledger_transactions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_membership.py b/test/test_loyalty_membership.py
index 6e10427..e8ee18d 100644
--- a/test/test_loyalty_membership.py
+++ b/test/test_loyalty_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_program.py b/test/test_loyalty_program.py
index c078035..c6b4b68 100644
--- a/test/test_loyalty_program.py
+++ b/test/test_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_program_balance.py b/test/test_loyalty_program_balance.py
index 429b09e..0c903a8 100644
--- a/test/test_loyalty_program_balance.py
+++ b/test/test_loyalty_program_balance.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_program_entity.py b/test/test_loyalty_program_entity.py
index edcdcf1..e1b139a 100644
--- a/test/test_loyalty_program_entity.py
+++ b/test/test_loyalty_program_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_program_ledgers.py b/test/test_loyalty_program_ledgers.py
index 00c5153..f802a92 100644
--- a/test/test_loyalty_program_ledgers.py
+++ b/test/test_loyalty_program_ledgers.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_program_transaction.py b/test/test_loyalty_program_transaction.py
index 9612f1c..3ad643c 100644
--- a/test/test_loyalty_program_transaction.py
+++ b/test/test_loyalty_program_transaction.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_sub_ledger.py b/test/test_loyalty_sub_ledger.py
index 4079ed0..4c7d91b 100644
--- a/test/test_loyalty_sub_ledger.py
+++ b/test/test_loyalty_sub_ledger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_loyalty_tier.py b/test/test_loyalty_tier.py
index e3c3d18..da48f6e 100644
--- a/test/test_loyalty_tier.py
+++ b/test/test_loyalty_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_management_api.py b/test/test_management_api.py
index 6d38bfd..72caa08 100644
--- a/test/test_management_api.py
+++ b/test/test_management_api.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -1048,6 +1048,13 @@ def test_okta_event_handler_challenge(self) -> None:
"""
pass
+ def test_price_history(self) -> None:
+ """Test case for price_history
+
+ Get summary of price history
+ """
+ pass
+
def test_remove_loyalty_points(self) -> None:
"""Test case for remove_loyalty_points
diff --git a/test/test_management_key.py b/test/test_management_key.py
index 103d0ab..397c1ad 100644
--- a/test/test_management_key.py
+++ b/test/test_management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_manager_config.py b/test/test_manager_config.py
index 7686df2..1e0f0f4 100644
--- a/test/test_manager_config.py
+++ b/test/test_manager_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_message_log_entries.py b/test/test_message_log_entries.py
index b176649..8152372 100644
--- a/test/test_message_log_entries.py
+++ b/test/test_message_log_entries.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_message_log_entry.py b/test/test_message_log_entry.py
index c86d159..0ee2237 100644
--- a/test/test_message_log_entry.py
+++ b/test/test_message_log_entry.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_message_log_request.py b/test/test_message_log_request.py
index 878dff2..cbcaa00 100644
--- a/test/test_message_log_request.py
+++ b/test/test_message_log_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_message_log_response.py b/test/test_message_log_response.py
index baa0a6c..534cc10 100644
--- a/test/test_message_log_response.py
+++ b/test/test_message_log_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_message_test.py b/test/test_message_test.py
index 1bd956a..b1a81d9 100644
--- a/test/test_message_test.py
+++ b/test/test_message_test.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_meta.py b/test/test_meta.py
index 9f3a58a..408fe67 100644
--- a/test/test_meta.py
+++ b/test/test_meta.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_model_import.py b/test/test_model_import.py
index 2c06dad..efc74cf 100644
--- a/test/test_model_import.py
+++ b/test/test_model_import.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_model_return.py b/test/test_model_return.py
index 7b0cab6..d50ac45 100644
--- a/test/test_model_return.py
+++ b/test/test_model_return.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multi_application_entity.py b/test/test_multi_application_entity.py
index 80e3f7c..83c7ade 100644
--- a/test/test_multi_application_entity.py
+++ b/test/test_multi_application_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_attribute.py b/test/test_multiple_attribute.py
index c467a83..c67d37e 100644
--- a/test/test_multiple_attribute.py
+++ b/test/test_multiple_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_audiences.py b/test/test_multiple_audiences.py
index 40292b1..1461abb 100644
--- a/test/test_multiple_audiences.py
+++ b/test/test_multiple_audiences.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_audiences_item.py b/test/test_multiple_audiences_item.py
index 01bd0eb..9b773ff 100644
--- a/test/test_multiple_audiences_item.py
+++ b/test/test_multiple_audiences_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_customer_profile_integration_request.py b/test/test_multiple_customer_profile_integration_request.py
index 74708eb..ae35506 100644
--- a/test/test_multiple_customer_profile_integration_request.py
+++ b/test/test_multiple_customer_profile_integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_customer_profile_integration_request_item.py b/test/test_multiple_customer_profile_integration_request_item.py
index 036f871..211e1e3 100644
--- a/test/test_multiple_customer_profile_integration_request_item.py
+++ b/test/test_multiple_customer_profile_integration_request_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_customer_profile_integration_response_v2.py b/test/test_multiple_customer_profile_integration_response_v2.py
index f6b0bbf..f24ff39 100644
--- a/test/test_multiple_customer_profile_integration_response_v2.py
+++ b/test/test_multiple_customer_profile_integration_response_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_new_attribute.py b/test/test_multiple_new_attribute.py
index 972f177..a393d6c 100644
--- a/test/test_multiple_new_attribute.py
+++ b/test/test_multiple_new_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_multiple_new_audiences.py b/test/test_multiple_new_audiences.py
index 75309d4..fc3e2dc 100644
--- a/test/test_multiple_new_audiences.py
+++ b/test/test_multiple_new_audiences.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_mutable_entity.py b/test/test_mutable_entity.py
index f3818ea..95f6dc9 100644
--- a/test/test_mutable_entity.py
+++ b/test/test_mutable_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_account.py b/test/test_new_account.py
index 76541dc..398c1c1 100644
--- a/test/test_new_account.py
+++ b/test/test_new_account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_account_sign_up.py b/test/test_new_account_sign_up.py
index 5e37ef8..56190d6 100644
--- a/test/test_new_account_sign_up.py
+++ b/test/test_new_account_sign_up.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_additional_cost.py b/test/test_new_additional_cost.py
index 77dd6ef..fe680f9 100644
--- a/test/test_new_additional_cost.py
+++ b/test/test_new_additional_cost.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_app_wide_coupon_deletion_job.py b/test/test_new_app_wide_coupon_deletion_job.py
index 6f92e33..3b907a4 100644
--- a/test/test_new_app_wide_coupon_deletion_job.py
+++ b/test/test_new_app_wide_coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_application.py b/test/test_new_application.py
index c794de2..d5ca3b2 100644
--- a/test/test_new_application.py
+++ b/test/test_new_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_application_api_key.py b/test/test_new_application_api_key.py
index e4ab89a..1b88e67 100644
--- a/test/test_new_application_api_key.py
+++ b/test/test_new_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_application_cif.py b/test/test_new_application_cif.py
index 944fb1e..30a8cb6 100644
--- a/test/test_new_application_cif.py
+++ b/test/test_new_application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_application_cif_expression.py b/test/test_new_application_cif_expression.py
index 67d9e6a..bf9650a 100644
--- a/test/test_new_application_cif_expression.py
+++ b/test/test_new_application_cif_expression.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_attribute.py b/test/test_new_attribute.py
index 6ba6921..a746192 100644
--- a/test/test_new_attribute.py
+++ b/test/test_new_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_audience.py b/test/test_new_audience.py
index a2834ca..14abb6f 100644
--- a/test/test_new_audience.py
+++ b/test/test_new_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_base_notification.py b/test/test_new_base_notification.py
index 15f35f2..6ce57b6 100644
--- a/test/test_new_base_notification.py
+++ b/test/test_new_base_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_blueprint.py b/test/test_new_blueprint.py
index 3d45985..44714dc 100644
--- a/test/test_new_blueprint.py
+++ b/test/test_new_blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign.py b/test/test_new_campaign.py
index 3de3b49..630b80f 100644
--- a/test/test_new_campaign.py
+++ b/test/test_new_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -61,6 +61,7 @@ def make_instance(self, include_optional) -> NewCampaign:
campaign_groups = [1, 3],
type = 'advanced',
linked_store_ids = [1, 2, 3],
+ coupon_attributes = talon_one.models.coupon_attributes.couponAttributes(),
evaluation_group_id = 2
)
else:
diff --git a/test/test_new_campaign_collection.py b/test/test_new_campaign_collection.py
index 15d2c5a..eb2d54a 100644
--- a/test/test_new_campaign_collection.py
+++ b/test/test_new_campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_evaluation_group.py b/test/test_new_campaign_evaluation_group.py
index d8cb7f4..ab96a49 100644
--- a/test/test_new_campaign_evaluation_group.py
+++ b/test/test_new_campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_group.py b/test/test_new_campaign_group.py
index 1e0b763..a347108 100644
--- a/test/test_new_campaign_group.py
+++ b/test/test_new_campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_set.py b/test/test_new_campaign_set.py
index b8c5bc1..708455b 100644
--- a/test/test_new_campaign_set.py
+++ b/test/test_new_campaign_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_store_budget.py b/test/test_new_campaign_store_budget.py
index 4bf0578..4a41921 100644
--- a/test/test_new_campaign_store_budget.py
+++ b/test/test_new_campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_store_budget_store_limit.py b/test/test_new_campaign_store_budget_store_limit.py
index 308ed83..5fd4ae2 100644
--- a/test/test_new_campaign_store_budget_store_limit.py
+++ b/test/test_new_campaign_store_budget_store_limit.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_campaign_template.py b/test/test_new_campaign_template.py
index 08d2ecc..71630e3 100644
--- a/test/test_new_campaign_template.py
+++ b/test/test_new_campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_catalog.py b/test/test_new_catalog.py
index 7ff8c71..fecc38b 100644
--- a/test/test_new_catalog.py
+++ b/test/test_new_catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_collection.py b/test/test_new_collection.py
index c693de2..964ec45 100644
--- a/test/test_new_collection.py
+++ b/test/test_new_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_coupon_creation_job.py b/test/test_new_coupon_creation_job.py
index 81220ab..f24351f 100644
--- a/test/test_new_coupon_creation_job.py
+++ b/test/test_new_coupon_creation_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_coupon_deletion_job.py b/test/test_new_coupon_deletion_job.py
index 8ceea1c..40a3408 100644
--- a/test/test_new_coupon_deletion_job.py
+++ b/test/test_new_coupon_deletion_job.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_coupons.py b/test/test_new_coupons.py
index 499ba45..4d7ff3e 100644
--- a/test/test_new_coupons.py
+++ b/test/test_new_coupons.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_coupons_for_multiple_recipients.py b/test/test_new_coupons_for_multiple_recipients.py
index 8f3a099..ebbef23 100644
--- a/test/test_new_coupons_for_multiple_recipients.py
+++ b/test/test_new_coupons_for_multiple_recipients.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_custom_effect.py b/test/test_new_custom_effect.py
index 63262a8..f2d55d7 100644
--- a/test/test_new_custom_effect.py
+++ b/test/test_new_custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_customer_profile.py b/test/test_new_customer_profile.py
index 5d71dcc..78e1607 100644
--- a/test/test_new_customer_profile.py
+++ b/test/test_new_customer_profile.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_customer_session.py b/test/test_new_customer_session.py
index 3c19794..30531c6 100644
--- a/test/test_new_customer_session.py
+++ b/test/test_new_customer_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_customer_session_v2.py b/test/test_new_customer_session_v2.py
index bd6697e..fe4c61e 100644
--- a/test/test_new_customer_session_v2.py
+++ b/test/test_new_customer_session_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_event.py b/test/test_new_event.py
index 177ad6b..8d3d7a3 100644
--- a/test/test_new_event.py
+++ b/test/test_new_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_event_type.py b/test/test_new_event_type.py
index 346aaf4..5dd085d 100644
--- a/test/test_new_event_type.py
+++ b/test/test_new_event_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_experiment.py b/test/test_new_experiment.py
index c2b3e92..a8c4a74 100644
--- a/test/test_new_experiment.py
+++ b/test/test_new_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_experiment_variant.py b/test/test_new_experiment_variant.py
index 4cebe7b..79ee35b 100644
--- a/test/test_new_experiment_variant.py
+++ b/test/test_new_experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_experiment_variant_array.py b/test/test_new_experiment_variant_array.py
index 46f8a02..ee7cadb 100644
--- a/test/test_new_experiment_variant_array.py
+++ b/test/test_new_experiment_variant_array.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_external_invitation.py b/test/test_new_external_invitation.py
index ed29429..c895878 100644
--- a/test/test_new_external_invitation.py
+++ b/test/test_new_external_invitation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_giveaways_pool.py b/test/test_new_giveaways_pool.py
index 8e47c42..f6008a8 100644
--- a/test/test_new_giveaways_pool.py
+++ b/test/test_new_giveaways_pool.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_internal_audience.py b/test/test_new_internal_audience.py
index 60475e7..e229a06 100644
--- a/test/test_new_internal_audience.py
+++ b/test/test_new_internal_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_invitation.py b/test/test_new_invitation.py
index 133098b..cdd4ebb 100644
--- a/test/test_new_invitation.py
+++ b/test/test_new_invitation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_invite_email.py b/test/test_new_invite_email.py
index d8b3973..aa92fcb 100644
--- a/test/test_new_invite_email.py
+++ b/test/test_new_invite_email.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_loyalty_program.py b/test/test_new_loyalty_program.py
index 1b34643..998b351 100644
--- a/test/test_new_loyalty_program.py
+++ b/test/test_new_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_loyalty_tier.py b/test/test_new_loyalty_tier.py
index 92684da..786aa15 100644
--- a/test/test_new_loyalty_tier.py
+++ b/test/test_new_loyalty_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_management_key.py b/test/test_new_management_key.py
index 5bacf79..01bea53 100644
--- a/test/test_new_management_key.py
+++ b/test/test_new_management_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_message_test.py b/test/test_new_message_test.py
index 42181bc..63b7c29 100644
--- a/test/test_new_message_test.py
+++ b/test/test_new_message_test.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_multiple_audiences_item.py b/test/test_new_multiple_audiences_item.py
index e91e330..a5b9c06 100644
--- a/test/test_new_multiple_audiences_item.py
+++ b/test/test_new_multiple_audiences_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_notification_webhook.py b/test/test_new_notification_webhook.py
index ef4adda..7a22622 100644
--- a/test/test_new_notification_webhook.py
+++ b/test/test_new_notification_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_outgoing_integration_webhook.py b/test/test_new_outgoing_integration_webhook.py
index 64d0392..dddf7c9 100644
--- a/test/test_new_outgoing_integration_webhook.py
+++ b/test/test_new_outgoing_integration_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_password.py b/test/test_new_password.py
index 930885e..c1b36a9 100644
--- a/test/test_new_password.py
+++ b/test/test_new_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_password_email.py b/test/test_new_password_email.py
index 9909d8e..35daf82 100644
--- a/test/test_new_password_email.py
+++ b/test/test_new_password_email.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_picklist.py b/test/test_new_picklist.py
index 02c91c1..df267eb 100644
--- a/test/test_new_picklist.py
+++ b/test/test_new_picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_price_adjustment.py b/test/test_new_price_adjustment.py
index d07aa83..7921f0e 100644
--- a/test/test_new_price_adjustment.py
+++ b/test/test_new_price_adjustment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_price_type.py b/test/test_new_price_type.py
index a64699d..e794d92 100644
--- a/test/test_new_price_type.py
+++ b/test/test_new_price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_referral.py b/test/test_new_referral.py
index 8b6f045..95d644a 100644
--- a/test/test_new_referral.py
+++ b/test/test_new_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_referrals_for_multiple_advocates.py b/test/test_new_referrals_for_multiple_advocates.py
index ae12db7..4f7c1ff 100644
--- a/test/test_new_referrals_for_multiple_advocates.py
+++ b/test/test_new_referrals_for_multiple_advocates.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_return.py b/test/test_new_return.py
index dca8573..dc12042 100644
--- a/test/test_new_return.py
+++ b/test/test_new_return.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_revision_version.py b/test/test_new_revision_version.py
index 1a980f2..d4b6108 100644
--- a/test/test_new_revision_version.py
+++ b/test/test_new_revision_version.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -60,7 +60,8 @@ def make_instance(self, include_optional) -> NewRevisionVersion:
reevaluate_on_return = True,
features = [
'coupons'
- ]
+ ],
+ coupon_attributes = None
)
else:
return NewRevisionVersion(
diff --git a/test/test_new_role.py b/test/test_new_role.py
index 62fb753..b2c3ef3 100644
--- a/test/test_new_role.py
+++ b/test/test_new_role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_role_v2.py b/test/test_new_role_v2.py
index c48e562..538e21f 100644
--- a/test/test_new_role_v2.py
+++ b/test/test_new_role_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_ruleset.py b/test/test_new_ruleset.py
index 0ddcfba..4870140 100644
--- a/test/test_new_ruleset.py
+++ b/test/test_new_ruleset.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_saml_connection.py b/test/test_new_saml_connection.py
index 93902e8..0dddbac 100644
--- a/test/test_new_saml_connection.py
+++ b/test/test_new_saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_secondary_deployment.py b/test/test_new_secondary_deployment.py
index 7cf9c47..b1966f3 100644
--- a/test/test_new_secondary_deployment.py
+++ b/test/test_new_secondary_deployment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_store.py b/test/test_new_store.py
index be407c1..ee19e98 100644
--- a/test/test_new_store.py
+++ b/test/test_new_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_template_def.py b/test/test_new_template_def.py
index e2bb2ff..63c38d3 100644
--- a/test/test_new_template_def.py
+++ b/test/test_new_template_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_user.py b/test/test_new_user.py
index 91a7d2a..4f2c49f 100644
--- a/test/test_new_user.py
+++ b/test/test_new_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_new_webhook.py b/test/test_new_webhook.py
index 702502b..fd91d6e 100644
--- a/test/test_new_webhook.py
+++ b/test/test_new_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_notification.py b/test/test_notification.py
index 14188ce..5a19554 100644
--- a/test/test_notification.py
+++ b/test/test_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_notification_activation.py b/test/test_notification_activation.py
index 950509f..a83b031 100644
--- a/test/test_notification_activation.py
+++ b/test/test_notification_activation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_notification_list_item.py b/test/test_notification_list_item.py
index a673ee9..95386ec 100644
--- a/test/test_notification_list_item.py
+++ b/test/test_notification_list_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_okta_event.py b/test/test_okta_event.py
index aa5bcb8..fb4a0d9 100644
--- a/test/test_okta_event.py
+++ b/test/test_okta_event.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_okta_event_payload.py b/test/test_okta_event_payload.py
index d9cc4da..07cca67 100644
--- a/test/test_okta_event_payload.py
+++ b/test/test_okta_event_payload.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_okta_event_payload_data.py b/test/test_okta_event_payload_data.py
index b38e78f..4800ec5 100644
--- a/test/test_okta_event_payload_data.py
+++ b/test/test_okta_event_payload_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_okta_event_target.py b/test/test_okta_event_target.py
index 4b32cf3..a0adec4 100644
--- a/test/test_okta_event_target.py
+++ b/test/test_okta_event_target.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_one_time_code.py b/test/test_one_time_code.py
index 6d2401d..ff1300b 100644
--- a/test/test_one_time_code.py
+++ b/test/test_one_time_code.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_braze_policy.py b/test/test_outgoing_integration_braze_policy.py
index ba7a7a2..8da9b68 100644
--- a/test/test_outgoing_integration_braze_policy.py
+++ b/test/test_outgoing_integration_braze_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_clever_tap_policy.py b/test/test_outgoing_integration_clever_tap_policy.py
index de7f461..b90922f 100644
--- a/test/test_outgoing_integration_clever_tap_policy.py
+++ b/test/test_outgoing_integration_clever_tap_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_configuration.py b/test/test_outgoing_integration_configuration.py
index a9b0c8e..ad72268 100644
--- a/test/test_outgoing_integration_configuration.py
+++ b/test/test_outgoing_integration_configuration.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_iterable_policy.py b/test/test_outgoing_integration_iterable_policy.py
index 24b1137..cfceec6 100644
--- a/test/test_outgoing_integration_iterable_policy.py
+++ b/test/test_outgoing_integration_iterable_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_mo_engage_policy.py b/test/test_outgoing_integration_mo_engage_policy.py
index 8415f7c..6e23a59 100644
--- a/test/test_outgoing_integration_mo_engage_policy.py
+++ b/test/test_outgoing_integration_mo_engage_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_template.py b/test/test_outgoing_integration_template.py
index 313c09e..3d57b12 100644
--- a/test/test_outgoing_integration_template.py
+++ b/test/test_outgoing_integration_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_template_with_configuration_details.py b/test/test_outgoing_integration_template_with_configuration_details.py
index 01dd545..8f8ce25 100644
--- a/test/test_outgoing_integration_template_with_configuration_details.py
+++ b/test/test_outgoing_integration_template_with_configuration_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_templates.py b/test/test_outgoing_integration_templates.py
index c0d1ba1..4f61284 100644
--- a/test/test_outgoing_integration_templates.py
+++ b/test/test_outgoing_integration_templates.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_type.py b/test/test_outgoing_integration_type.py
index 60e0ced..c54e04c 100644
--- a/test/test_outgoing_integration_type.py
+++ b/test/test_outgoing_integration_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_outgoing_integration_types.py b/test/test_outgoing_integration_types.py
index 68c32e2..7258d52 100644
--- a/test/test_outgoing_integration_types.py
+++ b/test/test_outgoing_integration_types.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_patch_item_catalog_action.py b/test/test_patch_item_catalog_action.py
index faa3cc1..633efba 100644
--- a/test/test_patch_item_catalog_action.py
+++ b/test/test_patch_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_patch_many_items_catalog_action.py b/test/test_patch_many_items_catalog_action.py
index 359796e..e46e37e 100644
--- a/test/test_patch_many_items_catalog_action.py
+++ b/test/test_patch_many_items_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_pending_active_points_data.py b/test/test_pending_active_points_data.py
index a96b9fa..dae8c98 100644
--- a/test/test_pending_active_points_data.py
+++ b/test/test_pending_active_points_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_pending_active_points_notification.py b/test/test_pending_active_points_notification.py
index c275cdc..0d0494c 100644
--- a/test/test_pending_active_points_notification.py
+++ b/test/test_pending_active_points_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_pending_points_notification_policy.py b/test/test_pending_points_notification_policy.py
index becfd8b..2f5682c 100644
--- a/test/test_pending_points_notification_policy.py
+++ b/test/test_pending_points_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_picklist.py b/test/test_picklist.py
index 7f317a3..85968ec 100644
--- a/test/test_picklist.py
+++ b/test/test_picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_placeholder_details.py b/test/test_placeholder_details.py
index b98118e..e7aafe4 100644
--- a/test/test_placeholder_details.py
+++ b/test/test_placeholder_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_detail.py b/test/test_price_detail.py
index 523517e..a7b6317 100644
--- a/test/test_price_detail.py
+++ b/test/test_price_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_history_request.py b/test/test_price_history_request.py
index 82f92f3..927544f 100644
--- a/test/test_price_history_request.py
+++ b/test/test_price_history_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_history_response.py b/test/test_price_history_response.py
index 9af97a1..cd7ddbf 100644
--- a/test/test_price_history_response.py
+++ b/test/test_price_history_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_type.py b/test/test_price_type.py
index ac29624..a9ea523 100644
--- a/test/test_price_type.py
+++ b/test/test_price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_type_reference_detail.py b/test/test_price_type_reference_detail.py
index 8e3cf8e..183e4de 100644
--- a/test/test_price_type_reference_detail.py
+++ b/test/test_price_type_reference_detail.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_price_type_references.py b/test/test_price_type_references.py
index b0e6684..b34be8d 100644
--- a/test/test_price_type_references.py
+++ b/test/test_price_type_references.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_product.py b/test/test_product.py
index fc1ecab..3955202 100644
--- a/test/test_product.py
+++ b/test/test_product.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_product_search_match.py b/test/test_product_search_match.py
index 4a379f0..48951f4 100644
--- a/test/test_product_search_match.py
+++ b/test/test_product_search_match.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_product_unit_analytics.py b/test/test_product_unit_analytics.py
index c4c48d2..4957f6a 100644
--- a/test/test_product_unit_analytics.py
+++ b/test/test_product_unit_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_product_unit_analytics_data_point.py b/test/test_product_unit_analytics_data_point.py
index 4d84f2e..251e656 100644
--- a/test/test_product_unit_analytics_data_point.py
+++ b/test/test_product_unit_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_product_unit_analytics_totals.py b/test/test_product_unit_analytics_totals.py
index 935dcbf..bfcc2c1 100644
--- a/test/test_product_unit_analytics_totals.py
+++ b/test/test_product_unit_analytics_totals.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_profile_audiences_changes.py b/test/test_profile_audiences_changes.py
index 3a60718..bd6982c 100644
--- a/test/test_profile_audiences_changes.py
+++ b/test/test_profile_audiences_changes.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_projected_tier.py b/test/test_projected_tier.py
index e6f0156..14eea4b 100644
--- a/test/test_projected_tier.py
+++ b/test/test_projected_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_promote_experiment.py b/test/test_promote_experiment.py
index 03e9d26..11dec9a 100644
--- a/test/test_promote_experiment.py
+++ b/test/test_promote_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_redeem_referral_effect_props.py b/test/test_redeem_referral_effect_props.py
index a0346fd..590a4ec 100644
--- a/test/test_redeem_referral_effect_props.py
+++ b/test/test_redeem_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_referral.py b/test/test_referral.py
index 9a3417f..0d808fd 100644
--- a/test/test_referral.py
+++ b/test/test_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_referral_constraints.py b/test/test_referral_constraints.py
index 438484d..9e44854 100644
--- a/test/test_referral_constraints.py
+++ b/test/test_referral_constraints.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_referral_created_effect_props.py b/test/test_referral_created_effect_props.py
index 4e0ef2e..45b8932 100644
--- a/test/test_referral_created_effect_props.py
+++ b/test/test_referral_created_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_referral_rejection_reason.py b/test/test_referral_rejection_reason.py
index a1370a1..a2f44bf 100644
--- a/test/test_referral_rejection_reason.py
+++ b/test/test_referral_rejection_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_reject_coupon_effect_props.py b/test/test_reject_coupon_effect_props.py
index 6e8a5c5..bdeaee3 100644
--- a/test/test_reject_coupon_effect_props.py
+++ b/test/test_reject_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_reject_referral_effect_props.py b/test/test_reject_referral_effect_props.py
index 8db040e..c36c92e 100644
--- a/test/test_reject_referral_effect_props.py
+++ b/test/test_reject_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_remove_from_audience_effect_props.py b/test/test_remove_from_audience_effect_props.py
index 1619fcb..310c4b0 100644
--- a/test/test_remove_from_audience_effect_props.py
+++ b/test/test_remove_from_audience_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_remove_item_catalog_action.py b/test/test_remove_item_catalog_action.py
index b19ec06..12f44d1 100644
--- a/test/test_remove_item_catalog_action.py
+++ b/test/test_remove_item_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_remove_many_items_catalog_action.py b/test/test_remove_many_items_catalog_action.py
index a49b8d0..20b10c4 100644
--- a/test/test_remove_many_items_catalog_action.py
+++ b/test/test_remove_many_items_catalog_action.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_reopen_session_response.py b/test/test_reopen_session_response.py
index 45bb0b8..1d6faa4 100644
--- a/test/test_reopen_session_response.py
+++ b/test/test_reopen_session_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_reserve_coupon_effect_props.py b/test/test_reserve_coupon_effect_props.py
index 15d6e91..155bf97 100644
--- a/test/test_reserve_coupon_effect_props.py
+++ b/test/test_reserve_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_response_content_object.py b/test/test_response_content_object.py
index f5a60b1..0f0be21 100644
--- a/test/test_response_content_object.py
+++ b/test/test_response_content_object.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_return_integration_request.py b/test/test_return_integration_request.py
index 332f28a..88b00b9 100644
--- a/test/test_return_integration_request.py
+++ b/test/test_return_integration_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_returned_cart_item.py b/test/test_returned_cart_item.py
index b8f928d..f7bf7c8 100644
--- a/test/test_returned_cart_item.py
+++ b/test/test_returned_cart_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_revision.py b/test/test_revision.py
index 8074e27..329b357 100644
--- a/test/test_revision.py
+++ b/test/test_revision.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_revision_activation.py b/test/test_revision_activation.py
index 3d24d73..e930f61 100644
--- a/test/test_revision_activation.py
+++ b/test/test_revision_activation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_revision_activation_request.py b/test/test_revision_activation_request.py
index f69af5f..c71a66a 100644
--- a/test/test_revision_activation_request.py
+++ b/test/test_revision_activation_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_revision_version.py b/test/test_revision_version.py
index bd1bf09..084ffec 100644
--- a/test/test_revision_version.py
+++ b/test/test_revision_version.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -62,6 +62,7 @@ def make_instance(self, include_optional) -> RevisionVersion:
features = [
'coupons'
],
+ coupon_attributes = talon_one.models.coupon_attributes.couponAttributes(),
account_id = 56,
application_id = 56,
campaign_id = 56,
diff --git a/test/test_role.py b/test/test_role.py
index e5b851e..bebab57 100644
--- a/test/test_role.py
+++ b/test/test_role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_assign.py b/test/test_role_assign.py
index 5260e88..111ddb0 100644
--- a/test/test_role_assign.py
+++ b/test/test_role_assign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_membership.py b/test/test_role_membership.py
index b7e3ccb..d206b07 100644
--- a/test/test_role_membership.py
+++ b/test/test_role_membership.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2.py b/test/test_role_v2.py
index 97342a1..24e3763 100644
--- a/test/test_role_v2.py
+++ b/test/test_role_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2_application_details.py b/test/test_role_v2_application_details.py
index cde2ef9..7a52dc2 100644
--- a/test/test_role_v2_application_details.py
+++ b/test/test_role_v2_application_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -38,7 +38,9 @@ def make_instance(self, include_optional) -> RoleV2ApplicationDetails:
application = '',
campaign = '',
draft_campaign = '',
- tools = 'Tools permission set'
+ tools = 'Tools permission set',
+ thresholds = talon_one.models.roles_v2_thresholds.RolesV2Thresholds(
+ loyalty_points_limit = 100, )
)
else:
return RoleV2ApplicationDetails(
diff --git a/test/test_role_v2_base.py b/test/test_role_v2_base.py
index 9e97913..0b8df06 100644
--- a/test/test_role_v2_base.py
+++ b/test/test_role_v2_base.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2_permission_set.py b/test/test_role_v2_permission_set.py
index 0649f2f..e31bd9f 100644
--- a/test/test_role_v2_permission_set.py
+++ b/test/test_role_v2_permission_set.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2_permissions.py b/test/test_role_v2_permissions.py
index e5d344a..ee4d4f2 100644
--- a/test/test_role_v2_permissions.py
+++ b/test/test_role_v2_permissions.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2_readonly.py b/test/test_role_v2_readonly.py
index 41287f5..b7416b7 100644
--- a/test/test_role_v2_readonly.py
+++ b/test/test_role_v2_readonly.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_role_v2_roles_group.py b/test/test_role_v2_roles_group.py
index 4a9a7f2..abcd9e1 100644
--- a/test/test_role_v2_roles_group.py
+++ b/test/test_role_v2_roles_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_roles_v2_thresholds.py b/test/test_roles_v2_thresholds.py
new file mode 100644
index 0000000..e2ace9e
--- /dev/null
+++ b/test/test_roles_v2_thresholds.py
@@ -0,0 +1,51 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.roles_v2_thresholds import RolesV2Thresholds
+
+class TestRolesV2Thresholds(unittest.TestCase):
+ """RolesV2Thresholds unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> RolesV2Thresholds:
+ """Test RolesV2Thresholds
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `RolesV2Thresholds`
+ """
+ model = RolesV2Thresholds()
+ if include_optional:
+ return RolesV2Thresholds(
+ loyalty_points_limit = 100
+ )
+ else:
+ return RolesV2Thresholds(
+ )
+ """
+
+ def testRolesV2Thresholds(self):
+ """Test RolesV2Thresholds"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_rollback_added_loyalty_points_effect_props.py b/test/test_rollback_added_loyalty_points_effect_props.py
index 6ab3a13..7e553b6 100644
--- a/test/test_rollback_added_loyalty_points_effect_props.py
+++ b/test/test_rollback_added_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rollback_coupon_effect_props.py b/test/test_rollback_coupon_effect_props.py
index 070f3e9..cdaf19c 100644
--- a/test/test_rollback_coupon_effect_props.py
+++ b/test/test_rollback_coupon_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rollback_deducted_loyalty_points_effect_props.py b/test/test_rollback_deducted_loyalty_points_effect_props.py
index 172671c..6b25543 100644
--- a/test/test_rollback_deducted_loyalty_points_effect_props.py
+++ b/test/test_rollback_deducted_loyalty_points_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rollback_discount_effect_props.py b/test/test_rollback_discount_effect_props.py
index 6b88900..40c1dfd 100644
--- a/test/test_rollback_discount_effect_props.py
+++ b/test/test_rollback_discount_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rollback_increased_achievement_progress_effect_props.py b/test/test_rollback_increased_achievement_progress_effect_props.py
index ee2d62f..028695a 100644
--- a/test/test_rollback_increased_achievement_progress_effect_props.py
+++ b/test/test_rollback_increased_achievement_progress_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rollback_referral_effect_props.py b/test/test_rollback_referral_effect_props.py
index c400e26..0650018 100644
--- a/test/test_rollback_referral_effect_props.py
+++ b/test/test_rollback_referral_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rule.py b/test/test_rule.py
index 8b8c7a1..4bb1a07 100644
--- a/test/test_rule.py
+++ b/test/test_rule.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rule_failure_reason.py b/test/test_rule_failure_reason.py
index b2aa339..a475df8 100644
--- a/test/test_rule_failure_reason.py
+++ b/test/test_rule_failure_reason.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_rule_metadata.py b/test/test_rule_metadata.py
new file mode 100644
index 0000000..79ce751
--- /dev/null
+++ b/test/test_rule_metadata.py
@@ -0,0 +1,55 @@
+# coding: utf-8
+
+"""
+ Talon.One API
+
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
+
+ The version of the OpenAPI document:
+ Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+ Do not edit the class manually.
+""" # noqa: E501
+
+
+import unittest
+
+from talon_one.models.rule_metadata import RuleMetadata
+
+class TestRuleMetadata(unittest.TestCase):
+ """RuleMetadata unit test stubs"""
+
+ def setUp(self):
+ pass
+
+ def tearDown(self):
+ pass
+
+ def make_instance(self, include_optional) -> RuleMetadata:
+ """Test RuleMetadata
+ include_optional is a boolean, when False only required
+ params are included, when True both required and
+ optional params are included """
+ # uncomment below to create an instance of `RuleMetadata`
+ """
+ model = RuleMetadata()
+ if include_optional:
+ return RuleMetadata(
+ title = 'Give discount via coupon',
+ display_name = '20% off all shoes!',
+ display_description = 'Get a 20% discount on all shoes during Thanksgiving! Offer valid till Dec 5 only.',
+ related_data = 'https://example.com/discounts/20-off-shoes.png'
+ )
+ else:
+ return RuleMetadata(
+ title = 'Give discount via coupon',
+ )
+ """
+
+ def testRuleMetadata(self):
+ """Test RuleMetadata"""
+ # inst_req_only = self.make_instance(include_optional=False)
+ # inst_req_and_optional = self.make_instance(include_optional=True)
+
+if __name__ == '__main__':
+ unittest.main()
diff --git a/test/test_ruleset.py b/test/test_ruleset.py
index b476b2d..002190f 100644
--- a/test/test_ruleset.py
+++ b/test/test_ruleset.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_saml_connection.py b/test/test_saml_connection.py
index 6342cfa..0573e83 100644
--- a/test/test_saml_connection.py
+++ b/test/test_saml_connection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_saml_connection_internal.py b/test/test_saml_connection_internal.py
index 1996da6..bd61bb1 100644
--- a/test/test_saml_connection_internal.py
+++ b/test/test_saml_connection_internal.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_saml_connection_metadata.py b/test/test_saml_connection_metadata.py
index 0a85760..12a3523 100644
--- a/test/test_saml_connection_metadata.py
+++ b/test/test_saml_connection_metadata.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_saml_login_endpoint.py b/test/test_saml_login_endpoint.py
index 38a6e5c..494bf89 100644
--- a/test/test_saml_login_endpoint.py
+++ b/test/test_saml_login_endpoint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_base_group.py b/test/test_scim_base_group.py
index 0221836..bd3db89 100644
--- a/test/test_scim_base_group.py
+++ b/test/test_scim_base_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_base_user.py b/test/test_scim_base_user.py
index 832b27b..2517e36 100644
--- a/test/test_scim_base_user.py
+++ b/test/test_scim_base_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_base_user_name.py b/test/test_scim_base_user_name.py
index b0dddf6..5c15e7e 100644
--- a/test/test_scim_base_user_name.py
+++ b/test/test_scim_base_user_name.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_group.py b/test/test_scim_group.py
index 94901b6..34e006b 100644
--- a/test/test_scim_group.py
+++ b/test/test_scim_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_group_member.py b/test/test_scim_group_member.py
index 8f4e778..752d26f 100644
--- a/test/test_scim_group_member.py
+++ b/test/test_scim_group_member.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_groups_list_response.py b/test/test_scim_groups_list_response.py
index 44abf78..9883130 100644
--- a/test/test_scim_groups_list_response.py
+++ b/test/test_scim_groups_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_new_user.py b/test/test_scim_new_user.py
index cbc9caf..ac6ac92 100644
--- a/test/test_scim_new_user.py
+++ b/test/test_scim_new_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_patch_operation.py b/test/test_scim_patch_operation.py
index 9f618d7..b444ff5 100644
--- a/test/test_scim_patch_operation.py
+++ b/test/test_scim_patch_operation.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_patch_request.py b/test/test_scim_patch_request.py
index dd66293..4976f31 100644
--- a/test/test_scim_patch_request.py
+++ b/test/test_scim_patch_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_resource.py b/test/test_scim_resource.py
index 8a9c9fb..3752e2a 100644
--- a/test/test_scim_resource.py
+++ b/test/test_scim_resource.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_resource_types_list_response.py b/test/test_scim_resource_types_list_response.py
index 6b09fda..24a7b7d 100644
--- a/test/test_scim_resource_types_list_response.py
+++ b/test/test_scim_resource_types_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_schema_resource.py b/test/test_scim_schema_resource.py
index 3d61a9e..88a38b5 100644
--- a/test/test_scim_schema_resource.py
+++ b/test/test_scim_schema_resource.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_schemas_list_response.py b/test/test_scim_schemas_list_response.py
index e989241..6b22e6c 100644
--- a/test/test_scim_schemas_list_response.py
+++ b/test/test_scim_schemas_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response.py b/test/test_scim_service_provider_config_response.py
index 34b7f34..72ec9c7 100644
--- a/test/test_scim_service_provider_config_response.py
+++ b/test/test_scim_service_provider_config_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response_bulk.py b/test/test_scim_service_provider_config_response_bulk.py
index 55dd165..0aa2cca 100644
--- a/test/test_scim_service_provider_config_response_bulk.py
+++ b/test/test_scim_service_provider_config_response_bulk.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response_change_password.py b/test/test_scim_service_provider_config_response_change_password.py
index 427d93e..4d1fd07 100644
--- a/test/test_scim_service_provider_config_response_change_password.py
+++ b/test/test_scim_service_provider_config_response_change_password.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response_filter.py b/test/test_scim_service_provider_config_response_filter.py
index 2e37e1f..7abae96 100644
--- a/test/test_scim_service_provider_config_response_filter.py
+++ b/test/test_scim_service_provider_config_response_filter.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response_patch.py b/test/test_scim_service_provider_config_response_patch.py
index f6360fd..50a826c 100644
--- a/test/test_scim_service_provider_config_response_patch.py
+++ b/test/test_scim_service_provider_config_response_patch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_service_provider_config_response_sort.py b/test/test_scim_service_provider_config_response_sort.py
index e648d00..7588e16 100644
--- a/test/test_scim_service_provider_config_response_sort.py
+++ b/test/test_scim_service_provider_config_response_sort.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_user.py b/test/test_scim_user.py
index 67beb19..b09c6a0 100644
--- a/test/test_scim_user.py
+++ b/test/test_scim_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_scim_users_list_response.py b/test/test_scim_users_list_response.py
index 5f7bb96..d89102b 100644
--- a/test/test_scim_users_list_response.py
+++ b/test/test_scim_users_list_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_secondary_deployment.py b/test/test_secondary_deployment.py
index 935c691..ac4722f 100644
--- a/test/test_secondary_deployment.py
+++ b/test/test_secondary_deployment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_session.py b/test/test_session.py
index 18ab57c..bb06951 100644
--- a/test/test_session.py
+++ b/test/test_session.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_set_discount_effect_props.py b/test/test_set_discount_effect_props.py
index 1daba4b..693a298 100644
--- a/test/test_set_discount_effect_props.py
+++ b/test/test_set_discount_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_set_discount_per_additional_cost_effect_props.py b/test/test_set_discount_per_additional_cost_effect_props.py
index e6730c3..f16b847 100644
--- a/test/test_set_discount_per_additional_cost_effect_props.py
+++ b/test/test_set_discount_per_additional_cost_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_set_discount_per_additional_cost_per_item_effect_props.py b/test/test_set_discount_per_additional_cost_per_item_effect_props.py
index b037fbc..bb571b5 100644
--- a/test/test_set_discount_per_additional_cost_per_item_effect_props.py
+++ b/test/test_set_discount_per_additional_cost_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_set_discount_per_item_effect_props.py b/test/test_set_discount_per_item_effect_props.py
index f73cc7e..9d558b7 100644
--- a/test/test_set_discount_per_item_effect_props.py
+++ b/test/test_set_discount_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_set_loyalty_points_expiry_date_effect_props.py b/test/test_set_loyalty_points_expiry_date_effect_props.py
index b1f5e98..e336102 100644
--- a/test/test_set_loyalty_points_expiry_date_effect_props.py
+++ b/test/test_set_loyalty_points_expiry_date_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_show_bundle_metadata_effect_props.py b/test/test_show_bundle_metadata_effect_props.py
index f243f65..8cc50bf 100644
--- a/test/test_show_bundle_metadata_effect_props.py
+++ b/test/test_show_bundle_metadata_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_show_notification_effect_props.py b/test/test_show_notification_effect_props.py
index 10afbe4..bd96bc8 100644
--- a/test/test_show_notification_effect_props.py
+++ b/test/test_show_notification_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_sku_unit_analytics.py b/test/test_sku_unit_analytics.py
index 45439a9..686f2b5 100644
--- a/test/test_sku_unit_analytics.py
+++ b/test/test_sku_unit_analytics.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_sku_unit_analytics_data_point.py b/test/test_sku_unit_analytics_data_point.py
index 240d01e..382175a 100644
--- a/test/test_sku_unit_analytics_data_point.py
+++ b/test/test_sku_unit_analytics_data_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_slot_def.py b/test/test_slot_def.py
index 5ee2436..33cb666 100644
--- a/test/test_slot_def.py
+++ b/test/test_slot_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_sso_config.py b/test/test_sso_config.py
index de9eb0a..551dbcf 100644
--- a/test/test_sso_config.py
+++ b/test/test_sso_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_store.py b/test/test_store.py
index 9fe7ac1..3e74a67 100644
--- a/test/test_store.py
+++ b/test/test_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_changed_item.py b/test/test_strikethrough_changed_item.py
index 99450e8..c5ded87 100644
--- a/test/test_strikethrough_changed_item.py
+++ b/test/test_strikethrough_changed_item.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_custom_effect_per_item_props.py b/test/test_strikethrough_custom_effect_per_item_props.py
index 5d4bcd4..6bd0dbf 100644
--- a/test/test_strikethrough_custom_effect_per_item_props.py
+++ b/test/test_strikethrough_custom_effect_per_item_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_debug_response.py b/test/test_strikethrough_debug_response.py
index 91d0ea9..f99b8a0 100644
--- a/test/test_strikethrough_debug_response.py
+++ b/test/test_strikethrough_debug_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_effect.py b/test/test_strikethrough_effect.py
index fa986d3..231fcad 100644
--- a/test/test_strikethrough_effect.py
+++ b/test/test_strikethrough_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_labeling_notification.py b/test/test_strikethrough_labeling_notification.py
index 9bbd87a..0ffcdae 100644
--- a/test/test_strikethrough_labeling_notification.py
+++ b/test/test_strikethrough_labeling_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_set_discount_per_item_effect_props.py b/test/test_strikethrough_set_discount_per_item_effect_props.py
index 22fa660..b48bf24 100644
--- a/test/test_strikethrough_set_discount_per_item_effect_props.py
+++ b/test/test_strikethrough_set_discount_per_item_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_set_discount_per_item_member_effect_props.py b/test/test_strikethrough_set_discount_per_item_member_effect_props.py
index 89e2ed1..cb49197 100644
--- a/test/test_strikethrough_set_discount_per_item_member_effect_props.py
+++ b/test/test_strikethrough_set_discount_per_item_member_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_strikethrough_trigger.py b/test/test_strikethrough_trigger.py
index 6ff5695..24c4054 100644
--- a/test/test_strikethrough_trigger.py
+++ b/test/test_strikethrough_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_summarize_campaign_store_budget200_response.py b/test/test_summarize_campaign_store_budget200_response.py
index d0a61c3..ac5ba5e 100644
--- a/test/test_summarize_campaign_store_budget200_response.py
+++ b/test/test_summarize_campaign_store_budget200_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_summary_campaign_store_budget.py b/test/test_summary_campaign_store_budget.py
index 4e27042..ac07e60 100644
--- a/test/test_summary_campaign_store_budget.py
+++ b/test/test_summary_campaign_store_budget.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_talang_attribute.py b/test/test_talang_attribute.py
index 88f1aed..89c5c90 100644
--- a/test/test_talang_attribute.py
+++ b/test/test_talang_attribute.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_talang_attribute_visibility.py b/test/test_talang_attribute_visibility.py
index cbc1372..e2b2af1 100644
--- a/test/test_talang_attribute_visibility.py
+++ b/test/test_talang_attribute_visibility.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_template_arg_def.py b/test/test_template_arg_def.py
index f542853..45cf497 100644
--- a/test/test_template_arg_def.py
+++ b/test/test_template_arg_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_template_def.py b/test/test_template_def.py
index 949dc56..0885f88 100644
--- a/test/test_template_def.py
+++ b/test/test_template_def.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_template_limit_config.py b/test/test_template_limit_config.py
index 84d2b84..0ec99ef 100644
--- a/test/test_template_limit_config.py
+++ b/test/test_template_limit_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier.py b/test/test_tier.py
index 296a6a8..c10d99f 100644
--- a/test/test_tier.py
+++ b/test/test_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_downgrade_data.py b/test/test_tier_downgrade_data.py
index 903422a..5d52dc1 100644
--- a/test/test_tier_downgrade_data.py
+++ b/test/test_tier_downgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_downgrade_notification.py b/test/test_tier_downgrade_notification.py
index c03dfda..daac9b6 100644
--- a/test/test_tier_downgrade_notification.py
+++ b/test/test_tier_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_downgrade_notification_policy.py b/test/test_tier_downgrade_notification_policy.py
index a491b09..747e022 100644
--- a/test/test_tier_downgrade_notification_policy.py
+++ b/test/test_tier_downgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_upgrade_data.py b/test/test_tier_upgrade_data.py
index d687f8d..393d0ea 100644
--- a/test/test_tier_upgrade_data.py
+++ b/test/test_tier_upgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_upgrade_notification.py b/test/test_tier_upgrade_notification.py
index 875e414..1157bb4 100644
--- a/test/test_tier_upgrade_notification.py
+++ b/test/test_tier_upgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_upgrade_notification_policy.py b/test/test_tier_upgrade_notification_policy.py
index d62f511..688b41d 100644
--- a/test/test_tier_upgrade_notification_policy.py
+++ b/test/test_tier_upgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_will_downgrade_data.py b/test/test_tier_will_downgrade_data.py
index 6b11e43..36990b0 100644
--- a/test/test_tier_will_downgrade_data.py
+++ b/test/test_tier_will_downgrade_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_will_downgrade_notification.py b/test/test_tier_will_downgrade_notification.py
index 9437b32..b7560b0 100644
--- a/test/test_tier_will_downgrade_notification.py
+++ b/test/test_tier_will_downgrade_notification.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_will_downgrade_notification_policy.py b/test/test_tier_will_downgrade_notification_policy.py
index 67896fe..925b5d1 100644
--- a/test/test_tier_will_downgrade_notification_policy.py
+++ b/test/test_tier_will_downgrade_notification_policy.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_tier_will_downgrade_notification_trigger.py b/test/test_tier_will_downgrade_notification_trigger.py
index 79b574e..ab9f057 100644
--- a/test/test_tier_will_downgrade_notification_trigger.py
+++ b/test/test_tier_will_downgrade_notification_trigger.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_time_point.py b/test/test_time_point.py
index 4f04152..b46ce6c 100644
--- a/test/test_time_point.py
+++ b/test/test_time_point.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_transfer_loyalty_card.py b/test/test_transfer_loyalty_card.py
index 01ce796..6c5608d 100644
--- a/test/test_transfer_loyalty_card.py
+++ b/test/test_transfer_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_trigger_webhook_effect_props.py b/test/test_trigger_webhook_effect_props.py
index 83d428b..2fed4c0 100644
--- a/test/test_trigger_webhook_effect_props.py
+++ b/test/test_trigger_webhook_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_two_fa_config.py b/test/test_two_fa_config.py
index dc43a2c..e5e2c82 100644
--- a/test/test_two_fa_config.py
+++ b/test/test_two_fa_config.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_account.py b/test/test_update_account.py
index 4e2f5ab..a31341c 100644
--- a/test/test_update_account.py
+++ b/test/test_update_account.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_achievement.py b/test/test_update_achievement.py
index 97c9b29..570d03d 100644
--- a/test/test_update_achievement.py
+++ b/test/test_update_achievement.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_achievement_v2.py b/test/test_update_achievement_v2.py
index 2a1f833..74a213f 100644
--- a/test/test_update_achievement_v2.py
+++ b/test/test_update_achievement_v2.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_application.py b/test/test_update_application.py
index 88bf359..b7b76dc 100644
--- a/test/test_update_application.py
+++ b/test/test_update_application.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_application_api_key.py b/test/test_update_application_api_key.py
index 9cf9334..bb7ca64 100644
--- a/test/test_update_application_api_key.py
+++ b/test/test_update_application_api_key.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_application_cif.py b/test/test_update_application_cif.py
index 39a045a..994a41c 100644
--- a/test/test_update_application_cif.py
+++ b/test/test_update_application_cif.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_attribute_effect_props.py b/test/test_update_attribute_effect_props.py
index 8402603..5a623c9 100644
--- a/test/test_update_attribute_effect_props.py
+++ b/test/test_update_attribute_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_audience.py b/test/test_update_audience.py
index 025971c..f730f8b 100644
--- a/test/test_update_audience.py
+++ b/test/test_update_audience.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_blueprint.py b/test/test_update_blueprint.py
index a370ce7..3e3e36e 100644
--- a/test/test_update_blueprint.py
+++ b/test/test_update_blueprint.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_campaign.py b/test/test_update_campaign.py
index 4564611..dbcaf42 100644
--- a/test/test_update_campaign.py
+++ b/test/test_update_campaign.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -61,7 +61,8 @@ def make_instance(self, include_optional) -> UpdateCampaign:
campaign_groups = [1, 3],
evaluation_group_id = 2,
type = 'advanced',
- linked_store_ids = [1, 2, 3]
+ linked_store_ids = [1, 2, 3],
+ coupon_attributes = None
)
else:
return UpdateCampaign(
diff --git a/test/test_update_campaign_collection.py b/test/test_update_campaign_collection.py
index ea65268..a5e0a84 100644
--- a/test/test_update_campaign_collection.py
+++ b/test/test_update_campaign_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_campaign_evaluation_group.py b/test/test_update_campaign_evaluation_group.py
index 71ccad9..edf12ba 100644
--- a/test/test_update_campaign_evaluation_group.py
+++ b/test/test_update_campaign_evaluation_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_campaign_group.py b/test/test_update_campaign_group.py
index df9f858..77210b8 100644
--- a/test/test_update_campaign_group.py
+++ b/test/test_update_campaign_group.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_campaign_template.py b/test/test_update_campaign_template.py
index a4bac61..b536754 100644
--- a/test/test_update_campaign_template.py
+++ b/test/test_update_campaign_template.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_catalog.py b/test/test_update_catalog.py
index ddb534d..d9b59ad 100644
--- a/test/test_update_catalog.py
+++ b/test/test_update_catalog.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_collection.py b/test/test_update_collection.py
index 02cf3cd..3b99842 100644
--- a/test/test_update_collection.py
+++ b/test/test_update_collection.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_coupon.py b/test/test_update_coupon.py
index 2dc22bf..16a7342 100644
--- a/test/test_update_coupon.py
+++ b/test/test_update_coupon.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_coupon_batch.py b/test/test_update_coupon_batch.py
index 0b043b7..0b2b453 100644
--- a/test/test_update_coupon_batch.py
+++ b/test/test_update_coupon_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_coupons_data.py b/test/test_update_coupons_data.py
index 9a75b1b..b544031 100644
--- a/test/test_update_coupons_data.py
+++ b/test/test_update_coupons_data.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_custom_effect.py b/test/test_update_custom_effect.py
index b4dcc34..d370d0e 100644
--- a/test/test_update_custom_effect.py
+++ b/test/test_update_custom_effect.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_customer_profile_v2409_response.py b/test/test_update_customer_profile_v2409_response.py
index 47a5592..bbf714c 100644
--- a/test/test_update_customer_profile_v2409_response.py
+++ b/test/test_update_customer_profile_v2409_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_customer_session_v2409_response.py b/test/test_update_customer_session_v2409_response.py
index 2cd5dd5..fdd01e4 100644
--- a/test/test_update_customer_session_v2409_response.py
+++ b/test/test_update_customer_session_v2409_response.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_experiment.py b/test/test_update_experiment.py
index ed3ded7..02e87c7 100644
--- a/test/test_update_experiment.py
+++ b/test/test_update_experiment.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -63,7 +63,8 @@ def make_instance(self, include_optional) -> UpdateExperiment:
campaign_groups = [1, 3],
evaluation_group_id = 2,
type = 'advanced',
- linked_store_ids = [1, 2, 3], )
+ linked_store_ids = [1, 2, 3],
+ coupon_attributes = talon_one.models.coupon_attributes.couponAttributes(), )
)
else:
return UpdateExperiment(
@@ -95,7 +96,8 @@ def make_instance(self, include_optional) -> UpdateExperiment:
campaign_groups = [1, 3],
evaluation_group_id = 2,
type = 'advanced',
- linked_store_ids = [1, 2, 3], ),
+ linked_store_ids = [1, 2, 3],
+ coupon_attributes = talon_one.models.coupon_attributes.couponAttributes(), ),
)
"""
diff --git a/test/test_update_experiment_variant.py b/test/test_update_experiment_variant.py
index 9d72e55..d990960 100644
--- a/test/test_update_experiment_variant.py
+++ b/test/test_update_experiment_variant.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_experiment_variant_array.py b/test/test_update_experiment_variant_array.py
index fb1b4a4..94b6e69 100644
--- a/test/test_update_experiment_variant_array.py
+++ b/test/test_update_experiment_variant_array.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_experiment_variant_name.py b/test/test_update_experiment_variant_name.py
index 93bad2d..0188dd1 100644
--- a/test/test_update_experiment_variant_name.py
+++ b/test/test_update_experiment_variant_name.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_loyalty_card.py b/test/test_update_loyalty_card.py
index 09bac82..4f6aa99 100644
--- a/test/test_update_loyalty_card.py
+++ b/test/test_update_loyalty_card.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_loyalty_card_request.py b/test/test_update_loyalty_card_request.py
index 8d07ab2..b6cabff 100644
--- a/test/test_update_loyalty_card_request.py
+++ b/test/test_update_loyalty_card_request.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_loyalty_program.py b/test/test_update_loyalty_program.py
index 7d1fab1..8306f3f 100644
--- a/test/test_update_loyalty_program.py
+++ b/test/test_update_loyalty_program.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_loyalty_program_tier.py b/test/test_update_loyalty_program_tier.py
index 2626a2e..ee09e29 100644
--- a/test/test_update_loyalty_program_tier.py
+++ b/test/test_update_loyalty_program_tier.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_picklist.py b/test/test_update_picklist.py
index 5fa82b7..befb9cf 100644
--- a/test/test_update_picklist.py
+++ b/test/test_update_picklist.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_price_type.py b/test/test_update_price_type.py
index a01073b..3feaeb1 100644
--- a/test/test_update_price_type.py
+++ b/test/test_update_price_type.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_referral.py b/test/test_update_referral.py
index 3b6000c..5f887eb 100644
--- a/test/test_update_referral.py
+++ b/test/test_update_referral.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_referral_batch.py b/test/test_update_referral_batch.py
index 808181b..0e935e5 100644
--- a/test/test_update_referral_batch.py
+++ b/test/test_update_referral_batch.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_role.py b/test/test_update_role.py
index b3f2e74..3cba957 100644
--- a/test/test_update_role.py
+++ b/test/test_update_role.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_store.py b/test/test_update_store.py
index efb418e..54e05ed 100644
--- a/test/test_update_store.py
+++ b/test/test_update_store.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_update_user.py b/test/test_update_user.py
index e0e0f0f..44623fa 100644
--- a/test/test_update_user.py
+++ b/test/test_update_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_user.py b/test/test_user.py
index d077ba2..f8b3270 100644
--- a/test/test_user.py
+++ b/test/test_user.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_user_entity.py b/test/test_user_entity.py
index 3448bdc..f165290 100644
--- a/test/test_user_entity.py
+++ b/test/test_user_entity.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_value_map.py b/test/test_value_map.py
index 30bc489..569e466 100644
--- a/test/test_value_map.py
+++ b/test/test_value_map.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook.py b/test/test_webhook.py
index be67927..ff94dd4 100644
--- a/test/test_webhook.py
+++ b/test/test_webhook.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook_authentication.py b/test/test_webhook_authentication.py
index 83c5118..458fc06 100644
--- a/test/test_webhook_authentication.py
+++ b/test/test_webhook_authentication.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook_authentication_data_basic.py b/test/test_webhook_authentication_data_basic.py
index e2fca3c..cbe459d 100644
--- a/test/test_webhook_authentication_data_basic.py
+++ b/test/test_webhook_authentication_data_basic.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook_authentication_data_custom.py b/test/test_webhook_authentication_data_custom.py
index 4dea2c2..4b3bdd1 100644
--- a/test/test_webhook_authentication_data_custom.py
+++ b/test/test_webhook_authentication_data_custom.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook_authentication_webhook_ref.py b/test/test_webhook_authentication_webhook_ref.py
index 17c967e..161b22f 100644
--- a/test/test_webhook_authentication_webhook_ref.py
+++ b/test/test_webhook_authentication_webhook_ref.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_webhook_with_outgoing_integration_details.py b/test/test_webhook_with_outgoing_integration_details.py
index 69b0633..d56fef7 100644
--- a/test/test_webhook_with_outgoing_integration_details.py
+++ b/test/test_webhook_with_outgoing_integration_details.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)
diff --git a/test/test_will_award_giveaway_effect_props.py b/test/test_will_award_giveaway_effect_props.py
index b1aeb05..fd7d439 100644
--- a/test/test_will_award_giveaway_effect_props.py
+++ b/test/test_will_award_giveaway_effect_props.py
@@ -3,7 +3,7 @@
"""
Talon.One API
- Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`
+ Use the Talon.One API to integrate with your application and to manage applications and campaigns: - Use the operations in the [Integration API section](#integration-api) to integrate with our platform. - Use the operation in the [Management API section](#management-api) to manage applications and campaigns. ## Determining the base URL of the endpoints The API is available at the same hostname as your Campaign Manager deployment. For example, if you access the Campaign Manager at `https://yourbaseurl.talon.one/`, the URL for the [updateCustomerSessionV2](https://docs.talon.one/integration-api#tag/Customer-sessions/operation/updateCustomerSessionV2) endpoint is `https://yourbaseurl.talon.one/v2/customer_sessions/{Id}`.
The version of the OpenAPI document:
Generated by OpenAPI Generator (https://openapi-generator.tech)