Skip to Content
OpenETL
ReferenceAPIConnector Service

Get catalog package

A package with its roles' config fields, from its highest version's descriptor, which the first call fetches.

GET
/v1/catalog/{catalog}/*/{*}

A package with its roles' config fields, from its highest version's descriptor, which the first call fetches.

Path Parameters

catalog*string

The catalog id.

**string

The * id.

Response Body

OK

application/json
  1. response
package?

CatalogPackage is a package as its source's index or releases describe it: what its publisher says, until it's applied.

roles?array<>
Example Request
curl -X GET 'http://localhost:8080/v1/catalog/string/*/string'
Example Response
{  "package": {    "name": "string",    "source": "string",    "package": "string",    "title": "string",    "version": "string",    "author": "string",    "description": "string",    "license": "string",    "repository": "string",    "docs": "string",    "roles": [      "string"    ],    "tags": [      "string"    ],    "logo": "string",    "reference": "string",    "official": true,    "impostor": true,    "appliedVersion": "string",    "manual": true,    "updateAvailable": true  },  "roles": [    {      "role": "string",      "config": [        {          "name": "string",          "type": "string",          "title": "string",          "description": "string",          "required": true,          "secret": true        }      ]    }  ]}

List catalog GET

Each package of every connected source, at its highest version, as its source last listed it, and each package the org applied that no source lists, at its highest applied version.

Refresh catalog POST

Lists every connected source now, as the control plane does every 15 minutes.