---
title: "Create a Knowledge Connector"
method: POST
path: "/v2.0/knowledgestores/{knowledgeStoreId}/connectors"
tags: ["Knowledge Connectors"]
---

# Create a Knowledge Connector

`POST /v2.0/knowledgestores/{knowledgeStoreId}/connectors`

Creates a Knowledge Connector.

## Path parameters

- `knowledgeStoreId` string, required

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Request body

- object
  - `extension` string — The name of the extension
  - `version` string — The version of extension identifier
  - `type` string — The Knowledge Connector type identifier within an extension
  - `config` object — The configuration of the KnowledgeConnector
  - `name` string — The name of the KnowledgeConnector
  - `schedule` object
    - `enabled` boolean — If scheduled execution is enabled or not
    - `hour` number — Hour to start the scheduled execution, in UTC, set 0 or any value if schedule is disabled
    - `minute` number — Minute to start the scheduled execution, in UTC, set 0 or any value if schedule is disabled
    - `weekDays` number[] — Repeat x days of the week, Sunday = 0 ... Saturday = 6

## Response `201`

Returns KnowledgeSource metadata object.

- object — The IEntityMeta defines meta information every entity within the system has. These are dates when a resource was created and modified as well as information about the user who initially created a resource and who modified it the last time.
  - `extension` string — The name of the extension
  - `version` string — The version of extension identifier
  - `type` string — The Knowledge Connector type identifier within an extension
  - `config` object — The configuration of the KnowledgeConnector
  - `name` string — The name of the KnowledgeConnector
  - `schedule` object
    - `enabled` boolean — If scheduled execution is enabled or not
    - `start` integer — Start date and time to calculate scheduled execution, set internally
    - `totalMinutes` number — Total minutes for the scheduled execution, set internally
    - `hour` number — Hour to start the scheduled execution, in UTC, set 0 or any value if schedule is disabled
    - `minute` number — Minute to start the scheduled execution, in UTC, set 0 or any value if schedule is disabled
    - `timezone` string — Timezone for the scheduled execution in UTC, set internally
    - `weekDays` number[] — Repeat x days of the week, Sunday = 0 ... Saturday = 6
  - `lastExecution` integer — Unix-timestamp when the last execution was triggered or null if never executed
  - `lastExecutionStatus` 'none' | 'queued' | 'active' | 'done' | 'error' — Last execution status of the KnowledgeConnector
  - `_id` string
  - `createdAt` integer — Unix-timestamp
  - `lastChanged` integer — Unix-timestamp
  - `createdBy` string
  - `lastChangedBy` string

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.dev/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.dev/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/revisions/85b2872bdfb7/schema)