@celigo/api-specs 0.2.39 → 0.2.41

package/dist/lookupcache.yml

@@ -1185,6 +1185,13 @@ components:
           description: Display name of the dependent resource.
           examples:
             - Import Orders to NetSuite
+        type:
+          type: string
+          description: |-
+            Sub-type of the dependent resource when its collection distinguishes one, such as
+            `stream` for a listener export. Only present for resource types that carry a `type`.
+          examples:
+            - stream
         paths:
           type: array
           description: |-

package/dist/marketplace.yml

@@ -22,9 +22,10 @@ tags:
 
       - **Integration Apps** — licensed, Celigo-built connectors (e.g.
         Shopify–NetSuite) that install with managed updates.
-      - **Templates** — reusable integration blueprints that create a set of
-        resources (integration, connections, flows, exports, imports, scripts)
-        when installed.
+      - **Templates** — reusable blueprints that create a set of resources
+        when installed: an integration with its flows, connections, exports,
+        imports, and scripts (`type: integration`), or an MCP server with its
+        tools (`type: mcpserver`).
 
       You can preview what a template would create before committing to the
       install.
@@ -33,6 +34,95 @@ tags:
 
       {% openapi-schemas spec="marketplace" schemas="MarketplaceEntry" grouped="true" %}
 paths:
+  /v1/templates/published:
+    get:
+      x-internal: false
+      operationId: listPublishedTemplates
+      tags:
+        - Marketplace
+      summary: List published Templates
+      description: |-
+        Returns the marketplace catalog of published **Templates** — the
+        Template-only counterpart of `GET /v1/published` (Integration Apps only).
+        Every entry carries `type`, which tells you whether the template installs
+        an integration or an MCP server and therefore which install route to
+        call. Entries have no `docType`.
+
+        The whole catalog is returned in one response, sorted by `name` unless
+        `sort_by` says otherwise. Templates that reference an application no
+        longer available on the platform are left out, so this list can be
+        shorter than the `docType: Template` subset of
+        `POST /v1/published/combined`.
+      parameters:
+        - name: sort_by
+          in: query
+          required: false
+          schema:
+            type: string
+            enum:
+              - name
+              - lastModified
+            default: name
+            x-enumDescriptions:
+              name: Sort by name, A→Z (case-sensitive, uppercase first)
+              lastModified: Sort by last modification date, newest first
+            examples:
+              - lastModified
+          description: |-
+            Sort key. The direction is fixed per key — ascending for `name`,
+            descending for `lastModified`.
+      responses:
+        '200':
+          description: Array of Template marketplace entries.
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: '#/components/schemas/MarketplaceEntry'
+              examples:
+                default:
+                  summary: One integration template and one MCP server template
+                  value:
+                    - _id: 606e109607404c69e620a938
+                      name: Error automation via integrator.io APIs
+                      description: Automate error management using integrator.io's error APIs, with sample flows that retrieve, classify, and retry errors automatically.
+                      websiteURL: https://www.celigo.com/
+                      applications:
+                        - 6384b4ad7fe100355d2bd646
+                      user:
+                        name: Celigo Product
+                        company: Celigo
+                      lastModified: '2026-09-20T20:12:07.747Z'
+                      numInstalls: 1009
+                      type: integration
+                    - _id: 6ab129aeb9e4547494c0667f
+                      name: Acumatica
+                      description: Connect an AI agent to Acumatica ERP with a well-described set of tools to read finance, sales, and inventory data and draft documents for review.
+                      applications:
+                        - 673706dddd4fd1c46b919e82
+                      user:
+                        name: Celigo Agents
+                        company: Celigo
+                      lastModified: '2026-09-22T01:17:47.223Z'
+                      numInstalls: 5
+                      type: mcpserver
+        '204':
+          description: No published templates are available.
+        '400':
+          description: '`sort_by` is not one of the accepted keys.'
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+              examples:
+                invalidSortBy:
+                  value:
+                    errors:
+                      - code: invalid_query_param
+                        message: The query parameter "sort_by" has invalid value.
+        '401':
+          $ref: '#/components/responses/401-unauthorized'
   /v1/templates/{_id}/preview:
     get:
       x-internal: false
@@ -42,17 +132,21 @@ paths:
       summary: Preview a template's installed resource docs
       description: |-
         Returns the concrete resource documents a template would create if
