Instill AI Integration API

Integration definitions for creating connections.

Operations 3

GET /v1beta/integrations List integrations #
GET /v1beta/integrations/{integrationId} Get an integration #
GET /v1beta/integrations/{integrationId_1} Get an integration #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/instill-ai:instill-ai-integration-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

instill-ai-integration-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Instill Ai Integration API
  version: v0.57.0
  contact:
    name: Instill AI
    url: https://github.com/instill-ai
    email: support@instill-ai.com
  license:
    name: MIT
    url: https://github.com/instill-ai/protobufs/blob/main/LICENSE
  description: 'Operations tagged Integration across 2 of this provider''s published API definitions: service.swagger.yaml, instill-ai-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.instill-ai.com
- url: http://api.instill-ai.com
security:
- Bearer: []
tags:
- name: Integration
  description: Integration definitions for creating connections.
paths:
  /v1beta/integrations:
    get:
      summary: List integrations
      description: Returns a paginated list of available integrations.
      operationId: PipelinePublicService_ListIntegrations
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipeline.v1beta.ListIntegrationsResponse'
        '401':
          description: Returned when the client credentials are not valid.
          content:
            application/json:
              schema: {}
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/rpc.Status'
      parameters:
      - name: pageSize
        description: 'The maximum number of items to return. The default and cap values are 10

          and 100, respectively.'
        in: query
        required: false
        schema:
          type: integer
          format: int32
      - name: pageToken
        description: Page token. By default, the first page will be returned.
        in: query
        required: false
        schema:
          type: string
      - name: filter
        description: 'Filter can hold an [AIP-160](https://google.aip.dev/160)-compliant filter

          expression. The following filters are supported:

          - `qIntegration` (fuzzy search on title or vendor)


          **Examples**:

          - List integrations where app name or vendor match `googl`: `q="googl"`.'
        in: query
        required: false
        schema:
          type: string
      tags:
      - Integration
      x-stage: beta
    servers:
    - url: https://api.instill-ai.com
    - url: http://api.instill-ai.com
  /v1beta/integrations/{integrationId}:
    get:
      summary: Get an integration
      description: Returns the details of an integration.
      operationId: MgmtPublicService_GetIntegration
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/mgmt.v1beta.GetIntegrationResponse'
        '401':
          description: Returned when the client credentials are not valid.
          content:
            application/json:
              schema: {}
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/rpc.Status'
      parameters:
      - name: integrationId
        description: Integration ID.
        in: path
        required: true
        schema:
          type: string
      - name: view
        description: "View allows clients to specify the desired view in the response.\n\n - VIEW_BASIC: Default view, only includes basic information.\n - VIEW_FULL: Full representation."
        in: query
        required: false
        schema:
          type: string
          enum:
          - VIEW_BASIC
          - VIEW_FULL
      tags:
      - Integration
      x-stage: beta
    servers:
    - url: https://api.instill-ai.com
    - url: http://api.instill-ai.com
  /v1beta/integrations/{integrationId_1}:
    get:
      summary: Get an integration
      description: Returns the details of an integration.
      operationId: PipelinePublicService_GetIntegration
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipeline.v1beta.GetIntegrationResponse'
        '401':
          description: Returned when the client credentials are not valid.
          content:
            application/json:
              schema: {}
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/rpc.Status'
      parameters:
      - name: integrationId_1
        description: Integration ID.
        in: path
        required: true
        schema:
          type: string
      - name: view
        description: "View allows clients to specify the desired view in the response.\n\n - VIEW_BASIC: Default view.\n - VIEW_FULL: Full representation."
        in: query
        required: false
        schema:
          type: string
          enum:
          - VIEW_BASIC
          - VIEW_FULL
      tags:
      - Integration
      x-stage: beta
    servers:
    - url: https://api.instill-ai.com
    - url: http://api.instill-ai.com
