@roxyapi/sdk 1.2.48 → 1.2.49

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "1.2.48";
1
+ export declare const VERSION = "1.2.49";
2
2
  //# sourceMappingURL=version.d.ts.map
@@ -1032,6 +1032,7 @@ const { data } = await roxy.humanDesign.generateBodygraph({
1032
1032
  timezone: 'America/New_York',
1033
1033
  latitude: 0,
1034
1034
  longitude: 0,
1035
+ nodeType: 'true',
1035
1036
  },
1036
1037
  });
1037
1038
 
@@ -1044,6 +1045,7 @@ const { data } = await roxy.humanDesign.calculateConnection({
1044
1045
  timezone: 'America/New_York',
1045
1046
  latitude: 0,
1046
1047
  longitude: 0,
1048
+ nodeType: 'true',
1047
1049
  },
1048
1050
  personB: {
1049
1051
  date: '1990-07-15',
@@ -1051,6 +1053,7 @@ const { data } = await roxy.humanDesign.calculateConnection({
1051
1053
  timezone: 'America/New_York',
1052
1054
  latitude: 0,
1053
1055
  longitude: 0,
1056
+ nodeType: 'true',
1054
1057
  },
1055
1058
  },
1056
1059
  });
@@ -1065,6 +1068,7 @@ const { data } = await roxy.humanDesign.calculatePenta({
1065
1068
  timezone: 'America/New_York',
1066
1069
  latitude: 0,
1067
1070
  longitude: 0,
1071
+ nodeType: 'true',
1068
1072
  },
1069
1073
  ],
1070
1074
  },
@@ -1079,6 +1083,7 @@ const { data } = await roxy.humanDesign.generateTransit({
1079
1083
  timezone: 'America/New_York',
1080
1084
  latitude: 0,
1081
1085
  longitude: 0,
1086
+ nodeType: 'true',
1082
1087
  },
1083
1088
  date: '2026-05-23',
1084
1089
  time: '12:00:00',
@@ -1093,6 +1098,7 @@ const { data } = await roxy.humanDesign.calculateType({
1093
1098
  timezone: 'America/New_York',
1094
1099
  latitude: 0,
1095
1100
  longitude: 0,
1101
+ nodeType: 'true',
1096
1102
  },
1097
1103
  });
1098
1104
 
@@ -1104,6 +1110,7 @@ const { data } = await roxy.humanDesign.calculateGates({
1104
1110
  timezone: 'America/New_York',
1105
1111
  latitude: 0,
1106
1112
  longitude: 0,
1113
+ nodeType: 'true',
1107
1114
  },
1108
1115
  });
1109
1116
 
@@ -1118,6 +1125,7 @@ const { data } = await roxy.humanDesign.calculateChannels({
1118
1125
  timezone: 'America/New_York',
1119
1126
  latitude: 0,
1120
1127
  longitude: 0,
1128
+ nodeType: 'true',
1121
1129
  },
1122
1130
  });
1123
1131
 
@@ -1129,6 +1137,7 @@ const { data } = await roxy.humanDesign.calculateCenters({
1129
1137
  timezone: 'America/New_York',
1130
1138
  latitude: 0,
1131
1139
  longitude: 0,
1140
+ nodeType: 'true',
1132
1141
  },
1133
1142
  });
1134
1143
 
@@ -1143,6 +1152,7 @@ const { data } = await roxy.humanDesign.calculateProfile({
1143
1152
  timezone: 'America/New_York',
1144
1153
  latitude: 0,
1145
1154
  longitude: 0,
1155
+ nodeType: 'true',
1146
1156
  },
1147
1157
  });
1148
1158
 
@@ -1154,6 +1164,7 @@ const { data } = await roxy.humanDesign.calculateVariables({
1154
1164
  timezone: 'America/New_York',
1155
1165
  latitude: 0,
1156
1166
  longitude: 0,
1167
+ nodeType: 'true',
1157
1168
  },
1158
1169
  });
1159
1170
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@roxyapi/sdk",
3
- "version": "1.2.48",
3
+ "version": "1.2.49",
4
4
  "description": "TypeScript SDK for Roxy — the multi-domain spiritual intelligence API",
5
5
  "type": "module",
6
6
  "exports": {
@@ -73,7 +73,7 @@
73
73
  "@types/node": "^26.1.1",
74
74
  "lefthook": "^2.1.10",
75
75
  "tsup": "^8.5.1",
76
- "typescript": "^6.0.2",
76
+ "typescript": "^6.0.3",
77
77
  "vitest": "^4.1.10"
78
78
  }
79
79
  }