-        installed. The response is an envelope `{objects, stackRequired}` where
-        `objects` is an array of `{model, doc}` entries — one per resource that
-        the install step would materialize.
+        installed. The response is an envelope `{type, objects, stackRequired}`
+        where `objects` is an array of `{model, doc}` entries — one per resource
+        that the install step would materialize.
 
+        `type` tells you which install route to use afterwards:
+        `POST /v1/integrations/template/{_id}` for `integration`,
+        `POST /v1/mcpservers/template/{_templateId}` for `mcpserver`.
         `stackRequired` is `true` when the template includes NetSuite-distributed
         resources that need a dedicated stack — the installer prompts for one
         before the install proceeds.
 
         The ID must belong to a Template, not a Connector (Integration App).
         Connector IDs from `/v1/published` return 404 here -- pull template
-        IDs from the `Template`-typed entries of `POST /v1/published/combined`.
+        IDs from `GET /v1/templates/published` or the `Template`-typed entries
+        of `POST /v1/published/combined`.
       parameters:
         - name: _id
           in: path
@@ -71,9 +165,36 @@ paths:
               schema:
                 $ref: '#/components/schemas/TemplatePreviewResponse'
               examples:
+                mcpServer:
+                  summary: MCP server template preview
+                  value:
+                    type: mcpserver
+                    stackRequired: false
+                    objects:
+                      - model: McpServer
+                        doc:
+                          name: Acumatica
+                          description: Connect an AI agent to Acumatica ERP.
+                          relativeURI: /acumatica
+                          disabled: true
+                          tools:
+                            - _toolId: 6aa95cff3ec91536beefef18
+                              name: list_bills
+                          prompts: []
+                      - model: Connection
+                        doc:
+                          _id: 6aa9baf21ed971fe88759345
+                          type: http
+                          name: Acumatica Connection
+                      - model: Tool
+                        doc:
+                          _id: 6aa95cff3ec91536beefef18
+                          name: '[Acumatica Finance] List bills'
+                          description: Retrieve Acumatica AP bills, optionally filtered by vendor and status.
                 default:
                   summary: Shopify - NetSuite template preview
                   value:
+                    type: integration
                     stackRequired: false
                     objects:
                       - model: Integration
@@ -174,7 +295,9 @@ paths:
       description: |-
         Returns a unified array of **all** marketplace content — both Integration
         Apps (`docType: Connector`) and Templates (`docType: Template`). Each
-        entry carries the `docType` discriminator so callers can partition.
+        entry carries the `docType` discriminator so callers can partition, and
+        every Template entry also carries `type` (`integration` or `mcpserver`),
+        which decides its install route.
 
         Despite being a POST, this is a **read-only, safe** endpoint — the body
         is an empty `{}` in the default CLI invocation. POST is used purely to
@@ -245,6 +368,7 @@ paths:
                     - _id: 606e109607404c69e620a938
                       name: Error automation via integrator.io APIs
                       docType: Template
+                      type: integration
                       description: Template that automates flow error handling via integrator.io APIs.
                       applications:
                         - integrator.io
@@ -290,105 +414,11 @@ components:
       type: http
       scheme: bearer
   schemas:
