A subscriber message object description.
This integration follows the EVENT/COMMAND pattern. The OpCo is considered as the owner of the SoR (system of records), therefore sending EVENTS. All other systems are considered as SoE (systems of engagement) and send COMMANDS.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"OPCO"
The event message header providing metadata details.
No Additional PropertiesIf the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"OPCO"
"EVENT"
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"SPARK"
"COMMAND"
The source entity of this event
"OPCO"
The version of the json event format
Must be at least 1 characters long
"v1"
COMMAND to request a change on masterEVENT from master to publish a change"EVENT"
The type of the document
"SUBSCRIBER"
The target, consumer of the request
"OPCO"
This object is used if errors are raised by the master (OpCO) receiving a COMMAND. This entity should be included in the response EVENT, if the case.
No Additional Properties{
"code": "SUBSCRIBER_NOT_FOUND",
"message": "The subscriber was not found"
}
The error code
"SUBSCRIBER_NOT_FOUND"
A message describing the error
Must be at least 1 characters long
"The subscriber was not found"
This object contains the actual data of the subscriber event
No Additional PropertiesIf the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
true
The email address of the subscriber
Must be at least 1 characters long
"test@gmail.com"
The account identifier of the subscriber
Must be at least 1 characters long
"123456"
Name of the subscriber:
last name in case of individualdepartment/service name otherwiseMust be at least 1 characters long
"Doe"
First name of the subscriber
Must be at least 1 characters long
"John"
Middle name of the subscriber
Must be at least 1 characters long
"Doe"
Flag to indicate if the subscriber is an individual or a service/department.
If true, the name field is used as last name.
If omitted, the subscriber is considered as an individual (true)
true
ContactId if it is a known user
Must be at least 1 characters long
"123456"
The status of the subscriber.
- PENDING for creation and modification
- ACTIVE if the subscriber is active
- DELETED if the subscriber is to be deleted
"ACTIVE"
The list of subscription codes to add to the subscriber
No Additional ItemsMust be at least 1 characters long
[
"INVOICE_NOTIFICATION"
]
[
"INVOICE_NOTIFICATION",
"PAYMENT_REMINDER",
"ACCOUNT_UPDATE"
]
The list of subscription codes to remove from the subscriber
No Additional ItemsMust be at least 1 characters long
[
"INVOICE_NOTIFICATION"
]
The date of the last modification of the subscriber
"2025-02-23T08:30:22.804Z"