@celigo/api-specs 0.2.82 → 0.2.83

package/dist/export.yml

@@ -6286,6 +6286,16 @@ components:
             - |-
               This value is combined with the baseURI defined in the associated connection to
               form the complete API endpoint URL.
+            - |-
+              On a GraphQL-form export (`formType` `graph_ql` / `assistant_graphql`) the form owns
+              this field: it shows no relative-URI field and, on every save in the editor, rewrites
+              it to the GET query string it compiles from the Query / Operation name / Variables
+              fields, because the endpoint is expected to be the connection's `baseURI` — a
+              `graph_ql` connection, or a connector connection bound to its GraphQL API. A path set
+              here through the API on such an export is invisible in the editor and does not survive
+              the next save there; when the connection's base URI stops at an API root, move the
+              export to a connection that supplies the GraphQL endpoint instead of patching this
+              field.
           examples:
             - /api/v1/contacts
             - /customers/{{record.customerId}}

package/dist/import.yml

@@ -1943,6 +1943,15 @@ components:
               (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.
+            - |-
+              On a GraphQL-form import (`formType` `graph_ql` / `assistant_graphql`) the form owns
+              this field: it shows no relative-URI field and writes `["/"]` back on every save in the
+              editor, because the request path is expected to come from the connection's `baseURI` —
+              a `graph_ql` connection, or a connector connection bound to its GraphQL API. A path set
+              here through the API on such an import does reach the wire, but it is invisible in the
+              editor and reverts to `["/"]` the next time the import is saved there; when the
+              connection's base URI stops at an API root, move the import to a connection that
+              supplies the GraphQL endpoint instead of patching this field.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json

package/dist/tool.yml

@@ -12637,6 +12637,15 @@ components:
               (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.
+            - |-
+              On a GraphQL-form import (`formType` `graph_ql` / `assistant_graphql`) the form owns
+              this field: it shows no relative-URI field and writes `["/"]` back on every save in the
+              editor, because the request path is expected to come from the connection's `baseURI` —
+              a `graph_ql` connection, or a connector connection bound to its GraphQL API. A path set
+              here through the API on such an import does reach the wire, but it is invisible in the
+              editor and reverts to `["/"]` the next time the import is saved there; when the
+              connection's base URI stops at an API root, move the import to a connection that
+              supplies the GraphQL endpoint instead of patching this field.
           examples:
             - - /api/v1/customers
             - - /customers/{{{data.0.shopifyCustomerId}}}.json
@@ -29541,6 +29550,16 @@ components:
             - |-
               This value is combined with the baseURI defined in the associated connection to
               form the complete API endpoint URL.
+            - |-
+              On a GraphQL-form export (`formType` `graph_ql` / `assistant_graphql`) the form owns
+              this field: it shows no relative-URI field and, on every save in the editor, rewrites
+              it to the GET query string it compiles from the Query / Operation name / Variables
+              fields, because the endpoint is expected to be the connection's `baseURI` — a
+              `graph_ql` connection, or a connector connection bound to its GraphQL API. A path set
+              here through the API on such an export is invisible in the editor and does not survive
+              the next save there; when the connection's base URI stops at an API root, move the
+              export to a connection that supplies the GraphQL endpoint instead of patching this
+              field.
           examples:
             - /api/v1/contacts
             - /customers/{{record.customerId}}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.82",
+  "version": "0.2.83",
   "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": "cb87cb4",
+		"iasCommit": "e8402ce",
 		"generatedAt": "2026-10-09"
 	},
 	"roots": {