-    TemplatePreviewResponse:
-      type: object
-      description: |-
-        Envelope describing what a template's install would produce. `objects[]`
-        enumerates each resource doc the installer would create, tagged by
-        `model`. The docs are populated with the template's defaults and
-        placeholder ids that the installer rewrites during the real install.
-      properties:
-        objects:
-          type: array
-          description: |-
-            Resource docs the installer would materialize. Ordering is
-            typically `Integration` first (exactly one), then `Connection`s,
-            `Export`s, `Import`s, `Flow`s, `Script`s.
-          items:
-            type: object
-            description: One resource doc tagged with its model type.
-            properties:
-              model:
-                type: string
-                enum:
-                  - Integration
-                  - Connection
-                  - Export
-                  - Import
-                  - Flow
-                  - Script
-                  - AsyncHelper
-                x-enumDescriptions:
-                  Integration: Integration workspace resource.
-                  Connection: Connection resource for authenticating to external systems.
-                  Export: Export resource for reading data from a source system.
-                  Import: Import resource for writing data to a destination system.
-                  Flow: Flow resource for data integration pipelines.
-                  Script: Script resource for custom JavaScript hooks.
-                  AsyncHelper: Async helper resource for polling-based connection patterns.
-                description: Resource class this doc describes.
-              doc:
-                type: object
-                description: |-
-                  The concrete resource document. Shape matches the write shape
-                  of the corresponding resource endpoint (e.g. `POST /v1/flows`,
-                  `POST /v1/exports`, etc.). Fields are populated with the
-                  template's defaults; ids are placeholders that the installer
-                  replaces during the real install.
-                additionalProperties: true
-        stackRequired:
-          type: boolean
-          description: |-
-            `true` when the template includes NetSuite-distributed resources
-            that need a dedicated stack — the installer prompts for one before
-            the install proceeds. `false` for Shopify / HTTP / file-only
-            templates.
-    Error:
-      type: object
-      description: Standard error response envelope returned by integrator.io APIs.
-      properties:
-        errors:
-          type: array
-          description: List of errors that occurred while processing the request.
-          items:
-            type: object
-            properties:
-              code:
-                oneOf:
-                  - type: string
-                  - type: integer
-                description: |-
-                  Machine-readable error code. Usually a string like
-                  `invalid_ref`, `missing_required_field`, or `unauthorized`;
-                  may be an **integer** when the error mirrors an upstream HTTP
-                  status (e.g. `500`) — most commonly returned by connection-ping
-                  and adaptor-proxy responses.
-              message:
-                type: string
-                description: Human-readable description of the error.
-              field:
-                type: string
-                description: |-
-                  Optional pointer to the document field that caused the error.
-                  Used by structural validation errors (`missing_required_field`,
-                  `invalid_ref`) to indicate which field is at fault
-                  (e.g. `_id`, `type`, `http.baseURI`).
-              source:
-                type: string
-                description: |-
-                  Optional origin layer for the error — e.g. `application` when
-                  the error came from the remote system the adaptor called,
-                  `connector` when the adaptor itself rejected the request.
-            required:
-              - message
-      required:
-        - errors
     MarketplaceEntry:
       type: object
       required:
         - _id
         - name
-        - description
         - applications
         - numInstalls
         - user
@@ -396,8 +426,8 @@ components:
       description: |-
         A single marketplace listing — either an Integration App (`docType: Connector`)
         or a Template (`docType: Template`). `docType` is only present in
-        `POST /v1/published/combined` responses; `GET /v1/published` entries (Connectors
-        only) omit the field.
+        `POST /v1/published/combined` responses; `GET /v1/published` (Connectors
+        only) and `GET /v1/templates/published` (Templates only) omit the field.
       properties:
         _id:
           type: string
@@ -412,9 +442,27 @@ components:
             - Shopify - NetSuite
         description:
           type: string
-          description: Marketing description shown in the marketplace listing.
+          description: |-
+            Marketing description shown in the marketplace listing. Always set on
+            Integration Apps; a Template publisher can leave it blank, in which
+            case the field is absent.
           examples:
             - Sync products, orders, fulfillments, and inventory between Shopify and NetSuite.
+        type:
+          type: string
+          enum:
+            - integration
+            - mcpserver
+          x-enumDescriptions:
+            integration: Template installs an integration — use `POST /v1/integrations/template/{_id}`
+            mcpserver: Template installs an MCP server — use `POST /v1/mcpservers/template/{_templateId}`
+          description: |-
+            Kind of resource a Template installs, which decides the install route.
+            Present on every Template entry (`GET /v1/templates/published` and
+            `docType: Template` entries of `POST /v1/published/combined`); absent
+            on Connector entries, which install through their own route.
+          examples:
+            - integration
         imageURL:
           type: string
           description: |-
@@ -646,6 +694,138 @@ components:
             isParentChild:
               type: boolean
               description: When true, this Integration App uses the parent-child model.