components:
  schemas:
    Any:
      type: object
      properties:
        '@type':
          type: string
          description: "A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none \"/\" character. The last segment of the URL's path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading \".\" is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics."
      additionalProperties: {}
      description: "`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n'type.googleapis.com/full.type.name' as the type URL and the unpack\nmethods only use the fully qualified type name after the last '/'\nin the type URL, for example \"foo.bar.com/x/y.z\" will yield type\nname \"y.z\".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      \"@type\": \"type.googleapis.com/google.profile.Person\",\n      \"firstName\": <string>,\n      \"lastName\": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      \"@type\": \"type.googleapis.com/google.protobuf.Duration\",\n      \"value\": \"1.212s\"\n    }"
    rpc.Status:
      type: object
      properties:
        code:
          type: integer
          format: int32
          description: 'The status code, which should be an enum value of

            [google.rpc.Code][google.rpc.Code].'
        message:
          type: string
          description: 'A developer-facing error message, which should be in English. Any

            user-facing error message should be localized and sent in the

            [google.rpc.Status.details][google.rpc.Status.details] field, or localized

            by the client.'
        details:
          type: array
          items:
            type: object
            $ref: '#/components/schemas/Any'
          description: 'A list of messages that carry the error details.  There is a common set of

            message types for APIs to use.'
      description: 'The `Status` type defines a logical error model that is suitable for

        different programming environments, including REST APIs and RPC APIs. It is

        used by [gRPC](https://github.com/grpc). Each `Status` message contains

        three pieces of data: error code, error message, and error details.


        You can find out more about this error model and how to work with it in the

        [API Design Guide](https://cloud.google.com/apis/design/errors).'
    mgmt.v1beta.Integration.Link:
      type: object
      properties:
        text:
          type: string
          description: Text contains the message to display.
          readOnly: true
        url:
          type: string
          description: URL contains the reference the link will redirect to.
          readOnly: true
      description: Link contains the information to display an reference to an external URL.
    mgmt.v1beta.Integration:
      type: object
      properties:
        id:
          type: string
          description: 'Field 1: Identifier of the integration, which references a component

            definition. Components with that definition ID will be able to use the

            connections produced by this integration.'
          readOnly: true
        title:
          type: string
          description: 'Field 2: Title, reflects the app name.'
          readOnly: true
        description:
          type: string
          description: 'Field 3: Short description of the integrated app.'
          readOnly: true
        vendor:
          type: string
          description: 'Field 4: Integrated app vendor name.'
          readOnly: true
        icon:
          type: string
          description: 'Field 5: Integration icon. This is a path that''s relative to the root of

            the component implementation and that allows frontend applications to pull

            and locate the icons.

            See the `icon` field in the `ComponentDefinition` entity for more

            information.'
          readOnly: true
        helpLink:
          description: 'Field 6: Reference to the vendor''s documentation to expand the integration

            details.'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/mgmt.v1beta.Integration.Link'
        setupSchema:
          type: object
          description: 'Field 7: The connection setup field definitions. Each integration will

            require different data to connect to the 3rd party app.'
          readOnly: true
        oAuthConfig:
          description: 'Field 8: Configuration parameters required for the OAuth setup flow. This

            field will be present only if the integration supports OAuth 2.0.'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/mgmt.v1beta.Integration.OAuthConfig'
        view:
          title: 'Field 9: View defines how the integration is presented. The following

            fields are only shown in the FULL view:

            - setupSchema

            - oAuthConfig'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/mgmt.v1beta.View'
      description: 'Integration contains the parameters to create a connection between

        components and 3rd party apps.'
    pipeline.v1beta.Integration.OAuthConfig:
      type: object
      properties:
        authUrl:
          type: string
          description: 'The URL of the OAuth server to initiate the authentication and

            authorization process.'
          readOnly: true
        accessUrl:
          type: string
          description: 'The URL of the OAuth server to exchange the authorization code for an

            access token.'
          readOnly: true
        scopes:
          type: array
          items:
            type: string
          description: 'A list of scopes that identify the resources that the connection will be

            able to access on the user''s behalf.'
          readOnly: true
      description: 'OAuthConfig contains the configuration parameters for fetching an access

        token via an OAuth 2.0 flow.'
    mgmt.v1beta.Integration.OAuthConfig:
      type: object
      properties:
        authUrl:
          type: string
          description: 'The URL of the OAuth server to initiate the authentication and

            authorization process.'
          readOnly: true
        accessUrl:
          type: string
          description: 'The URL of the OAuth server to exchange the authorization code for an

            access token.'
          readOnly: true
        scopes:
          type: array
          items:
            type: string
          description: 'A list of scopes that identify the resources that the connection will be

            able to access on the user''s behalf.'
          readOnly: true
      description: 'OAuthConfig contains the configuration parameters for fetching an access

        token via an OAuth 2.0 flow.'
    pipeline.v1beta.GetIntegrationResponse:
      type: object
      properties:
        integration:
          description: The requested integration.
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/pipeline.v1beta.Integration'
      description: GetIntegrationResponse contains the requested integration.
    pipeline.v1beta.Integration.Link:
      type: object
      properties:
        text:
          type: string
          description: Text contains the message to display.
          readOnly: true
        url:
          type: string
          description: URL contains the reference the link will redirect to.
          readOnly: true
      description: Link contains the information to display an reference to an external URL.
    pipeline.v1beta.ListIntegrationsResponse:
      type: object
      properties:
        integrations:
          type: array
          items:
            type: object
            $ref: '#/components/schemas/pipeline.v1beta.Integration'
          description: A list of integrations matching the request parameters.
          readOnly: true
        nextPageToken:
          type: string
          description: Next page token.
          readOnly: true
        totalSize:
          type: integer
          format: int32
          description: Total number of items.
          readOnly: true
      description: ListIntegrationsResponse contains a paginated list of integrations.
    pipeline.v1beta.View:
      type: string
      enum:
      - VIEW_BASIC
      - VIEW_FULL
      description: "View defines how a resource is presented. Most resources can share this view\ndefinition, the particular meaning of each value should be defined in the\nresource itself. Certain resources might have their own View definition if\nthey need to implement more than 2 (basic / full) views.\n\n - VIEW_BASIC: Default view.\n - VIEW_FULL: Full representation."
    mgmt.v1beta.View:
      type: string
      enum:
      - VIEW_BASIC
      - VIEW_FULL
      description: "View defines how a resource is presented. It can be used as a parameter in a\nmethod request to allow clients to select the amount of information they\nwant in the response.\n\n - VIEW_BASIC: Default view, only includes basic information.\n - VIEW_FULL: Full representation."
    mgmt.v1beta.GetIntegrationResponse:
      type: object
      properties:
        integration:
          description: The requested integration.
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/mgmt.v1beta.Integration'
      description: GetIntegrationResponse contains the requested integration.
    pipeline.v1beta.Integration:
      type: object
      properties:
        id:
          type: string
          description: 'Field 1: Identifier of the integration, which references a component

            definition. Components with that definition ID will be able to use the

            connections produced by this integration.'
          readOnly: true
        title:
          type: string
          description: 'Field 2: Title, reflects the app name.'
          readOnly: true
        description:
          type: string
          description: 'Field 3: Short description of the integrated app.'
          readOnly: true
        vendor:
          type: string
          description: 'Field 4: Integrated app vendor name.'
          readOnly: true
        icon:
          type: string
          description: 'Field 5: Integration icon. This is a path that''s relative to the root of

            the component implementation and that allows frontend applications to pull

            and locate the icons.

            See the `icon` field in the `ComponentDefinition` entity for more

            information.'
          readOnly: true
        helpLink:
          description: 'Field 6: Reference to the vendor''s documentation to expand the integration

            details.'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/pipeline.v1beta.Integration.Link'
        setupSchema:
          type: object
          description: 'Field 7: The connection setup field definitions. Each integration will

            require different data to connect to the 3rd party app.'
          readOnly: true
        oAuthConfig:
          description: 'Field 8: Configuration parameters required for the OAuth setup flow. This

            field will be present only if the integration supports OAuth 2.0.'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/pipeline.v1beta.Integration.OAuthConfig'
        view:
          title: 'Field 9: View defines how the integration is presented. The following

            fields are only shown in the FULL view:

            - setupSchema

            - oAuthConfig'
          readOnly: true
          allOf:
          - $ref: '#/components/schemas/pipeline.v1beta.View'
      description: 'Integration contains the parameters to create a connection between

        components and 3rd party apps.'
  securitySchemes:
    Bearer:
      type: apiKey
      description: Enter the token with the `Bearer ` prefix, e.g. `Bearer instill_sk_***`
      name: Authorization
      in: header
      x-default: Bearer instill_sk_***
externalDocs:
  description: More about Instill Core
  url: https://docs.instill-ai.com
x-refined-from:
- service.swagger.yaml
- instill-ai-openapi.yml