@celigo/api-specs 0.2.32 → 0.2.34

package/dist/export.yml

@@ -7597,22 +7597,49 @@ 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. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointId` — see that field for the rule.
         _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. Linked on save together with `_httpConnectorEndpointId` — see that field
+            for the rule.
         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. On save the
+            platform derives it (with the version and resource ids) from `relativeURI` and `method` when
+            they match an endpoint of the connector the connection is bound to — path parameters, literal
+            ids and query strings still match — and replaces ids that belong to another connector. An id for
+            the connection's own connector is kept as sent even when the URI names a different endpoint;
+            when nothing matches, or the connection has no connector, whatever was sent is kept and nothing
+            is derived.
+          x-celigo-ai-guidance:
+            - |-
+              To build an export on a prebuilt connector instead of a hand-rolled HTTP request, bind the
+              CONNECTION (`http._httpConnectorId` — find the connector in `GET /v1/httpconnectors` by `name`
+              or `legacyId`) and write the endpoint's `relativeURI` and `method`; the platform links the
+              export to that endpoint on save, so the three pointer fields may be omitted. Read the saved
+              export back: no pointers means the URI matched no endpoint of the connection's connector. Set
+              `_httpConnectorVersionId`, `_httpConnectorResourceId` and `_httpConnectorEndpointId` together
+              only to pin a same-connector endpoint the URI would not match. Endpoint discovery through the
+              published operations: `GET /v1/httpconnectors/{_id}` (`versions`, under `apis[]` for
+              multi-API connectors), `GET /v1/httpconnectors/{_id}/httpconnectorresources`,
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`, and
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}` for an endpoint's `method` and
+              `relativeURI`. A top-level `_httpConnectorId` on the export itself is dropped. Verified against
+              the live API 2026-09-21.
       if:
         properties:
           type:

package/dist/import.yml

@@ -1661,14 +1661,30 @@ 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. On save the
+            platform derives them (with the version and resource ids) from each `relativeURI` / `method`
+            pair that matches an endpoint of the connector the connection is bound to, and replaces ids
+            that belong to another connector; ids for the connection's own connector are kept as sent, and
+            when nothing matches, or the connection has no connector, whatever was sent is kept.
+          x-celigo-ai-guidance:
+            - |-
+              To build an import on a prebuilt connector, bind the CONNECTION (`http._httpConnectorId`) and
+              write each operation's `relativeURI` and `method` into the positional arrays; the platform links
+              the import to those endpoints on save, so the pointer fields may be omitted. Read the saved
+              import back: missing entries mean a URI matched no endpoint of the connection's connector. Set
+              `_httpConnectorVersionId`, `_httpConnectorResourceId` and `_httpConnectorEndpointIds` together
+              only to pin same-connector endpoints the URIs would not match. Imports use this plural field;
+              the singular `_httpConnectorEndpointId` is dropped on write. Endpoint discovery through the
+              published operations: `GET /v1/httpconnectors/{_id}`, `…/{_id}/httpconnectorresources`,
+              `…/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`, and
+              `…/{_id}/{_httpConnectorResourceId}/{_id}` for an endpoint's `method` and `relativeURI`.
+              Verified against the live API 2026-09-21.
         blobFormat:
           type: string
           enum:
@@ -1857,17 +1873,17 @@ 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.
+              ⚠️ On save the platform derives the connector pointer fields
+              (``_httpConnectorVersionId`` / ``_httpConnectorResourceId`` /
+              ``_httpConnectorEndpointIds``) from each ``relativeURI`` /
+              ``method`` pair that matches an endpoint of the connector the
+              connection is bound to (path parameters and query strings still
+              match); pointers you send for that connector are kept, pointers
+              from another connector are replaced, and a URI that matches
+              nothing leaves whatever you sent in place — nothing is unset
+              (verified 2026-09-21 on create, on PUT, and after a re-save). Keep
+              each entry equal to the endpoint you mean so the pointer and the
+              request agree. Get the URI shape right.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json
@@ -1903,19 +1919,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. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointIds` — see that field for the rule.
         _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. Linked on save together with `_httpConnectorEndpointIds` — see that field
+            for the rule.
         _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/tool.yml

