@roxyapi/sdk 1.2.60 → 1.2.61

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "1.2.60";
+export declare const VERSION = "1.2.61";
 //# sourceMappingURL=version.d.ts.map

package/docs/llms-full.txt

@@ -50,6 +50,7 @@ const { data } = await roxy.astrology.generateNatalChart({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     houseSystem: 'placidus',
   },
 });
@@ -59,6 +60,7 @@ const { data } = await roxy.astrology.getPlanetaryPositions({
   body: {
     date: '2025-12-18',
     time: '12:00:00',
+    nodeType: 'true',
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
@@ -92,6 +94,7 @@ const { data } = await roxy.astrology.calculateSynastry({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
       name: 'Alex',
     },
     person2: {
@@ -100,6 +103,7 @@ const { data } = await roxy.astrology.calculateSynastry({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
       name: 'Alex',
     },
     houseSystem: 'placidus',
@@ -143,7 +147,12 @@ const { data } = await roxy.astrology.detectAspectPatterns({
 
 // Calculate planetary transits - Current transits with natal chart comparison
 const { data } = await roxy.astrology.calculateTransits({
-  body: { date: '2025-12-19', time: '12:00:00', timezone: 0 },
+  body: {
+    date: '2025-12-19',
+    time: '12:00:00',
+    timezone: 0,
+    nodeType: 'true',
+  },
 });
 
 // Transit Aspects - Detailed transit-to-natal aspect analysis with interpretations
@@ -155,6 +164,7 @@ const { data } = await roxy.astrology.calculateTransitAspects({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
     },
     transitDate: '2026-02-03',
     transitTime: '12:00:00',
@@ -200,6 +210,7 @@ const { data } = await roxy.astrology.generateCompositeChart({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
     },
     person2: {
       date: '1990-07-15',
@@ -207,6 +218,7 @@ const { data } = await roxy.astrology.generateCompositeChart({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
     },
     houseSystem: 'placidus',
   },
@@ -221,6 +233,7 @@ const { data } = await roxy.astrology.calculateCompatibility({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
     },
     person2: {
       date: '1990-07-15',
@@ -228,6 +241,7 @@ const { data } = await roxy.astrology.calculateCompatibility({
       latitude: 40.7128,
       longitude: -74.006,
       timezone: -5,
+      nodeType: 'true',
     },
   },
 });
@@ -273,6 +287,7 @@ const { data } = await roxy.astrology.generateAstrocartography({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
   },
 });
 
@@ -311,6 +326,7 @@ const { data } = await roxy.astrology.generateFixedStars({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
   },
 });
 
@@ -322,6 +338,7 @@ const { data } = await roxy.astrology.calculateArabicLots({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     houseSystem: 'placidus',
   },
 });
@@ -334,6 +351,7 @@ const { data } = await roxy.astrology.generateAsteroids({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     houseSystem: 'placidus',
   },
 });
@@ -346,6 +364,7 @@ const { data } = await roxy.astrology.generateLilith({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     houseSystem: 'placidus',
   },
 });
@@ -358,6 +377,7 @@ const { data } = await roxy.astrology.generateProgressions({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     targetDate: '2025-07-15',
   },
 });
@@ -370,6 +390,7 @@ const { data } = await roxy.astrology.generateSolarArc({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     targetDate: '2025-07-15',
   },
 });
@@ -382,6 +403,7 @@ const { data } = await roxy.astrology.generateProfections({
     latitude: 40.7128,
     longitude: -74.006,
     timezone: -5,
+    nodeType: 'true',
     targetDate: '2025-08-04',
     houseSystem: 'placidus',
   },
@@ -1671,7 +1693,7 @@ const { data } = await roxy.angelNumbers.getDailyAngelNumber({ body: { seed: 'us
 
 ## Location and Timezone — `roxy.location`
 
-Location and timezone API with city search and geocoding across 23,000+ cities in 240+ countries, returning latitude,...
+Location and timezone API with city search and geocoding across 235,000+ cities in 240+ countries, returning latitude...
 
 ```typescript
 // Search cities worldwide - Geocoding autocomplete with coordinates and timezone

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@roxyapi/sdk",
-	"version": "1.2.60",
+	"version": "1.2.61",
 	"description": "TypeScript SDK for Roxy — the multi-domain spiritual intelligence API",
 	"type": "module",
 	"exports": {

package/src/sdk.gen.ts

@@ -1173,7 +1173,7 @@ export class VedicAstrology extends HeyApiClient {
     /**
      * Transit Analysis - Compare current planets to natal chart (Gochar)
      *
-     * Analyze planetary transits (Gochar) over natal chart positions. Returns transiting planets with their natal house positions, aspects to natal planets, and highlights key transits from slow-moving planets (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions.
+     * Analyze planetary transits (Gochar) over natal chart positions. Each transiting graha comes back with TWO whole-sign house numbers, because the two readings answer different questions: houseFromMoon is counted from the natal Moon sign (Janma Rashi), which is the reference classical Gochara uses, and natalHouse is counted from the Lagna. Also returns graha drishti onto the natal grahas (7th for every graha, plus Mars 4th and 8th, Jupiter 5th and 9th, Saturn 3rd and 10th), degree-based angular aspects with orbs, the Gochara Kaksha verdict, and highlighted transits from the slow-moving grahas (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions, Chandra Lagna gochara, graha drishti.
      */
     public calculateTransit<ThrowOnError extends boolean = false>(options?: Options<PostVedicAstrologyTransitData, ThrowOnError>): RequestResult<PostVedicAstrologyTransitResponses, PostVedicAstrologyTransitErrors, ThrowOnError> {
         return (options?.client ?? this.client).post<PostVedicAstrologyTransitResponses, PostVedicAstrologyTransitErrors, ThrowOnError>({
@@ -2779,7 +2779,7 @@ export class Location extends HeyApiClient {
     /**
      * Search cities worldwide - Geocoding autocomplete with coordinates and timezone
      *
-     * City autocomplete and geocoding search across 23,000+ locations in 240+ countries, including deep coverage of Indian tier-2 and tier-3 cities. Returns geographic coordinates (latitude, longitude), IANA timezone, and DST-aware UTC offset for each match. Built for birth chart location pickers, horoscope apps, event scheduling, and any feature requiring place-to-coordinates resolution. Partial name matching with intelligent ranking: exact prefix matches first, then sorted by population for relevance. Common alternate names like Bombay, Calcutta, Madras, and Banaras transparently resolve to their canonical entries.
+     * Turn a place name into coordinates, an IANA timezone and a DST-aware UTC offset, across 235,000+ cities and towns in 240+ countries. Coverage reaches rural towns of a few hundred people and every administrative seat, so a birthplace outside a major metro resolves as reliably as a capital. Matching is case-insensitive, accent-insensitive and partial, so ber matches Berlin, Bern and Bergen, native scripts are transliterated, and historic names resolve to the current place, so bombay returns Mumbai and peking returns Beijing. Results are ordered by match quality first and population second, so an exactly named small town is never buried under a larger city that merely shares its opening letters. Built for birth chart location pickers, horoscope apps, event scheduling, and any feature that needs place-to-coordinates resolution.
      */
     public searchCities<ThrowOnError extends boolean = false>(options: Options<GetLocationSearchData, ThrowOnError>): RequestResult<GetLocationSearchResponses, GetLocationSearchErrors, ThrowOnError> {
         return (options.client ?? this.client).get<GetLocationSearchResponses, GetLocationSearchErrors, ThrowOnError>({