@zyphr-dev/node-sdk 0.1.36 → 0.1.38

package/src/src/models/WorkflowStepExecutionStatus.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/models/index.ts

@@ -127,6 +127,7 @@ export * from './InboundEmailResponse';
 export * from './InboxListMeta';
 export * from './InboxListResponse';
 export * from './InboxNotificationResponse';
+export * from './InviteEndUserRequest';
 export * from './ListWaaSApplications200Response';
 export * from './ListWaaSEndpointDeliveries200Response';
 export * from './ListWaaSEndpoints200Response';
@@ -171,6 +172,7 @@ export * from './OAuthConnectionsResponse';
 export * from './OAuthConnectionsResponseData';
 export * from './OAuthProvider';
 export * from './OAuthProviderInfo';
+export * from './OAuthProviderName';
 export * from './OAuthProvidersResponse';
 export * from './OAuthProvidersResponseData';
 export * from './OAuthTokensRefreshResponse';
@@ -265,6 +267,7 @@ export * from './SendSlackMessageResult';
 export * from './SendSmsData';
 export * from './SendSmsRequest';
 export * from './SendSmsResponse';
+export * from './SendTemplateTestEmailRequest';
 export * from './SendTestSmsData';
 export * from './SendTestSmsRequest';
 export * from './SendTestSmsResponse';
@@ -273,9 +276,11 @@ export * from './SessionListResponse';
 export * from './SessionListResponseData';
 export * from './SessionListResponseDataSessionInfo';
 export * from './SetDomainInboundRequest';
+export * from './SetEndUserClaimsRequest';
 export * from './SetPreferencesRequest';
 export * from './SetPreferencesRequestPreferencesInner';
 export * from './SignInAnonymouslyRequest';
+export * from './SignInWithGameCenterRequest';
 export * from './SlackMessage';
 export * from './SlackMessageListResponse';
 export * from './SlackMessageListResponseMeta';
@@ -331,6 +336,7 @@ export * from './UnsubscribeListResponse';
 export * from './UnsubscribeRequest';
 export * from './UnsubscribeResponse';
 export * from './UpdateCategoryRequest';
+export * from './UpdateEndUserByApplicationRequest';
 export * from './UpdateEndUserRequest';
 export * from './UpdateOrganizationMemberRoleRequest';
 export * from './UpdateOrganizationRequest';

package/src/src/runtime.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