@zyphr-dev/node-sdk 0.1.38 → 0.1.39

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zyphr-dev/node-sdk",
-  "version": "0.1.38",
+  "version": "0.1.39",
   "description": "Official Zyphr SDK for Node.js, React, and React Native",
   "type": "module",
   "main": "./dist/index.cjs",

package/src/.openapi-generator/FILES

@@ -321,6 +321,7 @@ src/models/SetPreferencesRequest.ts
 src/models/SetPreferencesRequestPreferencesInner.ts
 src/models/SignInAnonymouslyRequest.ts
 src/models/SignInWithGameCenterRequest.ts
+src/models/SignInWithGooglePlayGamesRequest.ts
 src/models/SlackMessage.ts
 src/models/SlackMessageListResponse.ts
 src/models/SlackMessageListResponseMeta.ts

package/src/src/apis/AuthRegistrationApi.ts

@@ -21,6 +21,7 @@ import type {
   RegisterRequest,
   SignInAnonymouslyRequest,
   SignInWithGameCenterRequest,
+  SignInWithGooglePlayGamesRequest,
 } from '../models/index';
 import {
     ApiErrorFromJSON,
@@ -35,6 +36,8 @@ import {
     SignInAnonymouslyRequestToJSON,
     SignInWithGameCenterRequestFromJSON,
     SignInWithGameCenterRequestToJSON,
+    SignInWithGooglePlayGamesRequestFromJSON,
+    SignInWithGooglePlayGamesRequestToJSON,
 } from '../models/index';
 
 export interface AuthRegistrationApiConvertAnonymousUserOperationRequest {
@@ -53,6 +56,10 @@ export interface AuthRegistrationApiSignInWithGameCenterOperationRequest {
     signInWithGameCenterRequest: SignInWithGameCenterRequest;
 }
 
+export interface AuthRegistrationApiSignInWithGooglePlayGamesOperationRequest {
+    signInWithGooglePlayGamesRequest: SignInWithGooglePlayGamesRequest;
+}
+
 /**
  * AuthRegistrationApi - interface
  * 
@@ -124,6 +131,22 @@ export interface AuthRegistrationApiInterface {
      */
     signInWithGameCenter(signInWithGameCenterRequest: SignInWithGameCenterRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse>;
 
+    /**
+     * 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. 
+     * @summary Sign in with Google Play Games Services
+     * @param {SignInWithGooglePlayGamesRequest} signInWithGooglePlayGamesRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AuthRegistrationApiInterface
+     */
+    signInWithGooglePlayGamesRaw(requestParameters: AuthRegistrationApiSignInWithGooglePlayGamesOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>>;
+
+    /**
+     * 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
+     */
+    signInWithGooglePlayGames(signInWithGooglePlayGamesRequest: SignInWithGooglePlayGamesRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse>;
+
 }
 
 /**
@@ -299,4 +322,46 @@ export class AuthRegistrationApi extends runtime.BaseAPI implements AuthRegistra
         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: AuthRegistrationApiSignInWithGooglePlayGamesOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>> {
+        if (requestParameters['signInWithGooglePlayGamesRequest'] == null) {
+            throw new runtime.RequiredError(
+                'signInWithGooglePlayGamesRequest',
+                'Required parameter "signInWithGooglePlayGamesRequest" was null or undefined when calling signInWithGooglePlayGames().'
+            );
+        }
+
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        headerParameters['Content-Type'] = 'application/json';
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["X-Application-Key"] = await this.configuration.apiKey("X-Application-Key"); // ApplicationPublicKey authentication
+        }
+
+        const response = await this.request({
+            path: `/auth/google-play-games`,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+            body: SignInWithGooglePlayGamesRequestToJSON(requestParameters['signInWithGooglePlayGamesRequest']),
+        }, initOverrides);
+
+        return new runtime.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: SignInWithGooglePlayGamesRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse> {
+        const response = await this.signInWithGooglePlayGamesRaw({ signInWithGooglePlayGamesRequest: signInWithGooglePlayGamesRequest }, initOverrides);
+        return await response.value();
+    }
+
 }

package/src/src/models/SignInWithGooglePlayGamesRequest.ts

@@ -0,0 +1,66 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Zyphr API
+ * Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Account Sending Status  Every authenticated response carries the account\'s current sending state so you can surface it in your own tooling without a separate call:  - `X-Account-Sending-Status`: `active`, `throttled`, or `frozen` - `X-Account-Sending-Status-Reason`: human-readable reason (present only when the status is `throttled` or `frozen`)  This header is informational and non-blocking on non-send endpoints (reads, billing, and deliverability stay available). Send-capable endpoints additionally enforce the state: a frozen account receives `403 account_frozen` and a throttled account receives `429 account_throttled`, both with the reason in the error message.  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ *
+ * The version of the OpenAPI document: 1.0.0
+ * Contact: support@zyphr.dev
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+
+import { mapValues } from '../runtime';
+/**
+ * 
+ * @export
+ * @interface SignInWithGooglePlayGamesRequest
+ */
+export interface SignInWithGooglePlayGamesRequest {
+    /**
+     * The single-use server auth code from GamesSignInClient.requestServerSideAccess (obtained with the game's web/server client id). Zyphr exchanges it server-side; a client-supplied player id is neither accepted nor trusted.
+     * @type {string}
+     * @memberof SignInWithGooglePlayGamesRequest
+     */
+    serverAuthCode: string;
+}
+
+/**
+ * Check if a given object implements the SignInWithGooglePlayGamesRequest interface.
+ */
+export function instanceOfSignInWithGooglePlayGamesRequest(value: object): value is SignInWithGooglePlayGamesRequest {
+    if (!('serverAuthCode' in value) || value['serverAuthCode'] === undefined) return false;
+    return true;
+}
+
+export function SignInWithGooglePlayGamesRequestFromJSON(json: any): SignInWithGooglePlayGamesRequest {
+    return SignInWithGooglePlayGamesRequestFromJSONTyped(json, false);
+}
+
+export function SignInWithGooglePlayGamesRequestFromJSONTyped(json: any, ignoreDiscriminator: boolean): SignInWithGooglePlayGamesRequest {
+    if (json == null) {
+        return json;
+    }
+    return {
+        
+        'serverAuthCode': json['serverAuthCode'],
+    };
+}
+
+export function SignInWithGooglePlayGamesRequestToJSON(json: any): SignInWithGooglePlayGamesRequest {
+    return SignInWithGooglePlayGamesRequestToJSONTyped(json, false);
+}
+
+export function SignInWithGooglePlayGamesRequestToJSONTyped(value?: SignInWithGooglePlayGamesRequest | null, ignoreDiscriminator: boolean = false): any {
+    if (value == null) {
+        return value;
+    }
+
+    return {
+        
+        'serverAuthCode': value['serverAuthCode'],
+    };
+}
+

package/src/src/models/index.ts

@@ -281,6 +281,7 @@ export * from './SetPreferencesRequest';
 export * from './SetPreferencesRequestPreferencesInner';
 export * from './SignInAnonymouslyRequest';
 export * from './SignInWithGameCenterRequest';
+export * from './SignInWithGooglePlayGamesRequest';
 export * from './SlackMessage';
 export * from './SlackMessageListResponse';
 export * from './SlackMessageListResponseMeta';