---
title: "The creator connected an installation with their credentials; the connector can act for the project now."
method: POST
path: "connector.connected"
tags: ["connector.* events"]
---

# The creator connected an installation with their credentials; the connector can act for the project now.

`POST connector.connected` (webhook)

### When this fires

A creator completes a connector's connect flow on the dashboard: the connector checks the credentials, registers with its platform and the installation turns `connected`. For the first connector this is the **Connect Bot** modal, the platform bot's connectivity conversation and a Disaster Recovery bot replacement.

### Caveats

- Credentials are never in the payload. Read the installation back with [the installation endpoint](https://docs.subscriby.net/api/v1/reference/connectors).
- Reconnecting with new credentials fires this again for the same `installation_id`.

### Related events

- `connector.installed`: the pending row that preceded it, when the connector installs in two steps.
- `connector.status_changed`: the installation's health afterwards.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'connector.connected', required: The event name, always `connector.connected` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `connector` string, required: The connector key.
    - `installation_id` string, uuid, required: The installation row.
    - `project_id` string, uuid, required: Mirrors top-level `project_id`.
    - `display_name` string, nullable, required: The platform's display name for the installation (the bot's name).
    - `handle` string, nullable, required: The platform's handle for the installation (the bot's username), without a leading `@`.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)