> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/connector-types

List all available connector types

` GET /v1/connector-types `

List all available connector types

## Responses

### ` 200 ` — OK

Content type: ` application/json `

- ` value `: type ` object `

  - ` code `: type ` integer `

    - example: ` 200 `

  - ` data `: type ` array `

    - ` array item `: type ` object `

      - ` categories `: type ` array ` — Deprecated: use Tags instead

        - ` array item `: type ` string `

      - ` dataSchema `: type ` object `

      - ` defaultOnly `: type ` boolean ` — DefaultOnly indicates that this connector type is managed entirely by the platform. Users cannot create their own connector instances; actions always use platform credentials.

      - ` description `: type ` string `

      - ` inboundWebhookPlatform `: type ` string ` — InboundWebhookPlatform names this connector's org-scoped inbound webhook route (/v1/orgs/{orgId}/integrations/{platform}). Set it only for providers whose webhook the user must register by hand — the UI shows the URL at connector-setup time so there is no chicken-and-egg with publishing. Providers we auto-provision (Telegram, Stripe, Shopify, …) leave it empty.

      - ` informationUrl `: type ` string `

      - ` logoDomain `: type ` string ` — Domain for logo.dev (e.g., "slack.com")

      - ` logoUrl `: type ` string ` — Computed at runtime from LogoDomain

      - ` name `: type ` string `

      - ` optional `: type ` boolean ` — Optional indicates if the connector can be omitted when required by an action. If true, workflow nodes can have a null connector and the action will execute without connector data (b3os-actions handles fallback if needed).

      - ` provider `: type ` string ` — Provider indicates the underlying provider for this connector. For Pipedream connectors, this is "pipedream".

      - ` providerConfig `: type ` object ` — ProviderConfig contains provider-specific configuration. For Pipedream connectors, this includes appSlug, authPropName, authType.

      - ` setupGuide `: type ` string ` — SetupGuide contains markdown instructions for setting up the connector.

      - ` tags `: type ` array ` — Tags for filtering and categorization

        - ` array item `: type ` string `

      - ` type `: type ` string `

  - ` message `: type ` string `

    - example: ` "success" `

  - ` requestId `: type ` string `

    - example: ` "abc-123" `

## Request examples

### cURL

```curl
curl -X GET 'https://api.example.com/v1/connector-types' \
  -H 'Authorization: Bearer YOUR_API_TOKEN'
```

### JavaScript

```javascript
const response = await fetch('https://api.example.com/v1/connector-types', {
  method: 'GET',
  headers: {
      "Authorization": "Bearer YOUR_API_TOKEN"
  }
});

const data = await response.json();
console.log(data);
```

### Python

```python
import requests

headers = {
    'Authorization': 'Bearer YOUR_API_TOKEN'
}

response = requests.get('https://api.example.com/v1/connector-types', headers=headers)
print(response.json())
```

### Go

```go
package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.example.com/v1/connector-types", nil)
	req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")

	resp, _ := http.DefaultClient.Do(req)
	defer resp.Body.Close()
	result, _ := io.ReadAll(resp.Body)
	fmt.Println(string(result))
}
```