release: v0.1.15

Author: github-actions[bot]

specs/openapi.json

@@ -21,6 +21,8 @@ public partial class BodygraphPostRequestBody : IAdditionalDataHolder, IParsable
         public double? Latitude { get; set; }
         /// <summary>Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.</summary>
         public double? Longitude { get; set; }
+        /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+        public global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody_nodeType? NodeType { get; set; }
         /// <summary>Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.</summary>
         public Time? Time { get; set; }
         /// <summary>IANA name (e.g. &quot;America/New_York&quot;, &quot;Europe/London&quot;, &quot;UTC&quot;), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. &quot;-05:00&quot;, &quot;+01:00&quot;). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.</summary>
@@ -39,6 +41,7 @@ public BodygraphPostRequestBody()
             AdditionalData = new Dictionary<string, object>();
             Latitude = 0;
             Longitude = 0;
+            NodeType = global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody_nodeType.True;
         }
         /// <summary>
         /// Creates a new instance of the appropriate class based on discriminator value
@@ -61,6 +64,7 @@ public virtual IDictionary<string, Action<IParseNode>> GetFieldDeserializers()
                 { "date", n => { Date = n.GetDateValue(); } },
                 { "latitude", n => { Latitude = n.GetDoubleValue(); } },
                 { "longitude", n => { Longitude = n.GetDoubleValue(); } },
+                { "nodeType", n => { NodeType = n.GetEnumValue<global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody_nodeType>(); } },
                 { "time", n => { Time = n.GetTimeValue(); } },
                 { "timezone", n => { Timezone = n.GetObjectValue<global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody.BodygraphPostRequestBody_timezone>(global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody.BodygraphPostRequestBody_timezone.CreateFromDiscriminatorValue); } },
             };
@@ -75,6 +79,7 @@ public virtual void Serialize(ISerializationWriter writer)
             writer.WriteDateValue("date", Date);
             writer.WriteDoubleValue("latitude", Latitude);
             writer.WriteDoubleValue("longitude", Longitude);
+            writer.WriteEnumValue<global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody_nodeType>("nodeType", NodeType);
             writer.WriteTimeValue("time", Time);
             writer.WriteObjectValue<global::RoxyApi.HumanDesign.Bodygraph.BodygraphPostRequestBody.BodygraphPostRequestBody_timezone>("timezone", Timezone);
             writer.WriteAdditionalData(AdditionalData);

src/Generated/HumanDesign/Bodygraph/BodygraphPostRequestBody.cs

@@ -0,0 +1,19 @@
+// <auto-generated/>
+using System.Runtime.Serialization;
+using System;
+namespace RoxyApi.HumanDesign.Bodygraph
+{
+    /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+    [global::System.CodeDom.Compiler.GeneratedCode("Kiota", "1.0.0")]
+    public enum BodygraphPostRequestBody_nodeType
+    {
+        [EnumMember(Value = "mean")]
+        #pragma warning disable CS1591
+        Mean,
+        #pragma warning restore CS1591
+        [EnumMember(Value = "true")]
+        #pragma warning disable CS1591
+        True,
+        #pragma warning restore CS1591
+    }
+}

src/Generated/HumanDesign/Bodygraph/BodygraphPostRequestBody_nodeType.cs

@@ -21,6 +21,8 @@ public partial class CentersPostRequestBody : IAdditionalDataHolder, IParsable
         public double? Latitude { get; set; }
         /// <summary>Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.</summary>
         public double? Longitude { get; set; }
+        /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+        public global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody_nodeType? NodeType { get; set; }
         /// <summary>Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.</summary>
         public Time? Time { get; set; }
         /// <summary>IANA name (e.g. &quot;America/New_York&quot;, &quot;Europe/London&quot;, &quot;UTC&quot;), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. &quot;-05:00&quot;, &quot;+01:00&quot;). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.</summary>
@@ -39,6 +41,7 @@ public CentersPostRequestBody()
             AdditionalData = new Dictionary<string, object>();
             Latitude = 0;
             Longitude = 0;
