@celigo/api-specs 0.2.30 → 0.2.32

package/dist/enduser.yml

@@ -23,7 +23,11 @@ tags:
       in bulk), list and revoke them, and inspect the effective MCP tool
       access compiled from their grants, groups, and roles. An end user's
       access record is an ashare, so editing its grants and suspending it
-      use the `/v1/ashares` routes shared with workspace users.
+      use the `/v1/ashares` routes shared with workspace users. The account
+      owner is never an end user: owners already have MCP access without an
+      end-user record, the invite refuses the owner's address
+      (`owner_self_invite_not_allowed`), and the owner never appears in
+      these lists.
 
       ## End user schema
 
@@ -59,7 +63,9 @@ paths:
         Returns the account's end users with identity fields (`email`, `name`,
         `lastSignIn`) joined from each user record, plus a computed
         `hasWorkspaceShare` flag indicating whether the same person also holds a
-        workspace access record. Requires account owner or administrator access.
+        workspace access record. The account owner is never listed: owners
+        have MCP access without an end-user record, so none exists for them.
+        Requires account owner or administrator access.
       parameters:
         - name: provisionedBy
           in: query
@@ -124,8 +130,11 @@ paths:
       description: |-
         Finds or creates the user by email, creates an end-user access record,
         applies the requested group memberships and direct grants, and sends an
-        invite email. Account owners cannot be invited as end users. Requires
-        account owner or administrator access.
+        invite email. The account owner cannot be invited as an end user
+        (`owner_self_invite_not_allowed`): owners already have MCP access
+        without an end-user record, so there is nothing to grant — test
+        end-user access with a different address. Requires account owner or
+        administrator access.
       requestBody:
         required: true
         content:
@@ -163,7 +172,20 @@ paths:
                     _ashareId: 68b1c2d3e4f5a6b7c8d9e0f1
                     status: invited
         '400':
-          $ref: '#/components/responses/400-bad-request'
+          description: |-
+            The email is missing or invalid (`email_invalid`), or it is the
+            account owner's address (`owner_self_invite_not_allowed` — the owner
+            already has MCP access without an end-user record).
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                ownerSelfInvite:
+                  value:
+                    errors:
+                      - code: owner_self_invite_not_allowed
+                        message: Account owners cannot be invited as end-users. Owners already have MCP access without an end-user share.
         '401':
           $ref: '#/components/responses/401-unauthorized'
         '403':
@@ -1403,7 +1425,7 @@ components:
                 x-enumDescriptions:
                   email_invalid: The email address is not valid
                   enduser_ashare_exists: An end-user record already exists for this user in the account
-                  owner_self_invite_not_allowed: Account owners cannot be invited as end users
+                  owner_self_invite_not_allowed: The address is the account owner's — owners already have MCP access without an end-user record
                   validation_failed: The shared groupIds or grants failed validation for this item
                   invite_failed: An unexpected per-item error, caught so the batch can continue
                 description: Failure reason. Present when status is `failed`.

package/dist/mcp-server.yml

@@ -551,8 +551,11 @@ paths:
         server and compiles each one's effective tool access with source
         attribution — the union of direct grants, group grants, role grants, and
         permission sets. The result is recomputed on every request rather than
-        cached. Requires account owner or administrator access. The per-user view
-        of the same compilation is `GET /v1/endusers/{_ashareId}/effective-access`
+        cached. The account owner is never listed — owners have MCP access
+        without an end-user record, so there is no record to compile — and an
+        empty result therefore means no end user has been granted this server.
+        Requires account owner or administrator access. The per-user view of the
+        same compilation is `GET /v1/endusers/{_ashareId}/effective-access`
         (End Users API).
       parameters:
         - name: _id

package/dist/sync.yml

@@ -2602,9 +2602,10 @@ paths:
       summary: List supported sync destination applications
       description: |-
         Returns the catalog of applications that can be used as the **destination** of a sync — the
-        data warehouse a sync loads records into. Use the returned `id` as the destination application
-        when building a sync. Identifiers include `snowflake` (Snowflake), `nsaw` (NetSuite
-        Analytics Warehouse), and `bigquery` (Google BigQuery).
+        data warehouse a sync loads records into. A sync's destination application is the type of
+        its destination connection (`rdbms.type` for warehouse connections), which must match one
+        of the returned ids. Identifiers include `snowflake` (Snowflake), `nsaw` (NetSuite
+        Analytics Warehouse), `bigquery` (Google BigQuery), and `mssql` (Microsoft SQL Server).
       tags:
         - Syncs
       operationId: listSyncDestinations
@@ -2629,8 +2630,10 @@ paths:
               examples:
                 default:
                   value:
-                    - id: snowflake
+                    - id: bigquery
+                    - id: mssql
                     - id: nsaw
+                    - id: snowflake
         '401':
           $ref: '#/components/responses/401-unauthorized'
   /v1/di/metadata/connections/{_connectionId}/datasets:
@@ -3848,27 +3851,35 @@ components:
           type: object
           description: |-
             Data warehouse the sync loads records into. Empty (`{}`) on a draft that has no
