Notification connectors store organization-scoped credentials for SMTP, Slack, Lark, and generic
webhook delivery. Creating, updating, testing, or deleting a connector requires alerts.manage.
Listing and reading connectors requires alerts.read.
List supported types
The response describes the capabilities of each connector type registered by the running backend.
Current types are email_smtp, slack_app, slack_webhook, lark_app, lark_webhook, and
webhook.
Create a connector
The API returns 201 Created. The response includes the connector ID, capabilities, status, test
metadata, and timestamps. Sensitive config fields are masked:
List and read connectors
MoleSignal encrypts the complete config object at rest. Responses mask passwords, secrets,
tokens, URLs, and header objects with ***.
Update a connector
connector_type is immutable after creation. Send an unchanged masked value as *** to keep the
stored secret, or replace the mask with a new plaintext value. Omit config to leave the whole
configuration unchanged.
Test a connector
The target must be compatible with the connector. A successful or failed test updates status,
last_tested_at, last_test_status, and last_test_error. A disabled connector cannot run a test.
Delete a connector
Successful deletion returns 204 No Content. If a user endpoint, notification policy, or fallback
route still references the connector, the API returns a conflict. Move all references before
deletion.
See Notification channels and delivery for provider config fields,
target types, and routing operations. Last modified on August 4, 2026