ScalepointDeveloper Portal

Damage Service Report Event [Deprecated]

Integration point URL

  • URL: <SPCIntegrationAPIUrl>/Claim/DamageServiceReport
  • HTTP METHOD: PUT
  • URL Example: https://servicepartnercompany.com/ecbintegration/Claim/DamageServiceReport

Request structure

  • Schema: DamageServiceReportEventRequest.schema.json
  • Example: DamageServiceReportEventRequest.example.json

Root object

PropertyDescription
securityToken*Pre-shared secret string key that is used to authenticate SPC and ECB to each other
timestamp*Message generation UTC date/time. Should be in ISO 8601 format without time zone.
Note: Can be used to restore messages original order (per claim) – due to network/server errors it’s not guaranteed that messages will arrive in the order they were generated
payload*Payload object with integration endpoint specific data

Payload object

PropertyDescription
claim*Claim object
report*Report object

Claim object

PropertyDescription
id*Claim unique identifier in ECB
number*Claim number
url*URL to Claim Details in ECB

Report object

PropertyDescription
responsibleUserLogin*User login of SPC employee responsible for damage report. Also used to identify specific service partner company in SPC organization
Note: List of all users in SPC organization can be obtained using Damage Notification integration points. Those point are described in a separate specification, please contact Scalepoint to obtain it.
referenceNumberClaim reference number in internal SPC system
damageDescriptionDamage Description object
acuteDamageStopAcute Damage Stop object
followUpDamageStopFollow up damage stop object
status*Damage service report status
Possible values are: “Proposed”, “Approved”, “Rejected”, “Draft”
rejectionReasonDamage service report rejection reason in case when report was rejected
url*URL to report details in ECB
messageFree text description that will appear on Messages Tab
filesCollection of File objects

Damage Description object

PropertyDescription
description*Free text damage description
photosCollection of File objects representing damage images only

Acute Damage Stop object

PropertyDescription
arrival*Date and time of arrival to claimant. Should be in ISO 8601 format without time zone (always treated as date/time in tenant local time zone)
workPerformed*Free text description of performed work

Follow up Damage Stop object

PropertyDescription
estimatedStartEstimated work start date. Should be in ISO 8601 format without time zone (always treated as date/time in tenant local time zone)
estimatedFinishEstimated work finish date. Should be in ISO 8601 format without time zone (always treated as date/time in tenant local time zone)
workDescription*Free text description of required work scope
estimatedCost*Estimated Cost object

Estimated Cost object

PropertyDescription
calculationTypeSpecifies whether estimated expense items should be used or total estimated amount. Possible values are: “Items”, “Amount”
groupsCollection of Expense Group objects
itemsCollection of Expense Item objects (redundant when groups are available)
totalAmountTotal estimated cost amount (ex. VAT)

Expense Item object

PropertyDescription
title*Item title
category*Item Category identifier
Supported values are: "Wages", "Materials", "Equipment", "Subcontractor", "Claimant", "Other", "EquipmentInsurance", "SubcontractorAdmin", "EnvironmentAdditional"
unit*Item Unit Of Measure identifier
Supported values are: "Pcs", "Hours", "Days", "Kilograms", "Liters", "Meters", "SquareMeters", "CubicMeters", "Lbm", "Sum", "Tonnes", "Bags", "Kilometers", "CubicMetersDays", "None"
amount*Amount of items
unitPriceItem unit price (ex. VAT)
agreementPrice*Unit price with discount according to agreements with SPC (ex. VAT)
salesPrice*Sales price. agreementPrice value multiplied by amount of items (ex. VAT)
vat*VAT amount
externalCodeItem code from external system
externalIdProduct identifier from external system
externalSourceItem external system source
fulfilledByWho fulfills item. Supported values are: "MyCompany", "Subcontractor", "Claimant"
typeItems type. Supported values are: "Service", "Materials", "Equipment", "EnvironmentalFee", "Dehumidification", "Other"
subitemsSubitem collection of Expense Item objects

File object

PropertyDescription
name*File name
mimeType*File MIME type. For example, “image/jpeg”, “text/html”
SizeOriginal file size in bytes, before Base64 encoding
descriptionFree text file description
id*File unique identifier in ECB

Expense Group object

PropertyDescription
name*Group name
itemsCollection of Expense Item objects

Response structure

  • Schema: DamageServiceReportEventResponse.schema.json
  • Example: DamageServiceReportEventResponse.example.json

Root object

PropertyDescription
success*Boolean flag representing if request is processed successfully
errorDescriptionDescription of errors, if any
payloadPayload object with integration endpoint specific data

Payload object

PropertyDescription
claim.referenceNumber*Claim reference number in SPC internal system

Implementation notes

This endpoint is invoked in both cases when new damage service report was created in ECB and when existing damage service report was modified or its status was changed.

ECB can send only those fields that were modified in damage service report. For example, when report was approved the only Status field is changed, and no information about the report will be included in the request except for required fields and Status field. This allows to avoid sending the same information each time something happens with the report.

Last updated on

On this page