svix 1.10.0 → 1.12.0

data/lib/svix/models/template_out.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -19,6 +19,8 @@ module Svix
 
     attr_accessor :description
 
+    attr_accessor :feature_flag
+
     attr_accessor :filter_types
 
     attr_accessor :id
@@ -44,6 +46,7 @@ module Svix
       {
         :'created_at' => :'createdAt',
         :'description' => :'description',
+        :'feature_flag' => :'featureFlag',
         :'filter_types' => :'filterTypes',
         :'id' => :'id',
         :'instructions' => :'instructions',
@@ -67,6 +70,7 @@ module Svix
       {
         :'created_at' => :'Time',
         :'description' => :'String',
+        :'feature_flag' => :'String',
         :'filter_types' => :'Array<String>',
         :'id' => :'String',
         :'instructions' => :'String',
@@ -83,6 +87,7 @@ module Svix
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'feature_flag',
         :'filter_types',
         :'instructions_link',
       ])
@@ -111,6 +116,10 @@ module Svix
         self.description = attributes[:'description']
       end
 
+      if attributes.key?(:'feature_flag')
+        self.feature_flag = attributes[:'feature_flag']
+      end
+
       if attributes.key?(:'filter_types')
         if (value = attributes[:'filter_types']).is_a?(Array)
           self.filter_types = value
@@ -166,6 +175,15 @@ module Svix
         invalid_properties.push('invalid value for "description", description cannot be nil.')
       end
 
+      if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+        invalid_properties.push('invalid value for "feature_flag", the character length must be smaller than or equal to 256.')
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !@feature_flag.nil? && @feature_flag !~ pattern
+        invalid_properties.push("invalid value for \"feature_flag\", must conform to the pattern #{pattern}.")
+      end
+
       if !@filter_types.nil? && @filter_types.length < 1
         invalid_properties.push('invalid value for "filter_types", number of items must be greater than or equal to 1.')
       end
@@ -210,6 +228,8 @@ module Svix
     def valid?
       return false if @created_at.nil?
       return false if @description.nil?
+      return false if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+      return false if !@feature_flag.nil? && @feature_flag !~ Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
       return false if !@filter_types.nil? && @filter_types.length < 1
       return false if @id.nil?
       return false if @instructions.nil?
@@ -222,6 +242,21 @@ module Svix
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] feature_flag Value to be assigned
+    def feature_flag=(feature_flag)
+      if !feature_flag.nil? && feature_flag.to_s.length > 256
+        fail ArgumentError, 'invalid value for "feature_flag", the character length must be smaller than or equal to 256.'
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !feature_flag.nil? && feature_flag !~ pattern
+        fail ArgumentError, "invalid value for \"feature_flag\", must conform to the pattern #{pattern}."
+      end
+
+      @feature_flag = feature_flag
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] filter_types Value to be assigned
     def filter_types=(filter_types)
@@ -239,6 +274,7 @@ module Svix
       self.class == o.class &&
           created_at == o.created_at &&
           description == o.description &&
+          feature_flag == o.feature_flag &&
           filter_types == o.filter_types &&
           id == o.id &&
           instructions == o.instructions &&
@@ -260,7 +296,7 @@ module Svix
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [created_at, description, filter_types, id, instructions, instructions_link, kind, logo, name, org_id, transformation, updated_at].hash
+      [created_at, description, feature_flag, filter_types, id, instructions, instructions_link, kind, logo, name, org_id, transformation, updated_at].hash
     end
 
     # Builds the object from hash

data/lib/svix/models/template_patch.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -17,6 +17,8 @@ module Svix
   class TemplatePatch
     attr_accessor :description
 
+    attr_accessor :feature_flag
+
     attr_accessor :filter_types
 
     attr_accessor :instructions
@@ -33,6 +35,7 @@ module Svix
     def self.attribute_map
       {
         :'description' => :'description',
+        :'feature_flag' => :'featureFlag',
         :'filter_types' => :'filterTypes',
         :'instructions' => :'instructions',
         :'instructions_link' => :'instructionsLink',
@@ -51,6 +54,7 @@ module Svix
     def self.openapi_types
       {
         :'description' => :'String',
+        :'feature_flag' => :'String',
         :'filter_types' => :'Array<String>',
         :'instructions' => :'String',
         :'instructions_link' => :'String',
@@ -63,6 +67,7 @@ module Svix
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'feature_flag',
         :'filter_types',
         :'instructions_link',
       ])
