# datarequest.report_error

Triggered when an error occurred during generating report for a Data Request

### Reason Codes

|Reason Code|Description|
|--- |--- |
|UNSUPPORTED_FORMAT| The report could not be generated as the following items are of unsupported format.
|UNPROCESSABLE_DOCUMENT_QUALITY| The report could not be generated as the following items are unprocessable.
|PARTIAL_DOCUMENT| The report could not be generated as the following items are partial.
|NO_ITEMS| The report could not be generated as there are no items for this Individual.


Endpoint: POST datarequest.report_error
Version: 3.0
Security: Bearer, Basic, Internal, None

## Request fields (application/json):

  - `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"

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

  - `service_context_id` (string)
    Unique ID of the service context identified by MeasureOne
    Example: "trx_SEne2SSjP3GvpVrs5HLol4xor2"

  - `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"

  - `metadata` (object)
    metadata can be used for storing additional information in a structured format.
    Example: {"report_id":"REPORT"}

  - `reason_codes` (array)
    List of reason codes. Helps developer understand what error occurred during report generation.
    Example: [{"code":"UNSUPPORTED_FORMAT","description":"The report could not be generated as the following items are of unsupported format.","context":{"items":["itm_Cevp4JweIsEeNjpgAAjy2EZt3R","itm_2QE8ZMulsMal2OYaDAMxD0cQN4o"]}}]

  - `reason_codes.code` (string)
    Reason code applicable

  - `reason_codes.description` (string)
    Description providing details to understand what error occurred during report generation.

  - `reason_codes.context` (object)
    Context to understand where the reason code is applicable

  - `reason_codes.context.items` (array)
    List of Items where the reason code is applicable

  - `event` (string)
    Name of the event
    Example: "datarequest.report_error"

  - `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

  - `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.

  - `transaction_id` (string)
    Unique ID of the Transaction identified by MeasureOne
    Example: "trx_TSEne2SSjP3GvpVrs5HLol4xor2"