+            NodeType = global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody_nodeType.True;
         }
         /// <summary>
         /// Creates a new instance of the appropriate class based on discriminator value
@@ -61,6 +64,7 @@ public virtual IDictionary<string, Action<IParseNode>> GetFieldDeserializers()
                 { "date", n => { Date = n.GetDateValue(); } },
                 { "latitude", n => { Latitude = n.GetDoubleValue(); } },
                 { "longitude", n => { Longitude = n.GetDoubleValue(); } },
+                { "nodeType", n => { NodeType = n.GetEnumValue<global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody_nodeType>(); } },
                 { "time", n => { Time = n.GetTimeValue(); } },
                 { "timezone", n => { Timezone = n.GetObjectValue<global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody.CentersPostRequestBody_timezone>(global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody.CentersPostRequestBody_timezone.CreateFromDiscriminatorValue); } },
             };
@@ -75,6 +79,7 @@ public virtual void Serialize(ISerializationWriter writer)
             writer.WriteDateValue("date", Date);
             writer.WriteDoubleValue("latitude", Latitude);
             writer.WriteDoubleValue("longitude", Longitude);
+            writer.WriteEnumValue<global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody_nodeType>("nodeType", NodeType);
             writer.WriteTimeValue("time", Time);
             writer.WriteObjectValue<global::RoxyApi.HumanDesign.Centers.CentersPostRequestBody.CentersPostRequestBody_timezone>("timezone", Timezone);
             writer.WriteAdditionalData(AdditionalData);

src/Generated/HumanDesign/Centers/CentersPostRequestBody.cs

@@ -0,0 +1,19 @@
+// <auto-generated/>
+using System.Runtime.Serialization;
+using System;
+namespace RoxyApi.HumanDesign.Centers
+{
+    /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+    [global::System.CodeDom.Compiler.GeneratedCode("Kiota", "1.0.0")]
+    public enum CentersPostRequestBody_nodeType
+    {
+        [EnumMember(Value = "mean")]
+        #pragma warning disable CS1591
+        Mean,
+        #pragma warning restore CS1591
+        [EnumMember(Value = "true")]
+        #pragma warning disable CS1591
+        True,
+        #pragma warning restore CS1591
+    }
+}

src/Generated/HumanDesign/Centers/CentersPostRequestBody_nodeType.cs

@@ -21,6 +21,8 @@ public partial class ChannelsPostRequestBody : IAdditionalDataHolder, IParsable
         public double? Latitude { get; set; }
         /// <summary>Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.</summary>
         public double? Longitude { get; set; }
+        /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+        public global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody_nodeType? NodeType { get; set; }
         /// <summary>Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.</summary>
         public Time? Time { get; set; }
         /// <summary>IANA name (e.g. &quot;America/New_York&quot;, &quot;Europe/London&quot;, &quot;UTC&quot;), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. &quot;-05:00&quot;, &quot;+01:00&quot;). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.</summary>
@@ -39,6 +41,7 @@ public ChannelsPostRequestBody()
             AdditionalData = new Dictionary<string, object>();
             Latitude = 0;
             Longitude = 0;
+            NodeType = global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody_nodeType.True;
         }
         /// <summary>
         /// Creates a new instance of the appropriate class based on discriminator value
@@ -61,6 +64,7 @@ public virtual IDictionary<string, Action<IParseNode>> GetFieldDeserializers()
                 { "date", n => { Date = n.GetDateValue(); } },
                 { "latitude", n => { Latitude = n.GetDoubleValue(); } },
                 { "longitude", n => { Longitude = n.GetDoubleValue(); } },
+                { "nodeType", n => { NodeType = n.GetEnumValue<global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody_nodeType>(); } },
                 { "time", n => { Time = n.GetTimeValue(); } },
                 { "timezone", n => { Timezone = n.GetObjectValue<global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody.ChannelsPostRequestBody_timezone>(global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody.ChannelsPostRequestBody_timezone.CreateFromDiscriminatorValue); } },
             };