@@ -10880,14 +10880,30 @@ 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. On save the
+            platform derives them (with the version and resource ids) from each `relativeURI` / `method`
+            pair that matches an endpoint of the connector the connection is bound to, and replaces ids
+            that belong to another connector; ids for the connection's own connector are kept as sent, and
+            when nothing matches, or the connection has no connector, whatever was sent is kept.
+          x-celigo-ai-guidance:
+            - |-
+              To build an import on a prebuilt connector, bind the CONNECTION (`http._httpConnectorId`) and
+              write each operation's `relativeURI` and `method` into the positional arrays; the platform links
+              the import to those endpoints on save, so the pointer fields may be omitted. Read the saved
+              import back: missing entries mean a URI matched no endpoint of the connection's connector. Set
+              `_httpConnectorVersionId`, `_httpConnectorResourceId` and `_httpConnectorEndpointIds` together
+              only to pin same-connector endpoints the URIs would not match. Imports use this plural field;
+              the singular `_httpConnectorEndpointId` is dropped on write. Endpoint discovery through the
+              published operations: `GET /v1/httpconnectors/{_id}`, `…/{_id}/httpconnectorresources`,
+              `…/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`, and
+              `…/{_id}/{_httpConnectorResourceId}/{_id}` for an endpoint's `method` and `relativeURI`.
+              Verified against the live API 2026-09-21.
         blobFormat:
           type: string
           enum:
@@ -11076,17 +11092,17 @@ 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.
+              ⚠️ On save the platform derives the connector pointer fields
+              (``_httpConnectorVersionId`` / ``_httpConnectorResourceId`` /
+              ``_httpConnectorEndpointIds``) from each ``relativeURI`` /
+              ``method`` pair that matches an endpoint of the connector the
+              connection is bound to (path parameters and query strings still
+              match); pointers you send for that connector are kept, pointers
+              from another connector are replaced, and a URI that matches
+              nothing leaves whatever you sent in place — nothing is unset
+              (verified 2026-09-21 on create, on PUT, and after a re-save). Keep
+              each entry equal to the endpoint you mean so the pointer and the
+              request agree. Get the URI shape right.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json
@@ -11122,19 +11138,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. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointIds` — see that field for the rule.
         _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. Linked on save together with `_httpConnectorEndpointIds` — see that field
+            for the rule.
         _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 +28160,49 @@ 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. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointId` — see that field for the rule.
         _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. Linked on save together with `_httpConnectorEndpointId` — see that field
+            for the rule.
         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. On save the
+            platform derives it (with the version and resource ids) from `relativeURI` and `method` when
+            they match an endpoint of the connector the connection is bound to — path parameters, literal
+            ids and query strings still match — and replaces ids that belong to another connector. An id for
+            the connection's own connector is kept as sent even when the URI names a different endpoint;
+            when nothing matches, or the connection has no connector, whatever was sent is kept and nothing
+            is derived.
+          x-celigo-ai-guidance:
+            - |-
+              To build an export on a prebuilt connector instead of a hand-rolled HTTP request, bind the
+              CONNECTION (`http._httpConnectorId` — find the connector in `GET /v1/httpconnectors` by `name`
+              or `legacyId`) and write the endpoint's `relativeURI` and `method`; the platform links the
+              export to that endpoint on save, so the three pointer fields may be omitted. Read the saved
+              export back: no pointers means the URI matched no endpoint of the connection's connector. Set
+              `_httpConnectorVersionId`, `_httpConnectorResourceId` and `_httpConnectorEndpointId` together
+              only to pin a same-connector endpoint the URI would not match. Endpoint discovery through the
+              published operations: `GET /v1/httpconnectors/{_id}` (`versions`, under `apis[]` for
+              multi-API connectors), `GET /v1/httpconnectors/{_id}/httpconnectorresources`,
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/httpconnectorendpoints`, and
+              `GET /v1/httpconnectors/{_id}/{_httpConnectorResourceId}/{_id}` for an endpoint's `method` and
+              `relativeURI`. A top-level `_httpConnectorId` on the export itself is dropped. 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.32",
+  "version": "0.2.34",
   "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": "762b9a7",
-		"generatedAt": "2026-09-19"
+		"iasCommit": "820b9fd",
+		"generatedAt": "2026-09-21"
 	},
 	"roots": {
 		"aiagent": 133,