This object describe a user request
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.
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.
"WARRANTY"
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.
"CLAIM"
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.
"WARRANTY"
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.
"CLAIM"
This object is used to describe some technical meta information related to the event
The application source of this event
The version of the json format event
Type of the request.
"NEW_CUSTOMER_ONBOARDING"
This object is used to describe a warranty request.
This object is used to describe the header of the warranty header.
No Additional PropertiesThe unique identifier of the requested as generated by the master system.
Must be at least 1 characters long
"123456789"
The claim or warranty unique identifier as generated by the OpCo system
Must be at least 1 characters long
"123456789"
Is meant to be either the date requested by the customer for pickup or drop off to the branch for a return or requested by the OpCo for a reverse logistic.
"2023-10-01"
Contains the logistic 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.
"DROP_OFF"
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.
"PICK_UP"
This is the selected logistic method for the request.
- DROP_OFF when the customer is dropping off the product at a facility.
- PICK_UP when the customer is requesting a pickup from a specific address.
The facility id used for drop off.
Must be at least 1 characters long
"1234567"
The address used for pickup.
No Additional PropertiesOpCo internal system's unique identifier for the address.
Must be at least 1 characters long
"237564557868778"
The first line of the address. Should contain Street name, no, street type. Usually the whole address can fit on one line.
Must be at least 1 characters long
"235 Donaghy Ave"
The second line of the address. Should complete the address with other details (e.g. floor number)
Must be at least 1 characters long
"1st floor"
The third line of the address. Should complete the address with other information. e.g. Apartment no
Must be at least 1 characters long
"Apt 1"
The postal code
Must be at least 1 characters long
"V7P 1E2"
The city in which the street address is, and which is in the adminDevison(region)
Must be at least 1 characters long
"North Vancouver"
The region in which the locality is, and which is in the country.
Must be at least 1 characters long
"BC"
The department in which the locality is, and which is in the country.
Must be at least 1 characters long
"BC"
The ISO 3166-1 alpha-3 of the country
Must be at least 3 characters long
Must be at most 3 characters long
"CAN"
The unique identifier of the return as generated by the master system.
Must be at least 1 characters long
"123456789"
Contact information of the facility.
No Additional PropertiesPhone number of the contact.
Must be at least 1 characters long
"+12345678910"
The email of the contact. This is the identifier of the user on spark
"user@domain.com"
The fax number of the contact.
Must be at least 1 characters long
"+12345678910"
The list of contributors to the logistic issue.
Must contain a minimum of 1 items
[
{
"fullName": "John Smith",
"email": "john.smith@mycompany.com"
},
{
"fullName": "John Validator",
"email": "john.validator@mycompany.com"
}
]
The full name of a contributor.
Must be at least 1 characters long
"John Smith"
The email of a contributor. This is the identifier of the user on spark
"john.smith@mycompany.com"
The phone number of a contributor.
Must be at least 1 characters long
"+1234567890"
Indicates if the contributor is the creator of the return request.
true
Array containing the details per each line.
Must contain a minimum of 1 items
The line of the logistic issue.
No Additional PropertiesThe unique identifier of the sales order, as defined by the sales-order universal feed schema.
Must be at least 1 characters long
"1234567"
The unique identifier of the sales order line, as defined by the sales-order universal feed schema.
Must be at least 1 characters long
"1234567"
The unique identifier of the billing.
Must be at least 1 characters long
"1234567"
The unique identifier of the billing line.
Must be at least 1 characters long
"1234567"
The product subject to this request.
No Additional PropertiesThe unique identifier of the product.
Must be at least 1 characters long
"1234567"
The name of the product.
Must be at least 1 characters long
"Product Name"
The name of the brand.
Must be at least 1 characters long
"Brand Name"
From the list of reasons configured for the OpCo.
Must be at least 1 characters long
"DEFECTIVE_ITEM"
The list of images of the product.
No Additional ItemsThe image of the product.
No Additional PropertiesThe name of the image.
Must be at least 1 characters long
"Image Name"
The URL of the image.
"https://example.com/image.jpg"
A comment related to the product.
Must be at least 1 characters long
"Product Comment"
Any additional information related to the product
No Additional ItemsA free key value pair field to add any details about the product
The name or identifier for the additional information
{
"en-GB": "Diameter",
"fr-FR": "Diamètre"
}
Each additional property must conform to the following schema
Type: stringThe value for the named additional information
{
"en-GB": "1.2 m",
"fr-FR": "1.2 mètre"
}
Each additional property must conform to the following schema
Type: stringThe status of the logistic issue line.
- REQUESTED when the return is requested by the customer.
- RETURNED when the line item is returned in full by the customer.
- DELETED when the line item is to be deleted
"COMPLETE"
The requested quantity.
Value must be greater or equal to 0
10
The unique identifier of the shipment associated with the return line item.
Must be at least 1 characters long
"1234567"
This object is used to describe a warranty request.
This object is used to describe the header of the warranty header.
No Additional PropertiesThe unique identifier of the requested as generated by the master system.
Must be at least 1 characters long
"123456789"
The claim or warranty unique identifier as generated by the OpCo system
Must be at least 1 characters long
"123456789"
Is meant to be either the date requested by the customer for pickup or drop off to the branch for a return or requested by the OpCo for a reverse logistic.
"2023-10-01"
Contains the logistic 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.
"DROP_OFF"
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.
"PICK_UP"
This is the selected logistic method for the request.
- DROP_OFF when the customer is dropping off the product at a facility.
- PICK_UP when the customer is requesting a pickup from a specific address.
The facility id used for drop off.
Must be at least 1 characters long
"1234567"
The address used for pickup.
No Additional PropertiesOpCo internal system's unique identifier for the address.
Must be at least 1 characters long
"237564557868778"
The first line of the address. Should contain Street name, no, street type. Usually the whole address can fit on one line.
Must be at least 1 characters long
"235 Donaghy Ave"
The second line of the address. Should complete the address with other details (e.g. floor number)
Must be at least 1 characters long
"1st floor"
The third line of the address. Should complete the address with other information. e.g. Apartment no
Must be at least 1 characters long
"Apt 1"
The postal code
Must be at least 1 characters long
"V7P 1E2"
The city in which the street address is, and which is in the adminDevison(region)
Must be at least 1 characters long
"North Vancouver"
The region in which the locality is, and which is in the country.
Must be at least 1 characters long
"BC"
The department in which the locality is, and which is in the country.
Must be at least 1 characters long
"BC"
The ISO 3166-1 alpha-3 of the country
Must be at least 3 characters long
Must be at most 3 characters long
"CAN"
The unique identifier of the return as generated by the master system.
Must be at least 1 characters long
"123456789"
Contact information of the facility.
No Additional PropertiesPhone number of the contact.
Must be at least 1 characters long
"+12345678910"
The email of the contact. This is the identifier of the user on spark
"user@domain.com"
The fax number of the contact.
Must be at least 1 characters long
"+12345678910"
The list of contributors to the logistic issue.
Must contain a minimum of 1 items
[
{
"fullName": "John Smith",
"email": "john.smith@mycompany.com"
},
{
"fullName": "John Validator",
"email": "john.validator@mycompany.com"
}
]
The full name of a contributor.
Must be at least 1 characters long
"John Smith"
The email of a contributor. This is the identifier of the user on spark
"john.smith@mycompany.com"
The phone number of a contributor.
Must be at least 1 characters long
"+1234567890"
Indicates if the contributor is the creator of the return request.
true
Array containing the details per each line.
Must contain a minimum of 1 items
The line of the logistic issue.
No Additional PropertiesThe unique identifier of the sales order, as defined by the sales-order universal feed schema.
Must be at least 1 characters long
"1234567"
The unique identifier of the sales order line, as defined by the sales-order universal feed schema.
Must be at least 1 characters long
"1234567"
The unique identifier of the billing.
Must be at least 1 characters long
"1234567"
The unique identifier of the billing line.
Must be at least 1 characters long
"1234567"
The product subject to this request.
No Additional PropertiesThe unique identifier of the product.
Must be at least 1 characters long
"1234567"
The name of the product.
Must be at least 1 characters long
"Product Name"
The name of the brand.
Must be at least 1 characters long
"Brand Name"
From the list of reasons configured for the OpCo.
Must be at least 1 characters long
"DEFECTIVE_ITEM"
The list of images of the product.
No Additional ItemsThe image of the product.
No Additional PropertiesThe name of the image.
Must be at least 1 characters long
"Image Name"
The URL of the image.
"https://example.com/image.jpg"
A comment related to the product.
Must be at least 1 characters long
"Product Comment"
Any additional information related to the product
No Additional ItemsA free key value pair field to add any details about the product
The name or identifier for the additional information
{
"en-GB": "Diameter",
"fr-FR": "Diamètre"
}
Each additional property must conform to the following schema
Type: stringThe value for the named additional information
{
"en-GB": "1.2 m",
"fr-FR": "1.2 mètre"
}
Each additional property must conform to the following schema
Type: stringThe status of the logistic issue line.
- REQUESTED when the return is requested by the customer.
- RETURNED when the line item is returned in full by the customer.
- DELETED when the line item is to be deleted
"COMPLETE"
The requested quantity.
Value must be greater or equal to 0
10
The unique identifier of the shipment associated with the return line item.
Must be at least 1 characters long
"1234567"
User's email.
"geert@electracontractors.be"
User's title.
"Dhr."
User's firstname.
"Geert"
User's lastname.
"Corijn"
User's middle name.
"Van"
OpCo's organizatinal customer number that uniquely identifies its account. In the case of OpCo organised with a regional model or commercial organisation this should be suffix by '{orgId}'. if the accountId is 13563 and the orgId is OVIA so this field should contains 13563OVIA
Must be at least 1 characters long
"1234567"
"1234567_OVIA"
VAT number or Siret number.
Must be at least 1 characters long
"GM4837192941"
Name of the organizational customer.
Must be at least 1 characters long
"Independent Electric"
Optional field, needed by OpCo organised with a regional model or commercial organisation. It can be used to filter or route based on the orgId.
Must be at least 1 characters long
"org123"
"SNE"
Must contains the information about the formId setup in CMS if the requestType is equals to MARKETINGFORM. SPARK will use the predefined key FORMID, example: FORM_ID = MARKETING-EVENT-1-REGISTRATION
No Additional ItemsObject representing an additional information of the request.
No Additional PropertiesName of the additional information
Must be at least 1 characters long
"message"
"companyName"
Value of the additional information
Must be at least 1 characters long
"Super Elec"
The sales representative information.
No Additional Propertiesfirstname of the sale representative
Must be at least 1 characters long
"John"
lastname of the sale representative
Must be at least 1 characters long
"Doe"
phone number of the sale representative
Must be at least 1 characters long
"0683906389"
email of the sale representative
Must be at least 1 characters long
"john.doe@standelec.com"