# datarequest.report_update_available Triggered when some data is updated or added in the report update for a Data Request. Once a complete report is available then datarequest.report_complete webhook will trigger. Endpoint: POST datarequest.report_update_available Version: 3.0 Security: Bearer, Basic, Internal, None ## Request fields (application/json): - `datarequest_id` (string) Unique ID of the Data Request identified by MeasureOne Example: "dr_TSEne2SSjP3GvpVrs5HLol4xor2" - `individual_id` (string) Unique ID of the Individual identified by MeasureOne Example: "idv_TSEne2SSjP3GvpVrs5HLol4xor2" - `service_context_id` (string) Unique ID of the service context identified by MeasureOne Example: "trx_SEne2SSjP3GvpVrs5HLol4xor2" - `external_id` (string) Your identifier for the Individual Example: "ABCDECD" - `report_uri` (string) The type of the report. Enum: "m1_report://EMPLOYMENT_SUMMARY", "m1_report://INCOME_SUMMARY", "m1_report://INCOME_EMPLOYMENT_DETAILS", "m1_report://INSURANCE_DETAILS", "m1_report://INSURANCE_STATUS", "m1_report://ACADEMIC_SUMMARY", "m1_report://ENROLLMENT_STATUS", "m1_report://REALIZED_GAINS" - `event` (string) Name of the event Example: "datarequest.report_update_available" - `is_refresh` (boolean) A flag to identify if event trigger due to a scheduled auto refresh Example: true - `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. - `metadata` (object) metadata can be used for storing additional information in a structured format. Example: {"report_id":"REPORT"} - `transaction_id` (string) Unique ID of the Transaction identified by MeasureOne Example: "trx_TSEne2SSjP3GvpVrs5HLol4xor2"