@@ -87,6 +92,10 @@ module Svix
         self.description = attributes[:'description']
       end
 
+      if attributes.key?(:'feature_flag')
+        self.feature_flag = attributes[:'feature_flag']
+      end
+
       if attributes.key?(:'filter_types')
         if (value = attributes[:'filter_types']).is_a?(Array)
           self.filter_types = value
@@ -118,6 +127,15 @@ module Svix
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
+      if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+        invalid_properties.push('invalid value for "feature_flag", the character length must be smaller than or equal to 256.')
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !@feature_flag.nil? && @feature_flag !~ pattern
+        invalid_properties.push("invalid value for \"feature_flag\", must conform to the pattern #{pattern}.")
+      end
+
       if !@filter_types.nil? && @filter_types.length < 1
         invalid_properties.push('invalid value for "filter_types", number of items must be greater than or equal to 1.')
       end
@@ -136,12 +154,29 @@ module Svix
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
+      return false if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+      return false if !@feature_flag.nil? && @feature_flag !~ Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
       return false if !@filter_types.nil? && @filter_types.length < 1
       return false if !@transformation.nil? && @transformation.to_s.length > 51200
       return false if !@transformation.nil? && @transformation.to_s.length < 10
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] feature_flag Value to be assigned
+    def feature_flag=(feature_flag)
+      if !feature_flag.nil? && feature_flag.to_s.length > 256
+        fail ArgumentError, 'invalid value for "feature_flag", the character length must be smaller than or equal to 256.'
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !feature_flag.nil? && feature_flag !~ pattern
+        fail ArgumentError, "invalid value for \"feature_flag\", must conform to the pattern #{pattern}."
+      end
+
+      @feature_flag = feature_flag
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] filter_types Value to be assigned
     def filter_types=(filter_types)
@@ -172,6 +207,7 @@ module Svix
       return true if self.equal?(o)
       self.class == o.class &&
           description == o.description &&
+          feature_flag == o.feature_flag &&
           filter_types == o.filter_types &&
           instructions == o.instructions &&
           instructions_link == o.instructions_link &&
@@ -189,7 +225,7 @@ module Svix
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [description, filter_types, instructions, instructions_link, logo, name, transformation].hash
+      [description, feature_flag, filter_types, instructions, instructions_link, logo, name, transformation].hash
     end
 
     # Builds the object from hash

data/lib/svix/models/template_update.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -17,6 +17,8 @@ module Svix
   class TemplateUpdate
     attr_accessor :description
 
+    attr_accessor :feature_flag
+
     attr_accessor :filter_types
 
     attr_accessor :instructions
@@ -33,6 +35,7 @@ module Svix
     def self.attribute_map
       {
         :'description' => :'description',
+        :'feature_flag' => :'featureFlag',
         :'filter_types' => :'filterTypes',
         :'instructions' => :'instructions',
         :'instructions_link' => :'instructionsLink',
@@ -51,6 +54,7 @@ module Svix
     def self.openapi_types
       {
         :'description' => :'String',
+        :'feature_flag' => :'String',
         :'filter_types' => :'Array<String>',
         :'instructions' => :'String',
         :'instructions_link' => :'String',
@@ -63,6 +67,7 @@ module Svix
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'feature_flag',
         :'filter_types',
         :'instructions_link',
       ])
@@ -89,6 +94,10 @@ module Svix
         self.description = ''
       end
 
+      if attributes.key?(:'feature_flag')
+        self.feature_flag = attributes[:'feature_flag']
+      end
+
       if attributes.key?(:'filter_types')
         if (value = attributes[:'filter_types']).is_a?(Array)
           self.filter_types = value
@@ -124,6 +133,15 @@ module Svix
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
+      if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+        invalid_properties.push('invalid value for "feature_flag", the character length must be smaller than or equal to 256.')
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !@feature_flag.nil? && @feature_flag !~ pattern
+        invalid_properties.push("invalid value for \"feature_flag\", must conform to the pattern #{pattern}.")
+      end
+
       if !@filter_types.nil? && @filter_types.length < 1
         invalid_properties.push('invalid value for "filter_types", number of items must be greater than or equal to 1.')
       end
@@ -150,6 +168,8 @@ module Svix
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
+      return false if !@feature_flag.nil? && @feature_flag.to_s.length > 256
+      return false if !@feature_flag.nil? && @feature_flag !~ Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
       return false if !@filter_types.nil? && @filter_types.length < 1
       return false if @logo.nil?
       return false if @transformation.nil?
