@zyphr-dev/node-sdk 0.1.38 → 0.1.39

package/dist/index.cjs

@@ -1228,6 +1228,10 @@ __export(index_exports, {
   SignInWithGameCenterRequestFromJSONTyped: () => SignInWithGameCenterRequestFromJSONTyped,
   SignInWithGameCenterRequestToJSON: () => SignInWithGameCenterRequestToJSON,
   SignInWithGameCenterRequestToJSONTyped: () => SignInWithGameCenterRequestToJSONTyped,
+  SignInWithGooglePlayGamesRequestFromJSON: () => SignInWithGooglePlayGamesRequestFromJSON,
+  SignInWithGooglePlayGamesRequestFromJSONTyped: () => SignInWithGooglePlayGamesRequestFromJSONTyped,
+  SignInWithGooglePlayGamesRequestToJSON: () => SignInWithGooglePlayGamesRequestToJSON,
+  SignInWithGooglePlayGamesRequestToJSONTyped: () => SignInWithGooglePlayGamesRequestToJSONTyped,
   SlackApi: () => SlackApi,
   SlackMessageFromJSON: () => SlackMessageFromJSON,
   SlackMessageFromJSONTyped: () => SlackMessageFromJSONTyped,
@@ -2172,6 +2176,7 @@ __export(index_exports, {
   instanceOfSetPreferencesRequestPreferencesInner: () => instanceOfSetPreferencesRequestPreferencesInner,
   instanceOfSignInAnonymouslyRequest: () => instanceOfSignInAnonymouslyRequest,
   instanceOfSignInWithGameCenterRequest: () => instanceOfSignInWithGameCenterRequest,
+  instanceOfSignInWithGooglePlayGamesRequest: () => instanceOfSignInWithGooglePlayGamesRequest,
   instanceOfSlackMessage: () => instanceOfSlackMessage,
   instanceOfSlackMessageListResponse: () => instanceOfSlackMessageListResponse,
   instanceOfSlackMessageListResponseMeta: () => instanceOfSlackMessageListResponseMeta,
@@ -12623,6 +12628,34 @@ function SignInWithGameCenterRequestToJSONTyped(value, ignoreDiscriminator = fal
   };
 }
 
+// src/src/models/SignInWithGooglePlayGamesRequest.ts
+function instanceOfSignInWithGooglePlayGamesRequest(value) {
+  if (!("serverAuthCode" in value) || value["serverAuthCode"] === void 0) return false;
+  return true;
+}
+function SignInWithGooglePlayGamesRequestFromJSON(json) {
+  return SignInWithGooglePlayGamesRequestFromJSONTyped(json, false);
+}
+function SignInWithGooglePlayGamesRequestFromJSONTyped(json, ignoreDiscriminator) {
+  if (json == null) {
+    return json;
+  }
+  return {
+    "serverAuthCode": json["serverAuthCode"]
+  };
+}
+function SignInWithGooglePlayGamesRequestToJSON(json) {
+  return SignInWithGooglePlayGamesRequestToJSONTyped(json, false);
+}
+function SignInWithGooglePlayGamesRequestToJSONTyped(value, ignoreDiscriminator = false) {
+  if (value == null) {
+    return value;
+  }
+  return {
+    "serverAuthCode": value["serverAuthCode"]
+  };
+}
+
 // src/src/models/SlackMessage.ts
 function instanceOfSlackMessage(value) {
   return true;
@@ -19265,6 +19298,40 @@ var AuthRegistrationApi = class extends BaseAPI {
     const response = await this.signInWithGameCenterRaw({ signInWithGameCenterRequest }, initOverrides);
     return await response.value();
   }
+  /**
+   * Exchange a Google Play Games Services (GPGS) **server auth code** for a Zyphr end-user session. Unlike Game Center (which submits an Apple-signed assertion), GPGS is verified by Google: Zyphr exchanges the single-use server auth code at Google\'s OAuth2 token endpoint, then calls the Play Games REST API (`players/me`) server-side to obtain the trusted, tamper-proof `playerId`. The user is provisioned-or-looked-up on that server-fetched `playerId` and tokens are minted.  ## Producing the server auth code (Integration)  The server auth code is obtained **on-device by the Android app** — there is no server-side way to mint it. The app calls `GamesSignInClient.requestServerSideAccess(serverClientId, …)` using the Google Cloud **web (server) client id** configured for the game, which returns a single-use auth code string. Submit that string here as `serverAuthCode`.  The **backend-relayed** shape is the common one: the app forwards the auth code to the customer\'s own backend, which relays it to this endpoint; the app never holds Zyphr keys.  ## Security  The `playerId` is derived **only** from Zyphr\'s own server-side call to Google after the token exchange — a client-supplied player id is never accepted or trusted. On any verification failure the response is a single opaque `401` `invalid_auth_code`; the specific control that failed is never disclosed. 
+   * Sign in with Google Play Games Services
+   */
+  async signInWithGooglePlayGamesRaw(requestParameters, initOverrides) {
+    if (requestParameters["signInWithGooglePlayGamesRequest"] == null) {
+      throw new RequiredError(
+        "signInWithGooglePlayGamesRequest",
+        'Required parameter "signInWithGooglePlayGamesRequest" was null or undefined when calling signInWithGooglePlayGames().'
+      );
+    }
+    const queryParameters = {};
+    const headerParameters = {};
+    headerParameters["Content-Type"] = "application/json";
+    if (this.configuration && this.configuration.apiKey) {
+      headerParameters["X-Application-Key"] = await this.configuration.apiKey("X-Application-Key");
+    }
+    const response = await this.request({
+      path: `/auth/google-play-games`,
+      method: "POST",
+      headers: headerParameters,
+      query: queryParameters,
+      body: SignInWithGooglePlayGamesRequestToJSON(requestParameters["signInWithGooglePlayGamesRequest"])
+    }, initOverrides);
+    return new JSONApiResponse(response, (jsonValue) => AuthResultResponseFromJSON(jsonValue));
+  }
+  /**
+   * Exchange a Google Play Games Services (GPGS) **server auth code** for a Zyphr end-user session. Unlike Game Center (which submits an Apple-signed assertion), GPGS is verified by Google: Zyphr exchanges the single-use server auth code at Google\'s OAuth2 token endpoint, then calls the Play Games REST API (`players/me`) server-side to obtain the trusted, tamper-proof `playerId`. The user is provisioned-or-looked-up on that server-fetched `playerId` and tokens are minted.  ## Producing the server auth code (Integration)  The server auth code is obtained **on-device by the Android app** — there is no server-side way to mint it. The app calls `GamesSignInClient.requestServerSideAccess(serverClientId, …)` using the Google Cloud **web (server) client id** configured for the game, which returns a single-use auth code string. Submit that string here as `serverAuthCode`.  The **backend-relayed** shape is the common one: the app forwards the auth code to the customer\'s own backend, which relays it to this endpoint; the app never holds Zyphr keys.  ## Security  The `playerId` is derived **only** from Zyphr\'s own server-side call to Google after the token exchange — a client-supplied player id is never accepted or trusted. On any verification failure the response is a single opaque `401` `invalid_auth_code`; the specific control that failed is never disclosed. 
+   * Sign in with Google Play Games Services
+   */
+  async signInWithGooglePlayGames(signInWithGooglePlayGamesRequest, initOverrides) {
+    const response = await this.signInWithGooglePlayGamesRaw({ signInWithGooglePlayGamesRequest }, initOverrides);
+    return await response.value();
+  }
 };
 
 // src/src/apis/AuthSessionsApi.ts
@@ -27415,6 +27482,10 @@ var SDK_VERSION = "0.1.0";
   SignInWithGameCenterRequestFromJSONTyped,
   SignInWithGameCenterRequestToJSON,
   SignInWithGameCenterRequestToJSONTyped,
+  SignInWithGooglePlayGamesRequestFromJSON,
+  SignInWithGooglePlayGamesRequestFromJSONTyped,
+  SignInWithGooglePlayGamesRequestToJSON,
+  SignInWithGooglePlayGamesRequestToJSONTyped,
   SlackApi,
   SlackMessageFromJSON,
   SlackMessageFromJSONTyped,
@@ -28359,6 +28430,7 @@ var SDK_VERSION = "0.1.0";
   instanceOfSetPreferencesRequestPreferencesInner,
   instanceOfSignInAnonymouslyRequest,
   instanceOfSignInWithGameCenterRequest,
+  instanceOfSignInWithGooglePlayGamesRequest,
   instanceOfSlackMessage,
   instanceOfSlackMessageListResponse,
   instanceOfSlackMessageListResponseMeta,