This is a html view of the json schema please take the json schema as reference DOWNLOAD THE JSON SCHEMA

Processing Feedback Event

Type: object

In Pilot
This event provides a standardized way to report processing issues or warnings encountered by consumer systems when handling various types of objects, such as accounts or facilities. It is designed to be extensible and applicable across different domains, enabling consistent feedback on event processing outcomes. By emitting this event, consumer systems can inform source systems of problems or anomalies in a structured, programmatically consumable format. This facilitates better traceability, error handling, and system-to-system communication throughout the processing pipeline.


Examples:

{
    "entityType": "ACCOUNT",
    "identifier": "ERP_ID_SINT011",
    "source": "SPARK",
    "severity": "ERROR",
    "messages": [
        {
            "code": "ACCOUNT_STATUS_CLOSED",
            "details": "Account ERP_ID_SINT011 is closed and cannot be modified"
        }
    ],
    "timestamp": "2025-06-10T14:22:00Z"
}

{
    "entityType": "ACCOUNT",
    "identifier": "ERP_ID_SINT012",
    "source": "SPARK",
    "severity": "WARNING",
    "messages": [
        {
            "code": "ADDRESS_CONFLICT",
            "details": "Address conflict detected for account ERP_ID_SINT012"
        },
        {
            "code": "BILLING_ADDRESS_NOT_FOUND",
            "details": "Billing address not found for account ERP_ID_SINT012"
        }
    ],
    "timestamp": "2025-07-15T09:45:30+02:00"
}

{
    "entityType": "ACCOUNT",
    "identifier": "ERP_ID_SINT013",
    "source": "SPARK",
    "severity": "ERROR",
    "messages": [
        {
            "code": "ACCOUNT_VALIDATION_FAILED",
            "details": "Account validation failed due to missing required fields"
        }
    ],
    "correlationsInfo": {
        "integrationPattern": "EVENT",
        "topic": "account",
        "partition": 0,
        "offset": 12345
    },
    "timestamp": "2025-08-20T18:10:05.123Z"
}

{
    "entityType": "CONTACT",
    "identifier": "user-12345",
    "source": "SPARK",
    "severity": "ERROR",
    "messages": [
        {
            "code": "CONTACT_VALIDATION_FAILED",
            "details": "Contact validation failed: email field is required"
        }
    ],
    "correlationsInfo": {
        "integrationPattern": "EVENT",
        "topic": "contacts",
        "partition": 2,
        "offset": 67890
    },
    "timestamp": "2025-10-22T11:30:45.123Z"
}

root entityType

Entity Type

Type: enum (of string)

Type of the entity related to this feedback event. This can be an account, contact, facility, or any other entity type that the system supports.

Must be one of:

  • "ACCOUNT"
  • "ADDRESS"
  • "CONTACT"

Examples:

"ACCOUNT"

"CONTACT"

root identifier
Type: string

Unique identifier of the object, like the accountId, the facilityId, etc.

Must match regular expression: ^[A-Za-z0-9_-]+$

Must be at least 1 characters long

Must be at most 100 characters long


Example:

"ERP_ID_SINT009"

root source

Source

Type: enum (of string)

Source of the feedback event, indicating where it originated from. This first version only supports SPARK as the source.

Must be one of:

  • "SPARK"

Example:

"SPARK"

root severity

Severity

Type: enum (of string)

Severity level of the feedback. where
- WARNING indicates a warning that does not block processing.
- ERROR indicates a critical issue that prevents further processing.

Must be one of:

  • "WARNING"
  • "ERROR"

Example:

"ERROR"

root messages
Type: array

List of structured messages providing additional context or information about the feedback event

Must contain a minimum of 1 items

Must contain a maximum of 10 items

No Additional Items

Each item of this array must be:

root messages Feedback Event Message

Feedback Event Message

Type: object

A structured message providing additional context or information about the feedback event

root messages Feedback Event Message code
Type: enum (of string)

Message code representing the type of error or warning encountered. Each code is mapped to a specific processing issue or anomaly, enabling standardized feedback for consumer systems. See documentation for business context and usage of each code.

Must be one of:

  • "INVALID_PARENT_STATE"
  • "FACILITY_NOT_FOUND"
  • "GUEST_ACCOUNT_ALREADY_EXISTS"
  • "ACCOUNT_CIRCULAR_HIERARCHY"
  • "ACCOUNT_STATUS_CLOSED"
  • "ADDRESS_CONFLICT"
  • "BILLING_ADDRESS_NOT_FOUND"
  • "ACCOUNT_VALIDATION_FAILED"
  • "ACCOUNT_TECHNICAL_FAILURE"
  • "ADDRESS_IDENTIFIER_MISSING"
  • "ADDRESS_IS_DEFAULT_FOR_ACCOUNT"
  • "ADDRESS_ALREADY_LINKED"
  • "ADDRESS_ACCOUNT_NOT_FOUND"
  • "ADDRESS_MISSING_ACCOUNT_DEFAULT"
  • "OVERRIDE_PARENT_ACCOUNT_BILLING_ADDRESS"
  • "ADDRESS_VALIDATION_FAILED"
  • "ADDRESS_TECHNICAL_FAILURE"
  • "ACCOUNT_TECHNICAL_FAILURE"
  • "CONTACT_INVALID_LOCALE"
  • "CONTACT_INVALID_PHONE_NUMBER"
  • "CONTACT_IAM_OPERATION_FAILURE"
  • "CONTACT_VALIDATION_FAILED"
  • "CONTACT_TECHNICAL_FAILURE"

Examples:

"INVALID_PARENT_STATE"

"CONTACT_VALIDATION_FAILED"

root messages Feedback Event Message details
Type: string

English detailed message providing context or information about the error or warning, not to be used for programmatic logic

Must be at least 1 characters long

Must be at most 1000 characters long


Example:

"Parent account ERP_ID_SINT009 not found in SPARK"

root correlationsInfo

Event Correlation Information

Type: object

root correlationsInfo integrationPattern
Type: enum (of string)

The integration pattern used for the event, indicating how it was published.

Must be one of:

  • "EVENT"

root correlationsInfo topic
Type: string

The topic to which the event was published to
Example:

"account"

root correlationsInfo partition
Type: integer

The partition within the topic to which the event was published to
Example:

0

root correlationsInfo offset
Type: integer

The offset within the partition to which the event was published to
Example:

123

root timestamp
Type: stringFormat: date-time

Date and time when the feedback event occurred, in ISO 8601 format

Must be at least 20 characters long

Must be at most 35 characters long


Examples:

"2025-05-08T21:44:32Z"

"2025-05-08T21:44:32.123Z"

"2025-12-01T10:30:15+02:00"

"2025-12-01T10:30:15.123+02:00"

"2025-05-08T21:44:32.123456789Z"

"2025-05-08T21:44:32.123456789+02:00"