@zyphr-dev/node-sdk 0.1.36 → 0.1.38

package/src/src/apis/AuthOAuthApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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
@@ -21,6 +21,7 @@ import type {
   OAuthCallbackResponse,
   OAuthConnectionInfoResponse,
   OAuthConnectionsResponse,
+  OAuthProviderName,
   OAuthProvidersResponse,
   OAuthTokensRefreshResponse,
   OAuthTokensResponse,
@@ -40,6 +41,8 @@ import {
     OAuthConnectionInfoResponseToJSON,
     OAuthConnectionsResponseFromJSON,
     OAuthConnectionsResponseToJSON,
+    OAuthProviderNameFromJSON,
+    OAuthProviderNameToJSON,
     OAuthProvidersResponseFromJSON,
     OAuthProvidersResponseToJSON,
     OAuthTokensRefreshResponseFromJSON,
@@ -53,30 +56,30 @@ import {
 } from '../models/index';
 
 export interface AuthOAuthApiDisconnectOAuthProviderRequest {
-    provider: string;
+    provider: OAuthProviderName;
 }
 
 export interface AuthOAuthApiGetOAuthAuthorizationUrlRequest {
-    provider: string;
+    provider: OAuthProviderName;
     redirectUri: string;
 }
 
 export interface AuthOAuthApiGetOAuthConnectionInfoRequest {
-    provider: string;
+    provider: OAuthProviderName;
 }
 
 export interface AuthOAuthApiGetOAuthTokensRequest {
-    provider: string;
+    provider: OAuthProviderName;
     userId: string;
 }
 
 export interface AuthOAuthApiHandleOAuthCallbackRequest {
-    provider: string;
+    provider: OAuthProviderName;
     oAuthCallbackRequest: OAuthCallbackRequest;
 }
 
 export interface AuthOAuthApiRefreshOAuthTokensOperationRequest {
-    provider: string;
+    provider: OAuthProviderName;
     refreshOAuthTokensRequest: RefreshOAuthTokensRequest;
 }
 
@@ -90,7 +93,7 @@ export interface AuthOAuthApiInterface {
     /**
      * Disconnect an OAuth provider from the current user.
      * @summary Disconnect OAuth provider
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof AuthOAuthApiInterface
@@ -101,12 +104,12 @@ export interface AuthOAuthApiInterface {
      * Disconnect an OAuth provider from the current user.
      * Disconnect OAuth provider
      */
-    disconnectOAuthProvider(provider: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SuccessResult>;
+    disconnectOAuthProvider(provider: OAuthProviderName, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SuccessResult>;
 
     /**
      * Generate an OAuth authorization URL for the specified provider.
      * @summary Get OAuth authorization URL
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {string} redirectUri Redirect URI after authorization
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -118,12 +121,12 @@ export interface AuthOAuthApiInterface {
      * Generate an OAuth authorization URL for the specified provider.
      * Get OAuth authorization URL
      */
-    getOAuthAuthorizationUrl(provider: string, redirectUri: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthAuthorizationUrlResponse>;
+    getOAuthAuthorizationUrl(provider: OAuthProviderName, redirectUri: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthAuthorizationUrlResponse>;
 
     /**
      * Get OAuth connection info for a specific provider (without tokens). Safe for public key authentication.
      * @summary Get OAuth connection info
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof AuthOAuthApiInterface
@@ -134,12 +137,12 @@ export interface AuthOAuthApiInterface {
      * Get OAuth connection info for a specific provider (without tokens). Safe for public key authentication.
      * Get OAuth connection info
      */
-    getOAuthConnectionInfo(provider: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthConnectionInfoResponse>;
+    getOAuthConnectionInfo(provider: OAuthProviderName, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthConnectionInfoResponse>;
 
     /**
      * Get OAuth provider tokens for an end user. Requires secret key authentication (server-side only). This allows developers to access downstream APIs on behalf of their users. 
      * @summary Get OAuth provider tokens
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {string} userId End user ID
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -151,12 +154,12 @@ export interface AuthOAuthApiInterface {
      * Get OAuth provider tokens for an end user. Requires secret key authentication (server-side only). This allows developers to access downstream APIs on behalf of their users. 
      * Get OAuth provider tokens
      */
-    getOAuthTokens(provider: string, userId: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensResponse>;
+    getOAuthTokens(provider: OAuthProviderName, userId: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensResponse>;
 
     /**
      * Handle the OAuth callback by exchanging the authorization code for tokens and authenticating the user.
      * @summary Handle OAuth callback
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {OAuthCallbackRequest} oAuthCallbackRequest 
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -168,7 +171,7 @@ export interface AuthOAuthApiInterface {
      * Handle the OAuth callback by exchanging the authorization code for tokens and authenticating the user.
      * Handle OAuth callback
      */
-    handleOAuthCallback(provider: string, oAuthCallbackRequest: OAuthCallbackRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthCallbackResponse>;
+    handleOAuthCallback(provider: OAuthProviderName, oAuthCallbackRequest: OAuthCallbackRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthCallbackResponse>;
 
     /**
      * Get OAuth connections for the current user with metadata.
@@ -203,7 +206,7 @@ export interface AuthOAuthApiInterface {
     /**
      * Refresh OAuth provider tokens for an end user. Requires secret key authentication (server-side only). Only supported for providers that support token refresh (e.g., Google, Microsoft). 
      * @summary Refresh OAuth provider tokens
-     * @param {string} provider OAuth provider name
+     * @param {OAuthProviderName} provider OAuth provider name
      * @param {RefreshOAuthTokensRequest} refreshOAuthTokensRequest 
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -215,7 +218,7 @@ export interface AuthOAuthApiInterface {
      * Refresh OAuth provider tokens for an end user. Requires secret key authentication (server-side only). Only supported for providers that support token refresh (e.g., Google, Microsoft). 
      * Refresh OAuth provider tokens
      */
-    refreshOAuthTokens(provider: string, refreshOAuthTokensRequest: RefreshOAuthTokensRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensRefreshResponse>;
+    refreshOAuthTokens(provider: OAuthProviderName, refreshOAuthTokensRequest: RefreshOAuthTokensRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensRefreshResponse>;
 
 }
 
@@ -266,7 +269,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Disconnect an OAuth provider from the current user.
      * Disconnect OAuth provider
      */
-    async disconnectOAuthProvider(provider: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SuccessResult> {
+    async disconnectOAuthProvider(provider: OAuthProviderName, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SuccessResult> {
         const response = await this.disconnectOAuthProviderRaw({ provider: provider }, initOverrides);
         return await response.value();
     }
@@ -316,7 +319,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Generate an OAuth authorization URL for the specified provider.
      * Get OAuth authorization URL
      */
-    async getOAuthAuthorizationUrl(provider: string, redirectUri: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthAuthorizationUrlResponse> {
+    async getOAuthAuthorizationUrl(provider: OAuthProviderName, redirectUri: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthAuthorizationUrlResponse> {
         const response = await this.getOAuthAuthorizationUrlRaw({ provider: provider, redirectUri: redirectUri }, initOverrides);
         return await response.value();
     }
@@ -363,7 +366,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Get OAuth connection info for a specific provider (without tokens). Safe for public key authentication.
      * Get OAuth connection info
      */
-    async getOAuthConnectionInfo(provider: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthConnectionInfoResponse> {
+    async getOAuthConnectionInfo(provider: OAuthProviderName, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthConnectionInfoResponse> {
         const response = await this.getOAuthConnectionInfoRaw({ provider: provider }, initOverrides);
         return await response.value();
     }
@@ -417,7 +420,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Get OAuth provider tokens for an end user. Requires secret key authentication (server-side only). This allows developers to access downstream APIs on behalf of their users. 
      * Get OAuth provider tokens
      */
-    async getOAuthTokens(provider: string, userId: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensResponse> {
+    async getOAuthTokens(provider: OAuthProviderName, userId: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensResponse> {
         const response = await this.getOAuthTokensRaw({ provider: provider, userId: userId }, initOverrides);
         return await response.value();
     }
@@ -462,7 +465,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Handle the OAuth callback by exchanging the authorization code for tokens and authenticating the user.
      * Handle OAuth callback
      */
-    async handleOAuthCallback(provider: string, oAuthCallbackRequest: OAuthCallbackRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthCallbackResponse> {
+    async handleOAuthCallback(provider: OAuthProviderName, oAuthCallbackRequest: OAuthCallbackRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthCallbackResponse> {
         const response = await this.handleOAuthCallbackRaw({ provider: provider, oAuthCallbackRequest: oAuthCallbackRequest }, initOverrides);
         return await response.value();
     }
@@ -587,7 +590,7 @@ export class AuthOAuthApi extends runtime.BaseAPI implements AuthOAuthApiInterfa
      * Refresh OAuth provider tokens for an end user. Requires secret key authentication (server-side only). Only supported for providers that support token refresh (e.g., Google, Microsoft). 
      * Refresh OAuth provider tokens
      */
-    async refreshOAuthTokens(provider: string, refreshOAuthTokensRequest: RefreshOAuthTokensRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensRefreshResponse> {
+    async refreshOAuthTokens(provider: OAuthProviderName, refreshOAuthTokensRequest: RefreshOAuthTokensRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<OAuthTokensRefreshResponse> {
         const response = await this.refreshOAuthTokensRaw({ provider: provider, refreshOAuthTokensRequest: refreshOAuthTokensRequest }, initOverrides);
         return await response.value();
     }

package/src/src/apis/AuthOrganizationsApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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

package/src/src/apis/AuthPasswordResetApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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

package/src/src/apis/AuthPhoneApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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

package/src/src/apis/AuthRegistrationApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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
@@ -20,6 +20,7 @@ import type {
   ConvertAnonymousUserRequest,
   RegisterRequest,
   SignInAnonymouslyRequest,
+  SignInWithGameCenterRequest,
 } from '../models/index';
 import {
     ApiErrorFromJSON,
@@ -32,6 +33,8 @@ import {
     RegisterRequestToJSON,
     SignInAnonymouslyRequestFromJSON,
     SignInAnonymouslyRequestToJSON,
+    SignInWithGameCenterRequestFromJSON,
+    SignInWithGameCenterRequestToJSON,
 } from '../models/index';
 
 export interface AuthRegistrationApiConvertAnonymousUserOperationRequest {
@@ -46,6 +49,10 @@ export interface AuthRegistrationApiSignInAnonymouslyOperationRequest {
     signInAnonymouslyRequest: SignInAnonymouslyRequest;
 }
 
+export interface AuthRegistrationApiSignInWithGameCenterOperationRequest {
+    signInWithGameCenterRequest: SignInWithGameCenterRequest;
+}
+
 /**
  * AuthRegistrationApi - interface
  * 
@@ -86,7 +93,7 @@ export interface AuthRegistrationApiInterface {
     registerEndUser(registerRequest: RegisterRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse>;
 
     /**
-     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert. 
+     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert.  Pass an optional `organization_id` to create the anonymous user directly in an organization; the returned access token then carries `org_id` (and `orgs`), matching the org-scoped register/login flow. 
      * @summary Sign in anonymously
      * @param {SignInAnonymouslyRequest} signInAnonymouslyRequest 
      * @param {*} [options] Override http request option.
@@ -96,11 +103,27 @@ export interface AuthRegistrationApiInterface {
     signInAnonymouslyRaw(requestParameters: AuthRegistrationApiSignInAnonymouslyOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>>;
 
     /**
-     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert. 
+     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert.  Pass an optional `organization_id` to create the anonymous user directly in an organization; the returned access token then carries `org_id` (and `orgs`), matching the org-scoped register/login flow. 
      * Sign in anonymously
      */
     signInAnonymously(signInAnonymouslyRequest: SignInAnonymouslyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse>;
 
+    /**
+     * Exchange an Apple Game Center identity-verification assertion for a Zyphr end-user session. Zyphr independently re-verifies the assertion server-side (Apple certificate chain, RSA-SHA256 signature, timestamp freshness, single-use replay guard, and bundle-id binding) before provisioning-or-looking-up the user and minting tokens. The user is keyed on the modern scoped `playerId` (gamePlayerID).  ## Producing the assertion (Integration)  The assertion is produced **on-device by the iOS app** — there is no server-side way to mint it. The app calls GameKit\'s `GKLocalPlayer.fetchItems(forIdentityVerificationSignature:)`, which returns `publicKeyURL`, `signature`, `salt`, and `timestamp`; combine those with the local player\'s `gamePlayerID` and the app\'s bundle identifier and submit them here.  Two integration shapes are supported:   - **client-direct** — the iOS app holds the Zyphr application public     key and calls this endpoint itself.   - **backend-relayed** — the app forwards the fetched assertion fields     to the customer\'s own backend, which relays them to this endpoint;     the app never holds Zyphr keys. (This is the common shape for games.)  On any verification failure the response is a single opaque `401` `invalid_assertion` — the specific control that failed is never disclosed. 
+     * @summary Sign in with Apple Game Center
+     * @param {SignInWithGameCenterRequest} signInWithGameCenterRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AuthRegistrationApiInterface
+     */
+    signInWithGameCenterRaw(requestParameters: AuthRegistrationApiSignInWithGameCenterOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>>;
+
+    /**
+     * Exchange an Apple Game Center identity-verification assertion for a Zyphr end-user session. Zyphr independently re-verifies the assertion server-side (Apple certificate chain, RSA-SHA256 signature, timestamp freshness, single-use replay guard, and bundle-id binding) before provisioning-or-looking-up the user and minting tokens. The user is keyed on the modern scoped `playerId` (gamePlayerID).  ## Producing the assertion (Integration)  The assertion is produced **on-device by the iOS app** — there is no server-side way to mint it. The app calls GameKit\'s `GKLocalPlayer.fetchItems(forIdentityVerificationSignature:)`, which returns `publicKeyURL`, `signature`, `salt`, and `timestamp`; combine those with the local player\'s `gamePlayerID` and the app\'s bundle identifier and submit them here.  Two integration shapes are supported:   - **client-direct** — the iOS app holds the Zyphr application public     key and calls this endpoint itself.   - **backend-relayed** — the app forwards the fetched assertion fields     to the customer\'s own backend, which relays them to this endpoint;     the app never holds Zyphr keys. (This is the common shape for games.)  On any verification failure the response is a single opaque `401` `invalid_assertion` — the specific control that failed is never disclosed. 
+     * Sign in with Apple Game Center
+     */
+    signInWithGameCenter(signInWithGameCenterRequest: SignInWithGameCenterRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse>;
+
 }
 
 /**
@@ -193,7 +216,7 @@ export class AuthRegistrationApi extends runtime.BaseAPI implements AuthRegistra
     }
 
     /**
-     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert. 
+     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert.  Pass an optional `organization_id` to create the anonymous user directly in an organization; the returned access token then carries `org_id` (and `orgs`), matching the org-scoped register/login flow. 
      * Sign in anonymously
      */
     async signInAnonymouslyRaw(requestParameters: AuthRegistrationApiSignInAnonymouslyOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>> {
@@ -226,7 +249,7 @@ export class AuthRegistrationApi extends runtime.BaseAPI implements AuthRegistra
     }
 
     /**
-     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert. 
+     * Issue an end-user identity to a device without email, password, OAuth, or any other credential. Idempotent per (application, environment, device_id): repeated calls with the same device_id return the same user but a fresh token pair. Prior sessions for the user remain valid until natural expiry.  Anonymous users do not count toward MAU quota until their first authenticated request after sign-in (excluding /v1/auth/refresh).  Convert an anonymous user to a full account via POST /v1/auth/users/convert.  Pass an optional `organization_id` to create the anonymous user directly in an organization; the returned access token then carries `org_id` (and `orgs`), matching the org-scoped register/login flow. 
      * Sign in anonymously
      */
     async signInAnonymously(signInAnonymouslyRequest: SignInAnonymouslyRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse> {
@@ -234,4 +257,46 @@ export class AuthRegistrationApi extends runtime.BaseAPI implements AuthRegistra
         return await response.value();
     }
 
+    /**
+     * Exchange an Apple Game Center identity-verification assertion for a Zyphr end-user session. Zyphr independently re-verifies the assertion server-side (Apple certificate chain, RSA-SHA256 signature, timestamp freshness, single-use replay guard, and bundle-id binding) before provisioning-or-looking-up the user and minting tokens. The user is keyed on the modern scoped `playerId` (gamePlayerID).  ## Producing the assertion (Integration)  The assertion is produced **on-device by the iOS app** — there is no server-side way to mint it. The app calls GameKit\'s `GKLocalPlayer.fetchItems(forIdentityVerificationSignature:)`, which returns `publicKeyURL`, `signature`, `salt`, and `timestamp`; combine those with the local player\'s `gamePlayerID` and the app\'s bundle identifier and submit them here.  Two integration shapes are supported:   - **client-direct** — the iOS app holds the Zyphr application public     key and calls this endpoint itself.   - **backend-relayed** — the app forwards the fetched assertion fields     to the customer\'s own backend, which relays them to this endpoint;     the app never holds Zyphr keys. (This is the common shape for games.)  On any verification failure the response is a single opaque `401` `invalid_assertion` — the specific control that failed is never disclosed. 
+     * Sign in with Apple Game Center
+     */
+    async signInWithGameCenterRaw(requestParameters: AuthRegistrationApiSignInWithGameCenterOperationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AuthResultResponse>> {
+        if (requestParameters['signInWithGameCenterRequest'] == null) {
+            throw new runtime.RequiredError(
+                'signInWithGameCenterRequest',
+                'Required parameter "signInWithGameCenterRequest" was null or undefined when calling signInWithGameCenter().'
+            );
+        }
+
+        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/game-center`,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+            body: SignInWithGameCenterRequestToJSON(requestParameters['signInWithGameCenterRequest']),
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => AuthResultResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Exchange an Apple Game Center identity-verification assertion for a Zyphr end-user session. Zyphr independently re-verifies the assertion server-side (Apple certificate chain, RSA-SHA256 signature, timestamp freshness, single-use replay guard, and bundle-id binding) before provisioning-or-looking-up the user and minting tokens. The user is keyed on the modern scoped `playerId` (gamePlayerID).  ## Producing the assertion (Integration)  The assertion is produced **on-device by the iOS app** — there is no server-side way to mint it. The app calls GameKit\'s `GKLocalPlayer.fetchItems(forIdentityVerificationSignature:)`, which returns `publicKeyURL`, `signature`, `salt`, and `timestamp`; combine those with the local player\'s `gamePlayerID` and the app\'s bundle identifier and submit them here.  Two integration shapes are supported:   - **client-direct** — the iOS app holds the Zyphr application public     key and calls this endpoint itself.   - **backend-relayed** — the app forwards the fetched assertion fields     to the customer\'s own backend, which relays them to this endpoint;     the app never holds Zyphr keys. (This is the common shape for games.)  On any verification failure the response is a single opaque `401` `invalid_assertion` — the specific control that failed is never disclosed. 
+     * Sign in with Apple Game Center
+     */
+    async signInWithGameCenter(signInWithGameCenterRequest: SignInWithGameCenterRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AuthResultResponse> {
+        const response = await this.signInWithGameCenterRaw({ signInWithGameCenterRequest: signInWithGameCenterRequest }, initOverrides);
+        return await response.value();
+    }
+
 }

package/src/src/apis/AuthSessionsApi.ts

@@ -2,7 +2,7 @@
 /* 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  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+ * 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