Skip to main content
GET
GET /connectors/providers does two jobs with one endpoint:
  • Without id, it returns the catalog of providers you can connect, in display order.
  • With id={provider}, it describes that one provider: the credentials it needs and the fields you can search and filter on.
Use a catalog entry’s provider value as provider in Create Connector, and as id to read that provider’s credential schema.

The catalog

Only providers you can connect are listed, so supported is always true. webhook_support is true for providers whose data arrives by webhook instead of scheduled syncs. rank is null for providers without a display position; they are listed last, alphabetically.

One provider

  • credential_schema is the JSON Schema for credentials on Create Connector and Update Connector. It is omitted when unavailable.
  • setup_guide, token_scopes and token_scopes_note appear for providers that need extra setup, such as creating a token with specific scopes.
  • indexed_object_types are the provider’s record types that become searchable.
  • searchable_fields are values written into each synced document’s text. Search finds them, but you cannot target one field on its own.
  • filterable_fields are exact-match filters. Each entry’s filter_key is where the value lives in metadata_filters.
A filter_key such as additional_metadata.container_id is written as a nested object in a query:
Filtering by a provider field
A filter_key with no prefix, such as connector_id, goes directly under metadata_filters. For Gmail, filter on account_email (additional_metadata.account_email) to scope results to one connected mailbox.

Errors

  • 404: with id, no provider has that id. Check it against the catalog.

Query Parameters

id
string

Provider name (e.g. slack, gmail). Omit to list all.

Example:

"HydraDoc1234"

Response

OK

providers
object[]

Providers you can connect, in catalog display order.

Example: