@celigo/api-specs 0.2.33 → 0.2.34

package/dist/export.yml

@@ -7600,16 +7600,16 @@ components:
           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.
+            of a hand-authored request. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointId` — see that field for the rule.
         _httpConnectorResourceId:
           type: string
           format: objectId
           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`.
+            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.
@@ -7618,24 +7618,28 @@ components:
           format: objectId
           x-celigo-refModel: httpconnectorendpoints
           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.
+            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: 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.
+              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

@@ -1667,21 +1667,24 @@ components:
             x-celigo-refModel: httpconnectorendpoints
           description: |-
             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.
+            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: 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.
+              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:
@@ -1870,16 +1873,17 @@ components:
               // shape; do not emit it deliberately.
               "relativeURI": ["[\"/customers/{{{data.0.id}}}\",\"/customers\"]"]
               ```
-              ⚠️ 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.
+              ⚠️ 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
@@ -1918,16 +1922,16 @@ components:
           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.
+            of hand-authored requests. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointIds` — see that field for the rule.
         _httpConnectorResourceId:
           type: string
           format: objectId
           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`.
+            endpoints belong to. Linked on save together with `_httpConnectorEndpointIds` — see that field
+            for the rule.
         _httpConnectorEndpointId:
           type: string
           format: objectId

package/dist/tool.yml

@@ -10886,21 +10886,24 @@ components:
             x-celigo-refModel: httpconnectorendpoints
           description: |-
             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.
+            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: 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.
+              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:
@@ -11089,16 +11092,17 @@ components:
               // shape; do not emit it deliberately.
               "relativeURI": ["[\"/customers/{{{data.0.id}}}\",\"/customers\"]"]
               ```
-              ⚠️ 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.
+              ⚠️ 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
@@ -11137,16 +11141,16 @@ components:
           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.
+            of hand-authored requests. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointIds` — see that field for the rule.
         _httpConnectorResourceId:
           type: string
           format: objectId
           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`.
+            endpoints belong to. Linked on save together with `_httpConnectorEndpointIds` — see that field
+            for the rule.
         _httpConnectorEndpointId:
           type: string
           format: objectId
@@ -28159,16 +28163,16 @@ components:
           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.
+            of a hand-authored request. Linked on save together with `_httpConnectorResourceId` and
+            `_httpConnectorEndpointId` — see that field for the rule.
         _httpConnectorResourceId:
           type: string
           format: objectId
           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`.
+            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.
@@ -28177,24 +28181,28 @@ components:
           format: objectId
           x-celigo-refModel: httpconnectorendpoints
           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.
+            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: 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.
+              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.33",
+  "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,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "99c0989",
+		"iasCommit": "820b9fd",
 		"generatedAt": "2026-09-21"
 	},
 	"roots": {