@getanyapi/sdk 0.42.0 → 0.43.0

package/dist/index.d.cts

@@ -41685,6 +41685,10 @@ interface TwitterFollowersInput {
      * Range: minimum 1.
      */
     preferLatencyUnderMs?: number;
+    /**
+     * Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `bio`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
+     */
+    requireFields?: ("bio" | "followers" | "following" | "location" | "nextCursor" | "verified")[];
     /**
      * The X (Twitter) username to fetch followers for, without the @ prefix (e.g. elonmusk).
      */
@@ -41698,7 +41702,7 @@ interface TwitterFollowersItem {
     /**
      * The account's profile bio/description.
      */
-    bio: string;
+    bio?: string;
     /**
      * How many followers this account has.
      */
@@ -41706,7 +41710,7 @@ interface TwitterFollowersItem {
     /**
      * How many accounts this account follows.
      */
-    following: number;
+    following?: number;
     /**
      * The account's self-reported location (may be empty).
      */
@@ -41757,6 +41761,10 @@ interface TwitterFollowingInput {
      * Range: minimum 1.
      */
     preferLatencyUnderMs?: number;
+    /**
+     * Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `location`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
+     */
+    requireFields?: ("bio" | "followers" | "following" | "location" | "nextCursor")[];
     /**
      * The X (Twitter) username to fetch the following list for, without the @ prefix (e.g. elonmusk).
      */
@@ -41791,10 +41799,6 @@ interface TwitterFollowingItem {
      * The account's @ handle, without the @ prefix. Populated whenever the provider has data for the entity.
      */
     username: string;
-    /**
-     * Whether the account is verified.
-     */
-    verified?: boolean;
     [extra: string]: unknown;
 }
 /**
@@ -42747,7 +42751,7 @@ declare class TwitterNamespace {
      *
      * Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more.
      *
-     * Price: $0.00075 per request.
+     * Price: $0.0005 per request.
      *
      * @example
      * const res = await client.twitter.followers({ username: "nasa", limit: 200 });

package/dist/index.d.ts

@@ -41685,6 +41685,10 @@ interface TwitterFollowersInput {
      * Range: minimum 1.
      */
     preferLatencyUnderMs?: number;
+    /**
+     * Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `bio`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
+     */
+    requireFields?: ("bio" | "followers" | "following" | "location" | "nextCursor" | "verified")[];
     /**
      * The X (Twitter) username to fetch followers for, without the @ prefix (e.g. elonmusk).
      */
@@ -41698,7 +41702,7 @@ interface TwitterFollowersItem {
     /**
      * The account's profile bio/description.
      */
-    bio: string;
+    bio?: string;
     /**
      * How many followers this account has.
      */
@@ -41706,7 +41710,7 @@ interface TwitterFollowersItem {
     /**
      * How many accounts this account follows.
      */
-    following: number;
+    following?: number;
     /**
      * The account's self-reported location (may be empty).
      */
@@ -41757,6 +41761,10 @@ interface TwitterFollowingInput {
      * Range: minimum 1.
      */
     preferLatencyUnderMs?: number;
+    /**
+     * Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `location`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
+     */
+    requireFields?: ("bio" | "followers" | "following" | "location" | "nextCursor")[];
     /**
      * The X (Twitter) username to fetch the following list for, without the @ prefix (e.g. elonmusk).
      */
@@ -41791,10 +41799,6 @@ interface TwitterFollowingItem {
      * The account's @ handle, without the @ prefix. Populated whenever the provider has data for the entity.
      */
     username: string;
-    /**
-     * Whether the account is verified.
-     */
-    verified?: boolean;
     [extra: string]: unknown;
 }
 /**
@@ -42747,7 +42751,7 @@ declare class TwitterNamespace {
      *
      * Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more.
      *
-     * Price: $0.00075 per request.
+     * Price: $0.0005 per request.
      *
      * @example
      * const res = await client.twitter.followers({ username: "nasa", limit: 200 });

package/dist/index.js

@@ -6693,7 +6693,7 @@ var TwitterNamespace = class {
    *
    * Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more.
    *
-   * Price: $0.00075 per request.
+   * Price: $0.0005 per request.
    *
    * @example
    * const res = await client.twitter.followers({ username: "nasa", limit: 200 });