Returns asset tag validation information for the specified list of assets
Request
- Base URLhttps://sb2api.servicechannel.com/v3
- AuthOAuth 2Authorization codehttps://sb2login.servicechannel.com/oauth/authorizeToken URLhttps://sb2login.servicechannel.com/oauth/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Unique numeric identifier of the scanned asset. Must be greater than 0.
Tracking number of the work order associated with the scanned asset. Must be greater than 0.
Unique numeric identifier of the work order associated with the scanned asset.
Validation status of the scanned asset tag. Possible values: • 0=Unknown: Validation status is not determined. • 1=NotAvailable: Asset tag does not exist or cannot be scanned. • 2=NotValidated: Asset tag exists, but validation failed. • 3=PendingValidation: Asset tag has been scanned and is awaiting validation. • 4=Validated: Asset tag has been successfully validated.
Indicates whether the asset tag value was entered manually instead of being scanned. Possible values: true and false.
Free‑text explanation of why the tag was not scanned. Must not exceed 50 characters.
Indicates whether this asset requires asset tag validation. Possible values: true and false. To check whether validation is required, run the GET/assets/{trackingNumber}/IsValidationRequired method.
Indicates whether the asset has been successfully validated. Possible values: true and false.
Standardized reason code defining why validation could not be completed. Possible values: • 1: Cannot find the asset in the database • 2: Cannot find the asset on site • 3: New asset • 4: Other (requires explanation in OtherReason) To check the reasons and their IDs, run the GET/assets/UnableToValidateReasons method.
Free-text explanation of why validation failed. Required when UnableToValidateReasonId = 4 (Other).
Standardized reason code defining why scanning could not be completed. Possible values: • 1: Tag Missing • 2: Tag Damaged • 3: Scanner Problem • 4: Other To get the reason codes, run the GET/assets/UnableToScanReasons method.
Response
Request succeeded
Unique numeric identifier of the scanned asset. Must be greater than 0.
Tracking number of the work order associated with the scanned asset. Must be greater than 0.
Unique numeric identifier of the work order associated with the scanned asset.
Validation status of the scanned asset tag. Possible values: • 0=Unknown: Validation status is not determined. • 1=NotAvailable: Asset tag does not exist or cannot be scanned. • 2=NotValidated: Asset tag exists, but validation failed. • 3=PendingValidation: Asset tag has been scanned and is awaiting validation. • 4=Validated: Asset tag has been successfully validated.
Indicates whether the asset tag value was entered manually instead of being scanned. Possible values: true and false.
Free‑text explanation of why the tag was not scanned. Must not exceed 50 characters.
Indicates whether this asset requires asset tag validation. Possible values: true and false. To check whether validation is required, run the GET/assets/{trackingNumber}/IsValidationRequired method.
Indicates whether the asset has been successfully validated. Possible values: true and false.
Standardized reason code defining why validation could not be completed. Possible values: • 1: Cannot find the asset in the database • 2: Cannot find the asset on site • 3: New asset • 4: Other (requires explanation in OtherReason) To check the reasons and their IDs, run the GET/assets/UnableToValidateReasons method.
Free-text explanation of why validation failed. Required when UnableToValidateReasonId = 4 (Other).
Standardized reason code defining why scanning could not be completed. Possible values: • 1: Tag Missing • 2: Tag Damaged • 3: Scanner Problem • 4: Other To get the reason codes, run the GET/assets/UnableToScanReasons method.
Changes
No recorded changes to this operation across all 1 revision of this API.