@zernio/node 0.2.844 → 0.2.846

package/dist/index.d.mts

@@ -3429,6 +3429,13 @@ type ApiKey = {
      * Resource groups this key can NOT access (opt-out denylist). Absent or empty means legacy full access. A key with any group disabled is a restricted key (zrk_ prefix) and can never manage API keys, invites, or member identity. Each operation's group is published as x-resource-group. With 'messages' disabled, the key cannot read or send direct messages through any API surface, and it cannot create or edit a webhook subscription broader than itself: it cannot subscribe to, test-fire, redeliver, or read delivery logs for message events. Subscriptions created earlier, from the dashboard, or with a full-access key keep delivering whatever their own `disabledResourceGroups` allows, so restricting an existing integration end to end means restricting the subscription too. OAuth connector tokens (AI assistants and MCP clients) resolve against the same registry, but their groups are not settable yet: treat an authorized connector as full access.
      */
     disabledResourceGroups?: Array<('publishing' | 'engagement' | 'messages' | 'contacts' | 'analytics' | 'ads' | 'telephony' | 'accounts' | 'billing' | 'webhooks')>;
+    /**
+     * The team member who created this key. For the team owner's listing this can be any team member; for a non-owner it is always themselves, since a non-owner only ever sees their own keys.
+     */
+    createdBy?: {
+        id?: string;
+        email?: string;
+    } | null;
 };
 /**
  * 'full' grants access to all profiles, 'profiles' restricts to specific profiles
@@ -16878,10 +16885,15 @@ type ConnectAdsData = {
          * numeric sponsored-account id), `googleads` (bare customer id digits)
          * and `twitter` (X Ads, base36 account id). `tiktok` scopes advertisers
          * at OAuth and `pinterest` has no ads discovery, so both ignore it.
-         * Meta ids are additionally validated against the connected token;
-         * unreachable IDs return 400. Setting a scope also removes already
-         * synced ads from de-scoped ad accounts. For multiple accounts use
-         * `adAccountIds` instead.
+         * Meta ids are additionally validated against the connected token:
+         * an id the token cannot see returns 400 `invalid_field_value`, and an
+         * id it can see but that Meta marks unusable for ads (disabled, closed,
+         * under risk review, settlement pending) returns 400 `ad_account_unusable`
+         * with `details.accountStatus` (Meta's `account_status`) and, when Meta
+         * gives one, `details.disableReason`. Unsettled and in-grace accounts
+         * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
+         * Setting a scope also removes already synced ads from de-scoped ad
+         * accounts. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;

package/dist/index.d.ts

@@ -3429,6 +3429,13 @@ type ApiKey = {
      * Resource groups this key can NOT access (opt-out denylist). Absent or empty means legacy full access. A key with any group disabled is a restricted key (zrk_ prefix) and can never manage API keys, invites, or member identity. Each operation's group is published as x-resource-group. With 'messages' disabled, the key cannot read or send direct messages through any API surface, and it cannot create or edit a webhook subscription broader than itself: it cannot subscribe to, test-fire, redeliver, or read delivery logs for message events. Subscriptions created earlier, from the dashboard, or with a full-access key keep delivering whatever their own `disabledResourceGroups` allows, so restricting an existing integration end to end means restricting the subscription too. OAuth connector tokens (AI assistants and MCP clients) resolve against the same registry, but their groups are not settable yet: treat an authorized connector as full access.
      */
     disabledResourceGroups?: Array<('publishing' | 'engagement' | 'messages' | 'contacts' | 'analytics' | 'ads' | 'telephony' | 'accounts' | 'billing' | 'webhooks')>;