+    Error:
+      type: object
+      description: Standard error response envelope returned by integrator.io APIs.
+      properties:
+        errors:
+          type: array
+          description: List of errors that occurred while processing the request.
+          items:
+            type: object
+            properties:
+              code:
+                oneOf:
+                  - type: string
+                  - type: integer
+                description: |-
+                  Machine-readable error code. Usually a string like
+                  `invalid_ref`, `missing_required_field`, or `unauthorized`;
+                  may be an **integer** when the error mirrors an upstream HTTP
+                  status (e.g. `500`) — most commonly returned by connection-ping
+                  and adaptor-proxy responses.
+              message:
+                type: string
+                description: Human-readable description of the error.
+              field:
+                type: string
+                description: |-
+                  Optional pointer to the document field that caused the error.
+                  Used by structural validation errors (`missing_required_field`,
+                  `invalid_ref`) to indicate which field is at fault
+                  (e.g. `_id`, `type`, `http.baseURI`).
+              source:
+                type: string
+                description: |-
+                  Optional origin layer for the error — e.g. `application` when
+                  the error came from the remote system the adaptor called,
+                  `connector` when the adaptor itself rejected the request.
+            required:
+              - message
+      required:
+        - errors
+    TemplatePreviewResponse:
+      type: object
+      description: |-
+        Envelope describing what a template's install would produce. `objects[]`
+        enumerates each resource doc the installer would create, tagged by
+        `model`. The docs are populated with the template's defaults and
+        placeholder ids that the installer rewrites during the real install.
+      required:
+        - objects
+        - stackRequired
+        - type
+      properties:
+        type:
+          type: string
+          enum:
+            - integration
+            - mcpserver
+          x-enumDescriptions:
+            integration: Install with `POST /v1/integrations/template/{_id}`; `objects[]` starts with the `Integration` doc
+            mcpserver: Install with `POST /v1/mcpservers/template/{_templateId}`; `objects[]` starts with the `McpServer` doc
+          description: |-
+            Kind of resource the template installs. Read it before installing —
+            the two kinds use different install routes, and the integration route
+            rejects MCP server templates.
+          examples:
+            - integration
+        objects:
+          type: array
+          description: |-
+            Resource docs the installer would materialize. For an integration
+            template the ordering is `Integration` first (exactly one), then
+            `Connection`s, `Flow`s, `Export`s, `Import`s, `Script`s and any
+            other supporting resources; for an MCP server template it is the
+            `McpServer` doc first, then its `Connection`s, `Export`s, `Import`s,
+            `Script`s and `Tool`s, then one `Prompt` entry per inline prompt.
+          items:
+            type: object
+            description: One resource doc tagged with its model type.
+            properties:
+              model:
+                type: string
+                enum:
+                  - Integration
+                  - McpServer
+                  - Connection
+                  - Flow
+                  - Export
+                  - Import
+                  - Script
+                  - AsyncHelper
+                  - FileDefinition
+                  - EDIProfile
+                  - LookupCache
+                  - Api
+                  - Tool
+                  - Prompt
+                x-enumDescriptions:
+                  Integration: Integration workspace resource (integration templates only)
+                  McpServer: MCP server resource (MCP server templates only)
+                  Connection: Connection resource for authenticating to external systems
+                  Flow: Flow resource for data integration pipelines
+                  Export: Export resource for reading data from a source system
+                  Import: Import resource for writing data to a destination system
+                  Script: Script resource for custom JavaScript hooks
+                  AsyncHelper: Async helper resource for polling-based connection patterns
+                  FileDefinition: File definition resource for parsing and generating EDI or fixed-width files
+                  EDIProfile: EDI profile resource describing a trading partner
+                  LookupCache: Lookup cache resource for key-value lookups during flow runs
+                  Api: Builder-mode API resource
+                  Tool: Tool resource invoked by MCP servers, APIs, and flows
+                  Prompt: Inline prompt definition of the MCP server (MCP server templates only)
+                description: |-
+                  Resource class this doc describes. Which classes appear depends
+                  on what the template zip contains; `Integration` and `Prompt`
+                  never appear together because they belong to different template
+                  kinds.
+              doc:
+                type: object
+                description: |-
+                  The concrete resource document. Shape matches the write shape
+                  of the corresponding resource endpoint (e.g. `POST /v1/flows`,
+                  `POST /v1/exports`, etc.). Fields are populated with the
+                  template's defaults; ids are placeholders that the installer
+                  replaces during the real install.
+                additionalProperties: true
+        stackRequired:
+          type: boolean
+          description: |-
+            `true` when the template includes NetSuite-distributed resources
+            that need a dedicated stack — the installer prompts for one before
+            the install proceeds. `false` for Shopify / HTTP / file-only
+            templates.
   responses:
     401-unauthorized:
       description: |-