package/src/types.gen.ts CHANGED
@@ -803,7 +803,7 @@ export type TransitsResponse = {
803
803
  */
804
804
  isApplying: boolean;
805
805
  /**
806
- * Aspect strength percentage (0-100). Based on orb tightness — 100 is exact.
806
+ * Aspect strength percentage (0-100) based on orb tightness, where 100 is exact.
807
807
  */
808
808
  strength: number;
809
809
  /**
@@ -26279,6 +26279,10 @@ export type PostHumanDesignBodygraphData = {
26279
26279
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
26280
26280
  */
26281
26281
  longitude?: number;
26282
+ /**
26283
+ * 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.
26284
+ */
26285
+ nodeType?: 'mean' | 'true';
26282
26286
  };
26283
26287
  path?: never;
26284
26288
  query?: {
@@ -26658,6 +26662,10 @@ export type PostHumanDesignConnectionData = {
26658
26662
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
26659
26663
  */
26660
26664
  longitude?: number;
26665
+ /**
26666
+ * 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.
26667
+ */
26668
+ nodeType?: 'mean' | 'true';
26661
26669
  };
26662
26670
  /**
26663
26671
  * Birth moment of the second person in the connection.
@@ -26683,6 +26691,10 @@ export type PostHumanDesignConnectionData = {
26683
26691
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
26684
26692
  */
26685
26693
  longitude?: number;
26694
+ /**
26695
+ * 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.
26696
+ */
26697
+ nodeType?: 'mean' | 'true';
26686
26698
  };
26687
26699
  };
26688
26700
  path?: never;
@@ -26922,6 +26934,10 @@ export type PostHumanDesignPentaData = {
26922
26934
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
26923
26935
  */
26924
26936
  longitude?: number;
26937
+ /**
26938
+ * 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.
26939
+ */
26940
+ nodeType?: 'mean' | 'true';
26925
26941
  }>;
26926
26942
  };
26927
26943
  path?: never;
@@ -27161,6 +27177,10 @@ export type PostHumanDesignTransitData = {
27161
27177
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
27162
27178
  */
27163
27179
  longitude?: number;
27180
+ /**
27181
+ * 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.
27182
+ */
27183
+ nodeType?: 'mean' | 'true';
27164
27184
  };
27165
27185
  /**
27166
27186
  * Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.
@@ -27421,6 +27441,10 @@ export type PostHumanDesignTypeData = {
27421
27441
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
27422
27442
  */
27423
27443
  longitude?: number;
27444
+ /**
27445
+ * 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.
27446
+ */
27447
+ nodeType?: 'mean' | 'true';
27424
27448
  };
27425
27449
  path?: never;
27426
27450
  query?: {
@@ -27608,6 +27632,10 @@ export type PostHumanDesignGatesData = {
27608
27632
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
27609
27633
  */
27610
27634
  longitude?: number;
27635
+ /**
27636
+ * 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.
27637
+ */
27638
+ nodeType?: 'mean' | 'true';
27611
27639
  };
27612
27640
  path?: never;
27613
27641
  query?: {
@@ -28041,6 +28069,10 @@ export type PostHumanDesignChannelsData = {
28041
28069
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
28042
28070
  */
28043
28071
  longitude?: number;
28072
+ /**
28073
+ * 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.
28074
+ */
28075
+ nodeType?: 'mean' | 'true';
28044
28076
  };
28045
28077
  path?: never;
28046
28078
  query?: {
@@ -28229,6 +28261,10 @@ export type PostHumanDesignCentersData = {
28229
28261
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
28230
28262
  */
28231
28263
  longitude?: number;
28264
+ /**
28265
+ * 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.
28266
+ */
28267
+ nodeType?: 'mean' | 'true';
28232
28268
  };
28233
28269
  path?: never;
28234
28270
  query?: {
@@ -28576,6 +28612,10 @@ export type PostHumanDesignProfileData = {
28576
28612
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
28577
28613
  */
28578
28614
  longitude?: number;
28615
+ /**
28616
+ * 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.
28617
+ */
28618
+ nodeType?: 'mean' | 'true';
28579
28619
  };
28580
28620
  path?: never;
28581
28621
  query?: {
@@ -28743,6 +28783,10 @@ export type PostHumanDesignVariablesData = {
28743
28783
  * Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.
28744
28784
  */
28745
28785
  longitude?: number;
28786
+ /**
28787
+ * 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.
28788
+ */
28789
+ nodeType?: 'mean' | 'true';
28746
28790
  };
28747
28791
  path?: never;
28748
28792
  query?: {
package/src/version.ts CHANGED
@@ -1 +1 @@
1
- export const VERSION = '1.2.48';
1
+ export const VERSION = '1.2.49';