# datasource.connected

Triggered when a successful connection with the Datasource is established

Endpoint: POST datasource.connected
Version: 3.0
Security: Bearer, Basic, Internal, None

## Request fields (application/json):

  - `datasource_id` (string)
    Unique ID of the Datasource identified by MeasureOne
    Example: "sch_CV8e5Lsvv2S8Wjz9Bpwpr8lm9Ay"

  - `individual_id` (string)
    Unique ID of the Individual identified by MeasureOne
    Example: "idv_Cevp4Jw9CIsEeNjpgAAjy2EZt3R"

  - `datarequest_id` (string)
    Unique ID of the Data Request identified by MeasureOne
    Example: "dr_TSEne2SSjP3GvpVrs5HLol4xor2"

  - `connection_id` (string)
    Unique ID of the connection with the Datasource
    Example: "cn_TSEne2SSjP3GvpVrs5HLol4xor2"

  - `external_id` (string)
    Your identifier for the Individual
    Example: "ABCDECD"

  - `session_id` (string)
    MeasureOne's Unique ID of the session for which the Individual connected their account
    Example: "tls_1fGYo0n2ggSN7iROJNkvxFDkovE"

  - `checkcodes_created` (any)
    A flag to identify if checkcodes are available for given session
    Example: true

  - `event` (string)
    Name of the event
    Example: "datasource.connected"

  - `is_refresh` (boolean)
    A flag to identify if event trigger due to a scheduled auto refresh

  - `refresh_id` (string)
    Unique ID of a scheduled refresh identified by MeasureOne
    Example: "rfs_1234ks2lkdw4i4j2li342podjslru"

  - `monitor_events` (array)
    Present only when the webhook is triggered by an Event Based Refresh session. Contains the subscribed monitoring event(s) that caused this notification to be delivered. Each object includes the event type, the customer-provided event name, and event-specific context.

  - `monitor_events.event` (string)
    The monitoring event type that was triggered during the refresh session.
    Enum: "NEW_ITEMS", "REPORT_CHANGED", "NO_ITEMS"

  - `monitor_events.name` (string)
    The customer-provided label for this event subscription, as specified in the refresh_policy.schedule.events configuration. Useful for mapping triggered events back to specific subscriptions.

  - `monitor_events.context` (any)
    Event-specific context containing details about what triggered the event. The structure varies by event type.