@@ -158,6 +178,21 @@ module Svix
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] feature_flag Value to be assigned
+    def feature_flag=(feature_flag)
+      if !feature_flag.nil? && feature_flag.to_s.length > 256
+        fail ArgumentError, 'invalid value for "feature_flag", the character length must be smaller than or equal to 256.'
+      end
+
+      pattern = Regexp.new(/^[a-zA-Z0-9\-_.]+$/)
+      if !feature_flag.nil? && feature_flag !~ pattern
+        fail ArgumentError, "invalid value for \"feature_flag\", must conform to the pattern #{pattern}."
+      end
+
+      @feature_flag = feature_flag
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] filter_types Value to be assigned
     def filter_types=(filter_types)
@@ -192,6 +227,7 @@ module Svix
       return true if self.equal?(o)
       self.class == o.class &&
           description == o.description &&
+          feature_flag == o.feature_flag &&
           filter_types == o.filter_types &&
           instructions == o.instructions &&
           instructions_link == o.instructions_link &&
@@ -209,7 +245,7 @@ module Svix
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [description, filter_types, instructions, instructions_link, logo, name, transformation].hash
+      [description, feature_flag, filter_types, instructions, instructions_link, logo, name, transformation].hash
     end
 
     # Builds the object from hash

data/lib/svix/models/transformation_http_method.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0

data/lib/svix/models/transformation_simulate_in.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0

data/lib/svix/models/transformation_simulate_out.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0

data/lib/svix/models/transformation_template_kind.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0

data/lib/svix/models/validation_error.rb

@@ -1,9 +1,9 @@
 =begin
 #Svix API
 
-#Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys).  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
+#No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
-The version of the OpenAPI document: 1.7.0
+The version of the OpenAPI document: 1.1.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -16,7 +16,7 @@ require 'time'
 module Svix
   # Validation errors have their own schema to provide context for invalid requests eg. mismatched types and out of bounds values. There may be any number of these per 422 UNPROCESSABLE ENTITY error.
   class ValidationError
-    # The location as a [`Vec`] of [`String`]s -- often in the form `[\"body\", \"field_name\"]`, `[\"query\", \"field_name\"]`, etc. They may, however, be arbitarily deep.
+    # The location as a [`Vec`] of [`String`]s -- often in the form `[\"body\", \"field_name\"]`, `[\"query\", \"field_name\"]`, etc. They may, however, be arbitrarily deep.
     attr_accessor :loc
 
     # The message accompanying the validation error item.

data/lib/svix/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Svix
-  VERSION = "1.10.0"
+  VERSION = "1.12.0"
 end

data/lib/svix.rb

@@ -38,6 +38,9 @@ require "svix/models/endpoint_update"
 require "svix/models/endpoint_updated_event_data"
 require "svix/models/endpoint_updated_event"
 require "svix/models/event_example_in"
+require "svix/models/event_type_import_open_api_in"
+require "svix/models/event_type_import_open_api_out"
+require "svix/models/event_type_import_open_api_out_data"
 require "svix/models/event_type_in"
 require "svix/models/event_type_out"
 require "svix/models/event_type_update"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: svix
 version: !ruby/object:Gem::Version
-  version: 1.10.0
+  version: 1.12.0
 platform: ruby
 authors:
 - Svix
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-08-30 00:00:00.000000000 Z
+date: 2023-09-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus
@@ -158,6 +158,9 @@ files:
 - lib/svix/models/environment_settings_out.rb
 - lib/svix/models/event_example_in.rb
 - lib/svix/models/event_type_example_out.rb
+- lib/svix/models/event_type_import_open_api_in.rb
+- lib/svix/models/event_type_import_open_api_out.rb
+- lib/svix/models/event_type_import_open_api_out_data.rb
 - lib/svix/models/event_type_in.rb
 - lib/svix/models/event_type_out.rb
 - lib/svix/models/event_type_patch.rb
@@ -198,6 +201,7 @@ files:
 - lib/svix/models/message_endpoint_out.rb
 - lib/svix/models/message_in.rb
 - lib/svix/models/message_out.rb
+- lib/svix/models/message_raw_payload_out.rb
 - lib/svix/models/message_status.rb
 - lib/svix/models/one_time_token_in.rb
 - lib/svix/models/one_time_token_out.rb