+    /**
+     * The team member who created this key. For the team owner's listing this can be any team member; for a non-owner it is always themselves, since a non-owner only ever sees their own keys.
+     */
+    createdBy?: {
+        id?: string;
+        email?: string;
+    } | null;
 };
 /**
  * 'full' grants access to all profiles, 'profiles' restricts to specific profiles
@@ -16878,10 +16885,15 @@ type ConnectAdsData = {
          * numeric sponsored-account id), `googleads` (bare customer id digits)
          * and `twitter` (X Ads, base36 account id). `tiktok` scopes advertisers
          * at OAuth and `pinterest` has no ads discovery, so both ignore it.
-         * Meta ids are additionally validated against the connected token;
-         * unreachable IDs return 400. Setting a scope also removes already
-         * synced ads from de-scoped ad accounts. For multiple accounts use
-         * `adAccountIds` instead.
+         * Meta ids are additionally validated against the connected token:
+         * an id the token cannot see returns 400 `invalid_field_value`, and an
+         * id it can see but that Meta marks unusable for ads (disabled, closed,
+         * under risk review, settlement pending) returns 400 `ad_account_unusable`
+         * with `details.accountStatus` (Meta's `account_status`) and, when Meta
+         * gives one, `details.disableReason`. Unsettled and in-grace accounts
+         * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
+         * Setting a scope also removes already synced ads from de-scoped ad
+         * accounts. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.844",
+  version: "0.2.846",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.844",
+  version: "0.2.846",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zernio/node",
-  "version": "0.2.844",
+  "version": "0.2.846",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -1503,7 +1503,7 @@ export const verifyCredential = <ThrowOnError extends boolean = false>(options?:
 
 /**
  * List keys
- * Returns all API keys for the authenticated user. Keys are returned with a preview only, not the full key value.
+ * Returns API keys with a preview only, not the full key value. For a regular team member this is their own keys; for the team owner this is every team member's keys, each carrying a `createdBy` field.
  */
 export const listApiKeys = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<unknown, ThrowOnError>) => {
     return (options?.client ?? client).get<ListApiKeysResponse, ListApiKeysError, ThrowOnError>({
@@ -1525,7 +1525,7 @@ export const createApiKey = <ThrowOnError extends boolean = false>(options: Opti
 
 /**
  * Delete key
- * Permanently revokes and deletes an API key.
+ * Permanently revokes and deletes an API key. The team owner can revoke any team member's key; a non-owner member can only revoke their own.
  */
 export const deleteApiKey = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<DeleteApiKeyData, ThrowOnError>) => {
     return (options?.client ?? client).delete<DeleteApiKeyResponse, DeleteApiKeyError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -1799,6 +1799,13 @@ export type ApiKey = {
      * Resource groups this key can NOT access (opt-out denylist). Absent or empty means legacy full access. A key with any group disabled is a restricted key (zrk_ prefix) and can never manage API keys, invites, or member identity. Each operation's group is published as x-resource-group. With 'messages' disabled, the key cannot read or send direct messages through any API surface, and it cannot create or edit a webhook subscription broader than itself: it cannot subscribe to, test-fire, redeliver, or read delivery logs for message events. Subscriptions created earlier, from the dashboard, or with a full-access key keep delivering whatever their own `disabledResourceGroups` allows, so restricting an existing integration end to end means restricting the subscription too. OAuth connector tokens (AI assistants and MCP clients) resolve against the same registry, but their groups are not settable yet: treat an authorized connector as full access.
      */
     disabledResourceGroups?: Array<('publishing' | 'engagement' | 'messages' | 'contacts' | 'analytics' | 'ads' | 'telephony' | 'accounts' | 'billing' | 'webhooks')>;
+    /**
+     * The team member who created this key. For the team owner's listing this can be any team member; for a non-owner it is always themselves, since a non-owner only ever sees their own keys.
+     */
+    createdBy?: {
+        id?: string;
+        email?: string;
+    } | null;
 };
 
 /**
@@ -15930,10 +15937,15 @@ export type ConnectAdsData = {
          * numeric sponsored-account id), `googleads` (bare customer id digits)
          * and `twitter` (X Ads, base36 account id). `tiktok` scopes advertisers
          * at OAuth and `pinterest` has no ads discovery, so both ignore it.
-         * Meta ids are additionally validated against the connected token;
-         * unreachable IDs return 400. Setting a scope also removes already
-         * synced ads from de-scoped ad accounts. For multiple accounts use
-         * `adAccountIds` instead.
+         * Meta ids are additionally validated against the connected token:
+         * an id the token cannot see returns 400 `invalid_field_value`, and an
+         * id it can see but that Meta marks unusable for ads (disabled, closed,
+         * under risk review, settlement pending) returns 400 `ad_account_unusable`
+         * with `details.accountStatus` (Meta's `account_status`) and, when Meta
+         * gives one, `details.disableReason`. Unsettled and in-grace accounts
+         * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
+         * Setting a scope also removes already synced ads from de-scoped ad
+         * accounts. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;