@celigo/api-specs 0.2.31 → 0.2.33

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/export.yml

@@ -7597,22 +7597,45 @@ components:
         _httpConnectorVersionId:
           type: string
           format: objectId
-          readOnly: true
-          description: Identifies the HTTP connector version used by this export. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Pins the export to a version of the published HTTP connector its connection is bound to
+            (`connection.http._httpConnectorId`), so the UI renders that connector's endpoint form instead
+            of a hand-authored request. Persisted as sent on create and update; the value is not checked
+            against the connection's connector.
         _httpConnectorResourceId:
           type: string
           format: objectId
-          readOnly: true
-          description: Identifies the HTTP connector resource used by this export. Set by the connector framework; client-supplied values are ignored (write-tested).
+          x-celigo-refModel: httpconnectorresources
+          description: |-
+            The connector resource (a group of related endpoints, such as Orders) that this export's
+            endpoint belongs to. Persisted as sent; take it from the same connector blueprint as
+            `_httpConnectorVersionId`.
         sendAuthForFileDownloads:
           type: boolean
           description: When true, includes authentication headers when downloading files.
         _httpConnectorEndpointId:
           type: string
           format: objectId
-          readOnly: true
           x-celigo-refModel: httpconnectorendpoints
-          description: Identifies the HTTP connector endpoint configuration used for this export's requests. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            The connector endpoint this export calls, shown in the UI as the selected endpoint;
+            `relativeURI` and `method` should match that endpoint's definition. Persisted as sent on create
+            and update — the server does not verify that the endpoint belongs to the connection's connector,
+            so a mismatched id pins the export to the wrong endpoint form.
+          x-celigo-ai-guidance:
+            - |-
+              To build an export on a prebuilt connector instead of a hand-rolled HTTP request: find the
+              connector in `GET /v1/httpconnectors` (match `name` or `legacyId`); read
+              `GET /v1/httpconnectors/{_id}` for its `versions` (under `apis[]` for multi-API connectors);
+              list resources with `GET /v1/httpconnectors/{_id}/httpconnectorresources`, then that resource's
+              endpoints with `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`
+              and one endpoint's `method` and `relativeURI` with
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}`; copy that `relativeURI` and
+              `method` and set `_httpConnectorVersionId`, `_httpConnectorResourceId`, and
+              `_httpConnectorEndpointId` together. The export's connection must carry `http._httpConnectorId`
+              for the same connector; a top-level `_httpConnectorId` on the export itself is dropped. Omit all
+              three only when no published connector exists for the application. Verified against the live
+              API 2026-09-21.
       if:
         properties:
           type:

package/dist/import.yml

@@ -1661,14 +1661,27 @@ components:
             - xml
         _httpConnectorEndpointIds:
           type: array
-          readOnly: true
           items:
             type: string
             format: objectId
             x-celigo-refModel: httpconnectorendpoints
           description: |-
-            HTTP connector endpoint IDs used by this import (multiple endpoints for different request
-            types or operations). Set by the connector framework; client-supplied values are ignored.
+            The connector endpoints this import calls, one per entry of `relativeURI` / `method` (for
+            example a CREATE and an UPDATE endpoint), shown in the UI as the selected endpoints. Persisted
+            as sent on create and update; the server does not verify that they belong to the connection's
+            connector.
+          x-celigo-ai-guidance:
+            - |-
+              To build an import on a prebuilt connector: find the connector in `GET /v1/httpconnectors`; read
+              `GET /v1/httpconnectors/{_id}` for its `versions` (under `apis[]` for multi-API connectors); list
+              resources with `GET /v1/httpconnectors/{_id}/httpconnectorresources` and a resource's endpoints
+              with `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`; read each
+              chosen endpoint's `method` and `relativeURI` with
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}` and copy them into the positional
+              arrays, one endpoint per operation; set `_httpConnectorVersionId`, `_httpConnectorResourceId`, and
+              `_httpConnectorEndpointIds` together. Imports use this plural field; the singular
+              `_httpConnectorEndpointId` is dropped on write. The import's connection must carry
+              `http._httpConnectorId` for the same connector. Verified against the live API 2026-09-21.
         blobFormat:
           type: string
           enum:
