/v1/mgmt/connectorAuthorization
Descope Project ID and Management Key Project ID:Management Key as bearer token.
In: header
Query Parameters
Required. The connector id, as CreateConnector and LoadAllConnectors return it; ids starting with MP are
messaging providers.
Delete a single connector by id, using a valid management key. Flows that use the connector fail at that step until they are changed.
curl -X DELETE "https://api.descope.com/v1/mgmt/connector?id=string"Create connector POST
Create a connector from a template, using a valid management key. `type` is the template id from LoadAllConnectorTemplates, and `configuration` holds the template's fields by name as GetConnectorTemplate describes them. The server checks the configuration against the template before saving it: required fields must be set, values must match their field's type, allowed options and dependencies, unknown fields are rejected, and missing fields with a default are filled in. Returns the stored connector, with secret values as `PLACEHOLDER_VALUE` and defaults filled in. Messaging provider types such as `sendgrid`, except `smtp`, are stored as messaging providers with ids starting with `MP` and are not checked, since they have no template. A connector does nothing by itself; the template's `types` says how it is used: a `flows` connector is called from a flow by the `connector` action with the connector's id (agents on the Descope MCP find it with GetActionCatalog, query `connector`), or automatically on events when the template has auto-trigger settings and they are on, and an `audit` connector streams audit events while its `auditEnabled` configuration field is true (the default), or always when the template has no such field.
Get connector template GET
Get one connector template by id, using a valid management key, with its configuration fields: each field's name, type, whether it is required, its default value, its allowed values, the field it depends on, and its documentation. Build the `configuration` for CreateConnector from these fields; the server checks it against them. Secret values come from the user: don't invent them unless the user asks for a placeholder. An `httpAuth` value is an object with `method` and that method's settings: `none`; `bearerToken` with `bearerToken`; `apiKey` with `apiKey: {key, token}`; `basic` with `basic: {username, password}`; `oauth2ClientCredentials` with `oauth2ClientCredentials: {clientId, clientSecret, authUrl, authStyle}`, all required, where `authStyle` is `body` or `header` with no default, plus optional `scopes` as one space-separated string. A `secret-object` value is a list of `{key, value, secret}` entries; `secret` defaults to false, and a secret entry is read back as `PLACEHOLDER_VALUE` with `secret: true`. Leave out fields of type `cloudformation-link`, a console-only link, and `readonly-string`, which Descope generates on create and cannot be changed; give the generated value from the returned connector to the user, such as an AWS external ID to put in the IAM role's trust policy. Returns not found for unknown templates.