@roxyapi/sdk 1.2.46 → 1.2.48

package/dist/factory.cjs

@@ -3353,7 +3353,7 @@ var Roxy = class _Roxy extends HeyApiClient {
 };
 
 // src/version.ts
-var VERSION = "1.2.46";
+var VERSION = "1.2.48";
 
 // 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.46";
+var VERSION = "1.2.48";
 
 // src/factory.ts
 function createRoxy(auth) {

package/dist/types.gen.d.ts

@@ -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;
         };
     };
     /**
@@ -5383,6 +5395,20 @@ export type DrawnCard = {
      */
     imageUrl: string;
 };
+export type ChangingLine = {
+    /**
+     * Line position (1-6, bottom to top). In I-Ching, each hexagram has six lines (yao) read from bottom upward.
+     */
+    position: number;
+    /**
+     * The oracle statement for this line. It applies when this specific line comes up changing (old yin or old yang) in a casting, and it speaks in the concrete imagery of the tradition.
+     */
+    text: string;
+    /**
+     * What the line statement asks of the querent, read from its position in the hexagram (1 is the hidden beginning, 3 is the exposed threshold, 5 is the ruling line, 6 is past the peak) and from whether the line is yin or yang. This is the meaning behind the image, so a consuming agent does not have to invent one.
+     */
+    meaning?: string;
+};
 export type BasicHexagram = {
     /**
      * Hexagram number in King Wen sequence (1-64).
@@ -5482,16 +5508,6 @@ export type Interpretation = {
      */
     advice: string;
 };
-export type ChangingLine = {
-    /**
-     * Line position (1-6, bottom to top). In I-Ching, each hexagram has six lines (yao) read from bottom upward.
-     */
-    position: number;
-    /**
-     * Changing line interpretation text. Applies only when this specific line is a changing line (old yin or old yang) in a casting.
-     */
-    text: string;
-};
 export type BasicTrigram = {
     /**
      * Trigram number (1-8)
@@ -5524,7 +5540,7 @@ export type BasicTrigram = {
 };
 export type Trigram = {
     /**
-     * Trigram number (1-8) in the traditional I-Ching ordering.
+     * Stable identifier for the trigram, 1 to 8. This is our lookup key, not a canonical sequence: the tradition has several orderings (King Wen, Fu Xi, Earlier and Later Heaven) and they disagree, so do not read ranking or precedence into it.
      */
     number: number;
     /**
@@ -17081,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;
         /**
@@ -31397,6 +31413,10 @@ export type PostIchingDailyCastResponses = {
          * Positions of changing lines (1-6, bottom to top). These lines transform yin to yang or vice versa.
          */
         changingLinePositions: Array<number>;
+        /**
+         * The oracle statement and meaning of each line that came up CHANGING, and only those. The changing lines are what the cast is actually about, so this saves a second call to read them and stops a consuming agent from having to invent them.
+         */
+        changingLines?: Array<ChangingLine>;
         /**
          * Hexagram after transformation (if changing lines present)
          */