@@ -1857,17 +1870,16 @@ components:
               // shape; do not emit it deliberately.
               "relativeURI": ["[\"/customers/{{{data.0.id}}}\",\"/customers\"]"]
               ```
-              ⚠️ The platform performs a URI-vs-pointer-metadata cross-check
-              on save: when the persisted ``relativeURI`` doesn't match the
-              endpoint blueprint the connector pointer fields
-              (``_httpConnectorId`` / ``_httpConnectorVersionId`` /
-              ``_httpConnectorResourceId`` / ``_httpConnectorEndpointId(s)``)
-              are SILENTLY UNSET so they stay in sync with future user edits.
-              Any malformed URI shape (stringified, wrong nesting, etc.)
-              therefore breaks the marketplace audit link, the UI's
-              assistant-view selector, and mid-build schema introspection —
-              the import will work at runtime but loses every "this is a
-              Pipedrive Persons resource" signal.  Get the URI shape right.
+              ⚠️ The API does NOT cross-check ``relativeURI`` / ``method`` against
+              the connector pointer fields (``_httpConnectorVersionId`` /
+              ``_httpConnectorResourceId`` / ``_httpConnectorEndpointIds``):
+              a save whose URI does not match the pinned endpoint keeps the
+              pointers exactly as sent (verified 2026-09-21 on create, on PUT,
+              after 60 s, and after a no-op re-save). The consistency is yours
+              to keep — copy each pinned endpoint's ``relativeURI`` and
+              ``method`` into these arrays position by position, so the
+              endpoint the pointers name and the request the runtime sends
+              are the same one. Get the URI shape right.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json
@@ -1903,19 +1915,27 @@ components:
         _httpConnectorVersionId:
           type: string
           format: objectId
-          readOnly: true
-          description: HTTP connector version used by this import. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Pins the import to a version of the published HTTP connector its connection is bound to
+            (`connection.http._httpConnectorId`), so the UI renders that connector's endpoint forms instead
+            of hand-authored requests. Persisted as sent on create and update; not checked against the
+            connection's connector.
         _httpConnectorResourceId:
           type: string
           format: objectId
-          readOnly: true
-          description: HTTP connector resource used by this import. Set by the connector framework; client-supplied values are ignored (write-tested).
+          x-celigo-refModel: httpconnectorresources
+          description: |-
+            The connector resource (a group of related endpoints, such as Orders) that this import's
+            endpoints belong to. Persisted as sent; take it from the same connector blueprint as
+            `_httpConnectorVersionId`.
         _httpConnectorEndpointId:
           type: string
           format: objectId
           readOnly: true
           x-celigo-refModel: httpconnectorendpoints
-          description: HTTP connector endpoint used by this import (single endpoint). Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Not used by imports: values sent on create or update are dropped, and the platform does not
+            populate it. Imports bind connector endpoints per operation through `_httpConnectorEndpointIds`.
         body:
           type: array
           items:

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/tool.yml

@@ -10880,14 +10880,27 @@ components:
             - xml
         _httpConnectorEndpointIds:
           type: array
-          readOnly: true
           items:
             type: string
             format: objectId
             x-celigo-refModel: httpconnectorendpoints
           description: |-
-            HTTP connector endpoint IDs used by this import (multiple endpoints for different request
-            types or operations). Set by the connector framework; client-supplied values are ignored.
+            The connector endpoints this import calls, one per entry of `relativeURI` / `method` (for
+            example a CREATE and an UPDATE endpoint), shown in the UI as the selected endpoints. Persisted
+            as sent on create and update; the server does not verify that they belong to the connection's
+            connector.
+          x-celigo-ai-guidance:
+            - |-
+              To build an import on a prebuilt connector: find the connector in `GET /v1/httpconnectors`; read
+              `GET /v1/httpconnectors/{_id}` for its `versions` (under `apis[]` for multi-API connectors); list
+              resources with `GET /v1/httpconnectors/{_id}/httpconnectorresources` and a resource's endpoints
+              with `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`; read each
+              chosen endpoint's `method` and `relativeURI` with
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}` and copy them into the positional
+              arrays, one endpoint per operation; set `_httpConnectorVersionId`, `_httpConnectorResourceId`, and
+              `_httpConnectorEndpointIds` together. Imports use this plural field; the singular
+              `_httpConnectorEndpointId` is dropped on write. The import's connection must carry
+              `http._httpConnectorId` for the same connector. Verified against the live API 2026-09-21.
         blobFormat:
           type: string
           enum:
