{
  "opencollection": "1.0.0",
  "info": {
    "name": "Kong Enterprise Admin ACLs Catalog Integrations API",
    "version": "3.14.0"
  },
  "request": {
    "auth": {
      "type": "apikey",
      "key": "Kong-Admin-Token",
      "value": "{{Kong-Admin-Token}}",
      "placement": "header"
    }
  },
  "items": [
    {
      "info": {
        "name": "Catalog Integrations",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "List Integrations",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "{protocol}://{hostname}:{port}{path}/v1/integrations",
            "params": [
              {
                "name": "page[size]",
                "value": "",
                "type": "query",
                "description": "The maximum number of items to include per page. The last page of a collection may include fewer items."
              },
              {
                "name": "page[number]",
                "value": "",
                "type": "query",
                "description": "Determines which page of the entities to retrieve."
              },
              {
                "name": "filter",
                "value": "",
                "type": "query",
                "description": "Filters a collection of integrations."
              },
              {
                "name": "sort",
                "value": "",
                "type": "query",
                "description": "Sorts a collection of integrations. Supported sort attributes are:\n  - `display_name`\n  - `name`\n\nDefault sort is `display_name` in ascending order.\n"
              }
            ]
          },
          "docs": "Returns a paginated collection of all catalog integrations available to connect.\nEach integration represents a built-in connector that extends the platform's capabilities;\nenabling discovery, resource management, event ingestion, and more.\nIntegrations expose metadata that describes how they authenticate, what configuration they\nrequire, and how they interact with catalog entities like Resources and Services.\n\nCurrently, integrations are platform-defined and cannot be extend or registered by cus"
        }
      ]
    }
  ],
  "bundled": true
}