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

# List Connector Providers

> List every connector provider available to the authenticated organization.

Call `GET /connectors/providers` without an `id` query parameter to retrieve the catalog of connectable providers.

<RequestExample>
  ```bash cURL theme={"dark"}
  curl 'https://api.hydradb.com/connectors/providers' \
    -H "Authorization: Bearer $HYDRA_DB_API_KEY" \
    -H "API-Version: 2"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={"dark"}
  {
    "providers": [
      {
        "provider": "slack",
        "category": "Communication",
        "supported": true,
        "moveit_support": false,
        "is_alpha": false,
        "is_beta": false,
        "rank": 1
      }
    ]
  }
  ```
</ResponseExample>

| Property               | Meaning                                                                                                          |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `provider`             | Provider identifier. Use this value as `id` to get provider details and as `provider` when creating a connector. |
| `category`             | Display grouping for the provider.                                                                               |
| `supported`            | Whether the provider can be connected today.                                                                     |
| `moveit_support`       | Whether the provider syncs through the MOVEIT pipeline.                                                          |
| `is_alpha` / `is_beta` | Connector maturity flags.                                                                                        |
| `rank`                 | Catalog display order; lower ranks appear first.                                                                 |

## Related Resources

* [Get Connector Provider](/api-reference/v2/endpoint/get-connector-provider)  -  retrieve fields and credentials for one provider
* [Create Connector](/api-reference/v2/endpoint/create-connector)


## OpenAPI

````yaml api-reference/v2/openapi.json GET /connectors/providers
openapi: 3.1.0
info:
  contact:
    email: support@hydradb.com
    name: HydraDB Support
  description: >-
    HydraDB Application API — knowledge ingestion, search, and memory
    management.
  license:
    name: Proprietary
  title: HydraDB Application API
  version: 0.1.0
servers:
  - description: Production server
    url: https://api.hydradb.com
security: []
externalDocs:
  description: ''
  url: ''
paths:
  /connectors/providers:
    get:
      tags:
        - connectors
      summary: List supported providers, or describe one in detail
      description: >-
        Without ?id: returns every supported connector with its availability,
        maturity, category, and sync engine (the connector catalog). With
        ?id=<provider>: returns what that provider stores and how to use it —
        indexed_object_types (the streams that become searchable documents),
        searchable_fields (rendered into the indexed text), filterable_fields
        (each with the exact filter_key to pass in a query's metadata_filters),
        the credential_schema for connecting it, and setup_guide (present for
        providers whose configuration goes beyond the credential schema — e.g.
        bigquery's per-table cursor/change-history settings and the one-time
        ALTER statement they may require).
      parameters:
        - description: Provider name (e.g. slack, gmail). Omit to list all.
          in: query
          name: id
          schema:
            example: HydraDoc1234
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                additionalProperties: {}
                type: object
          description: OK
        '404':
          content:
            application/json:
              schema:
                additionalProperties: {}
                type: object
          description: Not Found

````