GET
/
connector-config
/
{id}
curl --request GET \
  --url https://api.openint.dev/v1/connector-config/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "<string>",
  "created_at": "<string>",
  "updated_at": "<string>",
  "org_id": "<string>",
  "display_name": "<string>",
  "disabled": true,
  "metadata": {},
  "connector_name": "<string>",
  "config": {
    "oauth": {
      "client_id": "<string>",
      "client_secret": "<string>",
      "scopes": [
        "<string>"
      ],
      "redirect_uri": "<string>"
    }
  },
  "connector": {
    "name": "<string>",
    "display_name": "<string>",
    "logo_url": "<string>",
    "stage": "alpha",
    "platforms": [
      "web"
    ],
    "schemas": {
      "connector_config": "<any>",
      "connection_settings": "<any>",
      "integration_data": "<any>",
      "webhook_input": "<any>",
      "pre_connect_input": "<any>",
      "connect_input": "<any>",
      "connect_output": "<any>"
    },
    "authType": "BASIC",
    "openint_scopes": [
      "<string>"
    ],
    "scopes": [
      {
        "scope": "<string>",
        "display_name": "<string>",
        "description": "<string>"
      }
    ]
  },
  "integrations": {},
  "connection_count": 123
}

Authorizations

Authorization
string
header
required

Organization API key generated in the OpenInt Console and passed in the authorization header with format: Bearer {apiKey}

Path Parameters

id
string
required

The id of the connector config, starts with ccfg_

Query Parameters

expand
enum<string>[]

Fields to expand: connector (includes connector details), enabled_integrations (includes enabled integrations details)

Available options:
connector,
connector.schemas,
connection_count

Response

200
application/json
Successful response

Connector specific data

id
string
required
created_at
string
required
updated_at
string
required
org_id
string
required
display_name
string | null
required
disabled
boolean | null
required
connector_name
string
required
Allowed value: "acme-oauth2"
config
object
required
metadata
object | null

JSON object can can be used to associate arbitrary metadata to avoid needing a separate 1-1 table just for simple key values in your application. During updates this object will be shallowly merged

connector
object
integrations
object
connection_count
number