@@ -75,6 +79,7 @@ public virtual void Serialize(ISerializationWriter writer)
             writer.WriteDateValue("date", Date);
             writer.WriteDoubleValue("latitude", Latitude);
             writer.WriteDoubleValue("longitude", Longitude);
+            writer.WriteEnumValue<global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody_nodeType>("nodeType", NodeType);
             writer.WriteTimeValue("time", Time);
             writer.WriteObjectValue<global::RoxyApi.HumanDesign.Channels.ChannelsPostRequestBody.ChannelsPostRequestBody_timezone>("timezone", Timezone);
             writer.WriteAdditionalData(AdditionalData);

src/Generated/HumanDesign/Channels/ChannelsPostRequestBody.cs

@@ -0,0 +1,19 @@
+// <auto-generated/>
+using System.Runtime.Serialization;
+using System;
+namespace RoxyApi.HumanDesign.Channels
+{
+    /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+    [global::System.CodeDom.Compiler.GeneratedCode("Kiota", "1.0.0")]
+    public enum ChannelsPostRequestBody_nodeType
+    {
+        [EnumMember(Value = "mean")]
+        #pragma warning disable CS1591
+        Mean,
+        #pragma warning restore CS1591
+        [EnumMember(Value = "true")]
+        #pragma warning disable CS1591
+        True,
+        #pragma warning restore CS1591
+    }
+}

src/Generated/HumanDesign/Channels/ChannelsPostRequestBody_nodeType.cs

@@ -22,6 +22,8 @@ public partial class ConnectionPostRequestBody_personA : IAdditionalDataHolder,
         public double? Latitude { get; set; }
         /// <summary>Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.</summary>
         public double? Longitude { get; set; }
+        /// <summary>Lunar node convention for the North and South Node activations. Leave unset (or &quot;true&quot;) for the standard Human Design chart: &quot;true&quot; is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass &quot;mean&quot; to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass &quot;mean&quot; to match it.</summary>
+        public global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA_nodeType? NodeType { get; set; }
         /// <summary>Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.</summary>
         public Time? Time { get; set; }
         /// <summary>IANA name (e.g. &quot;America/New_York&quot;, &quot;Europe/London&quot;, &quot;UTC&quot;), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. &quot;-05:00&quot;, &quot;+01:00&quot;). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.</summary>
@@ -40,6 +42,7 @@ public ConnectionPostRequestBody_personA()
             AdditionalData = new Dictionary<string, object>();
             Latitude = 0;
             Longitude = 0;
+            NodeType = global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA_nodeType.True;
         }
         /// <summary>
         /// Creates a new instance of the appropriate class based on discriminator value
@@ -62,6 +65,7 @@ public virtual IDictionary<string, Action<IParseNode>> GetFieldDeserializers()
                 { "date", n => { Date = n.GetDateValue(); } },
                 { "latitude", n => { Latitude = n.GetDoubleValue(); } },
                 { "longitude", n => { Longitude = n.GetDoubleValue(); } },
+                { "nodeType", n => { NodeType = n.GetEnumValue<global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA_nodeType>(); } },
                 { "time", n => { Time = n.GetTimeValue(); } },
                 { "timezone", n => { Timezone = n.GetObjectValue<global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA.ConnectionPostRequestBody_personA_timezone>(global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA.ConnectionPostRequestBody_personA_timezone.CreateFromDiscriminatorValue); } },
             };
@@ -76,6 +80,7 @@ public virtual void Serialize(ISerializationWriter writer)
             writer.WriteDateValue("date", Date);
             writer.WriteDoubleValue("latitude", Latitude);
             writer.WriteDoubleValue("longitude", Longitude);
+            writer.WriteEnumValue<global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA_nodeType>("nodeType", NodeType);
             writer.WriteTimeValue("time", Time);
             writer.WriteObjectValue<global::RoxyApi.HumanDesign.Connection.ConnectionPostRequestBody_personA.ConnectionPostRequestBody_personA_timezone>("timezone", Timezone);
             writer.WriteAdditionalData(AdditionalData);