@roxyapi/sdk 1.2.47 → 1.2.49

package/dist/factory.cjs

@@ -3353,7 +3353,7 @@ var Roxy = class _Roxy extends HeyApiClient {
 };
 
 // src/version.ts
-var VERSION = "1.2.47";
+var VERSION = "1.2.49";
 
 // src/factory.ts
 function createRoxy(auth) {

package/dist/factory.js

@@ -2532,7 +2532,7 @@ var Roxy = class _Roxy extends HeyApiClient {
 };
 
 // src/version.ts
-var VERSION = "1.2.47";
+var VERSION = "1.2.49";
 
 // src/factory.ts
 function createRoxy(auth) {

package/dist/types.gen.d.ts

@@ -793,7 +793,7 @@ export type TransitsResponse = {
          */
         isApplying: boolean;
         /**
-         * Aspect strength percentage (0-100). Based on orb tightness — 100 is exact.
+         * Aspect strength percentage (0-100) based on orb tightness, where 100 is exact.
          */
         strength: number;
         /**
@@ -3907,6 +3907,10 @@ export type KpChartResponse = {
          * Zodiac sign of the Ascendant.
          */
         sign: string;
+        /**
+         * Ruling planet of the Ascendant sign (the rashi lord). In KP this is the weakest of the four lords, ranked below the star lord and sub lord, but it still sets the broad temperament of the Lagna.
+         */
+        signLord: string;
         /**
          * Nakshatra (star) of the Ascendant.
          */
@@ -4074,6 +4078,10 @@ export type KpChartResponse = {
              * KP sub-sub lord (SSL) of Rahu.
              */
             subSubLord: string;
+            /**
+             * KP number (1-249) locating Rahu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
+             */
+            kpNumber: number;
         };
         /**
          * Ketu (South Lunar Node), shadow planet, spiritual karmic indicator.
@@ -4107,6 +4115,10 @@ export type KpChartResponse = {
              * KP sub-sub lord (SSL) of Ketu.
              */
             subSubLord: string;
+            /**
+             * KP number (1-249) locating Ketu in the 249-division sub-lord scheme. Each of the 249 divisions maps to a unique sign, star lord and sub lord triple, so one integer pins the position precisely enough for KP event timing.
+             */
+            kpNumber: number;
         };
     };
     /**
@@ -17085,7 +17097,7 @@ export type PostVedicAstrologyAspectsResponses = {
      */
     200: {
         /**
-         * UTC datetime used for aspect calculation (ISO 8601).
+         * Chart time the aspects were calculated for, echoed back as the local wall clock of the request (ISO 8601, no offset). This is the `date` and `time` you sent, NOT a UTC instant: hold them fixed and vary `timezone` and every longitude moves while this field does not. Combine it with the `timezone` you sent to recover the absolute moment.
          */
         datetime: string;
         /**
@@ -25653,6 +25665,10 @@ export type PostHumanDesignBodygraphData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -26027,6 +26043,10 @@ export type PostHumanDesignConnectionData = {
              * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
              */
             longitude?: number;
+            /**
+             * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+             */
+            nodeType?: 'mean' | 'true';
         };
         /**
          * Birth moment of the second person in the connection.
@@ -26052,6 +26072,10 @@ export type PostHumanDesignConnectionData = {
              * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
              */
             longitude?: number;
+            /**
+             * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+             */
+            nodeType?: 'mean' | 'true';
         };
     };
     path?: never;
@@ -26286,6 +26310,10 @@ export type PostHumanDesignPentaData = {
              * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
              */
             longitude?: number;
+            /**
+             * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+             */
+            nodeType?: 'mean' | 'true';
         }>;
     };
     path?: never;
@@ -26520,6 +26548,10 @@ export type PostHumanDesignTransitData = {
              * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
              */
             longitude?: number;
+            /**
+             * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+             */
+            nodeType?: 'mean' | 'true';
         };
         /**
          * Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.
@@ -26775,6 +26807,10 @@ export type PostHumanDesignTypeData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -26957,6 +26993,10 @@ export type PostHumanDesignGatesData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -27380,6 +27420,10 @@ export type PostHumanDesignChannelsData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -27563,6 +27607,10 @@ export type PostHumanDesignCentersData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -27900,6 +27948,10 @@ export type PostHumanDesignProfileData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {
@@ -28062,6 +28114,10 @@ export type PostHumanDesignVariablesData = {
          * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
          */
         longitude?: number;
+        /**
+         * Lunar node convention for the North and South Node activations. Leave unset (or "true") for the standard Human Design chart: "true" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass "mean" 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 "mean" to match it.
+         */
+        nodeType?: 'mean' | 'true';
     };
     path?: never;
     query?: {