-            destination yet. Each source + destination host/database/schema combination must
-            be unique across syncs — reusing one fails with `422 duplicate_destination_host` —
-            and all syncs in an integration must target the same destination application type.
+            destination yet. The destination application is the connection's own type
+            (`rdbms.type` for warehouse connections), so `database` and `schema` are read in that
+            application's terms — Google BigQuery treats them as the GCP project and the dataset.
+            Each source + destination host/database/schema combination must be unique across
+            syncs — reusing one fails with `422 duplicate_destination_host` — and all syncs in an
+            integration must target the same destination application type.
           properties:
             _connectionId:
               type: string
               format: objectId
               x-celigo-refModel: connections
               description: |-
-                Connection to the destination warehouse. The application must be one of the
-                supported sync destinations returned by `GET /v1/di/metadata/destinations`.
+                Connection to the destination warehouse. Its application (`rdbms.type` such as
+                `snowflake`, `bigquery` or `mssql`, or a NetSuite Analytics Warehouse JDBC
+                connection) is one of the ids returned by `GET /v1/di/metadata/destinations`.
               examples:
                 - 68d02dbe0839a514623c1d6d
             database:
               type: string
-              description: Database in the destination warehouse the sync loads into.
+              description: |-
+                Database in the destination warehouse the sync loads into. For Google BigQuery this
+                is the GCP project id the tables are created in (`project.dataset.table`).
               examples:
                 - ANALYTICS_DB
             schema:
               type: string
-              description: Schema within `database` where the sync creates and loads tables.
+              description: |-
+                Schema within `database` where the sync creates and loads tables. For Google
+                BigQuery this is the dataset name, with case preserved.
               examples:
                 - salesforce_raw
             tablePrefix:
@@ -4017,27 +4028,60 @@ components:
           description: |-
             Data warehouse the sync loads records into. Omit while drafting; a complete
             destination (connection, database, schema) is required before the sync can be
-            enabled. The source + destination host/database/schema combination must be unique
+            enabled. The destination application is the connection's own type (`rdbms.type`
+            for warehouse connections), so `database` and `schema` are read in that
+            application's terms — Google BigQuery treats them as the GCP project and the
+            dataset. The source + destination host/database/schema combination must be unique
             across syncs (`422 duplicate_destination_host`), and all syncs in an integration
             must target the same destination application type.
+          x-celigo-ai-guidance:
+            - |-
+              Send the block complete or not at all. A partial block is rejected in the destination's
+              own vocabulary with 422 `invalid_destination_sync_config`: `GCP project is required on
+              sync destination` / `BigQuery dataset is required on sync destination` (BigQuery),
+              `SQL Server database is required on sync destination` / `SQL Server schema is required
+              on sync destination` (Microsoft SQL Server). A partial Snowflake block is not caught
+              by validation — the save reaches the warehouse and fails with Snowflake's own
+              `002003` "Database 'UNDEFINED' does not exist" error.
+            - |-
+              Saving a complete destination connects to the warehouse to create the schema
+              (dataset) when it is missing. An unreachable host or unusable credentials fail the
+              save with the connection's error — 422 `invalid_host` for SQL Server,
+              `big_query_unexpected_error` for BigQuery — and no sync document is created or
+              updated; fix the connection rather than changing database or schema names.
+            - |-
+              Microsoft SQL Server validates `database` and `schema` as identifiers (start with a
+              letter or underscore; letters, digits, underscore or `$`; at most 128 characters) and
+              rejects others with 422 `invalid_destination_sync_config`
+              (`SQL Server schema name is invalid: ...`).
           properties:
             _connectionId:
               type: string
               format: objectId
               x-celigo-refModel: connections
               description: |-
-                Connection to the destination warehouse. The application must be one of the
-                supported sync destinations returned by `GET /v1/di/metadata/destinations`.
+                Connection to the destination warehouse. Its application (`rdbms.type` such as
+                `snowflake`, `bigquery` or `mssql`, or a NetSuite Analytics Warehouse JDBC
+                connection) must be one of the ids returned by `GET /v1/di/metadata/destinations`;
+                any other connection fails with `422 invalid_destination_type`.
               examples:
                 - 68d02dbe0839a514623c1d6d
             database:
               type: string
-              description: Database in the destination warehouse the sync loads into.
+              description: |-
+                Database in the destination warehouse the sync loads into; it must already exist.
+                For Google BigQuery this is the GCP project id the tables are created in
+                (`project.dataset.table`).
+              x-celigo-ui-override: For a BigQuery destination the Create Sync wizard shows no database picker and fills this field with the selected connection's rdbms.bigquery.projectId (IO-195900).
               examples:
                 - ANALYTICS_DB
             schema:
               type: string
-              description: Schema within `database` where the sync creates and loads tables.
+              description: |-
+                Schema within `database` where the sync creates and loads tables; created on save
+                when it does not exist. For Google BigQuery this is the dataset name, with case
+                preserved.
+              x-celigo-ui-override: For a BigQuery destination the Create Sync wizard labels this field "dataset" and accepts only letters, digits and underscore (no $), starting with a letter or underscore, at most 1024 characters (IO-195900); Snowflake and NSAW validation is unchanged.
               examples:
                 - salesforce_raw
             tablePrefix:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.30",
+  "version": "0.2.32",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "eedda60",
-		"generatedAt": "2026-09-18"
+		"iasCommit": "762b9a7",
+		"generatedAt": "2026-09-19"
 	},
 	"roots": {
 		"aiagent": 133,