@@ -11076,17 +11089,16 @@ components:
               // shape; do not emit it deliberately.
               "relativeURI": ["[\"/customers/{{{data.0.id}}}\",\"/customers\"]"]
               ```
-              ⚠️ The platform performs a URI-vs-pointer-metadata cross-check
-              on save: when the persisted ``relativeURI`` doesn't match the
-              endpoint blueprint the connector pointer fields
-              (``_httpConnectorId`` / ``_httpConnectorVersionId`` /
-              ``_httpConnectorResourceId`` / ``_httpConnectorEndpointId(s)``)
-              are SILENTLY UNSET so they stay in sync with future user edits.
-              Any malformed URI shape (stringified, wrong nesting, etc.)
-              therefore breaks the marketplace audit link, the UI's
-              assistant-view selector, and mid-build schema introspection —
-              the import will work at runtime but loses every "this is a
-              Pipedrive Persons resource" signal.  Get the URI shape right.
+              ⚠️ The API does NOT cross-check ``relativeURI`` / ``method`` against
+              the connector pointer fields (``_httpConnectorVersionId`` /
+              ``_httpConnectorResourceId`` / ``_httpConnectorEndpointIds``):
+              a save whose URI does not match the pinned endpoint keeps the
+              pointers exactly as sent (verified 2026-09-21 on create, on PUT,
+              after 60 s, and after a no-op re-save). The consistency is yours
+              to keep — copy each pinned endpoint's ``relativeURI`` and
+              ``method`` into these arrays position by position, so the
+              endpoint the pointers name and the request the runtime sends
+              are the same one. Get the URI shape right.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json
@@ -11122,19 +11134,27 @@ components:
         _httpConnectorVersionId:
           type: string
           format: objectId
-          readOnly: true
-          description: HTTP connector version used by this import. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Pins the import to a version of the published HTTP connector its connection is bound to
+            (`connection.http._httpConnectorId`), so the UI renders that connector's endpoint forms instead
+            of hand-authored requests. Persisted as sent on create and update; not checked against the
+            connection's connector.
         _httpConnectorResourceId:
           type: string
           format: objectId
-          readOnly: true
-          description: HTTP connector resource used by this import. Set by the connector framework; client-supplied values are ignored (write-tested).
+          x-celigo-refModel: httpconnectorresources
+          description: |-
+            The connector resource (a group of related endpoints, such as Orders) that this import's
+            endpoints belong to. Persisted as sent; take it from the same connector blueprint as
+            `_httpConnectorVersionId`.
         _httpConnectorEndpointId:
           type: string
           format: objectId
           readOnly: true
           x-celigo-refModel: httpconnectorendpoints
-          description: HTTP connector endpoint used by this import (single endpoint). Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Not used by imports: values sent on create or update are dropped, and the platform does not
+            populate it. Imports bind connector endpoints per operation through `_httpConnectorEndpointIds`.
         body:
           type: array
           items:
@@ -28136,22 +28156,45 @@ components:
         _httpConnectorVersionId:
           type: string
           format: objectId
-          readOnly: true
-          description: Identifies the HTTP connector version used by this export. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            Pins the export to a version of the published HTTP connector its connection is bound to
+            (`connection.http._httpConnectorId`), so the UI renders that connector's endpoint form instead
+            of a hand-authored request. Persisted as sent on create and update; the value is not checked
+            against the connection's connector.
         _httpConnectorResourceId:
           type: string
           format: objectId
-          readOnly: true
-          description: Identifies the HTTP connector resource used by this export. Set by the connector framework; client-supplied values are ignored (write-tested).
+          x-celigo-refModel: httpconnectorresources
+          description: |-
+            The connector resource (a group of related endpoints, such as Orders) that this export's
+            endpoint belongs to. Persisted as sent; take it from the same connector blueprint as
+            `_httpConnectorVersionId`.
         sendAuthForFileDownloads:
           type: boolean
           description: When true, includes authentication headers when downloading files.
         _httpConnectorEndpointId:
           type: string
           format: objectId
-          readOnly: true
           x-celigo-refModel: httpconnectorendpoints
-          description: Identifies the HTTP connector endpoint configuration used for this export's requests. Set by the connector framework; client-supplied values are ignored (write-tested).
+          description: |-
+            The connector endpoint this export calls, shown in the UI as the selected endpoint;
+            `relativeURI` and `method` should match that endpoint's definition. Persisted as sent on create
+            and update — the server does not verify that the endpoint belongs to the connection's connector,
+            so a mismatched id pins the export to the wrong endpoint form.
+          x-celigo-ai-guidance:
+            - |-
+              To build an export on a prebuilt connector instead of a hand-rolled HTTP request: find the
+              connector in `GET /v1/httpconnectors` (match `name` or `legacyId`); read
+              `GET /v1/httpconnectors/{_id}` for its `versions` (under `apis[]` for multi-API connectors);
+              list resources with `GET /v1/httpconnectors/{_id}/httpconnectorresources`, then that resource's
+              endpoints with `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`
+              and one endpoint's `method` and `relativeURI` with
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}`; copy that `relativeURI` and
+              `method` and set `_httpConnectorVersionId`, `_httpConnectorResourceId`, and
+              `_httpConnectorEndpointId` together. The export's connection must carry `http._httpConnectorId`
+              for the same connector; a top-level `_httpConnectorId` on the export itself is dropped. Omit all
+              three only when no published connector exists for the application. Verified against the live
+              API 2026-09-21.
       if:
         properties:
           type:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.31",
+  "version": "0.2.33",
   "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": "bcdaef7",
-		"generatedAt": "2026-09-19"
+		"iasCommit": "99c0989",
+		"generatedAt": "2026-09-21"
 	},
 	"roots": {
 		"aiagent": 133,