Get spot by ID
GET/api/inspect/v1/spot/:id
Fetch spot details with the ID of the spot.
Request
Path Parameters
Spot ID for which spot details are to be fetched.
Responses
- 200
- 400
- 401
- 403
- 404
- 500
200 response
- application/json
- Schema
- Example (from schema)
Schema
data
object
A specific location or area of interest identified for recording data or information, usually where a potential issue or condition is observed and recorded using a spot template.
The URL of the thumbnail image representing the spot.
The ID of the user who last updated the spot
The unique identifier of the asset to which the spot belongs.
The timestamp when the spot was created in milliseconds
fields
object
A map of spot fields and their values. The keys are the IDs of the spot fields, and the values are the values of the spot fields.
A map of spot fields and their values. The keys are the IDs of the spot fields, and the values are the values of the spot fields.
The unique identifier of the spot template used to create the spot.
The spot number
The timestamp when the spot was last updated in milliseconds
A flag indicating whether the spot is archived.
The ID of the user who created the spot
The unique identifier of the spot
{
"data": {
"thumbnailURL": "https://example.com/spot/thumbnail.jpg",
"updatedBy": 1413,
"assetID": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"createdAt": 1652933097739,
"fields": {
"377b652d-8ff7-4828-b7e1-31deae5b2faa": "There are some damages on the wall",
"assignedTo": null,
"dueDate": 1630444800000,
"fb122b5a-8871-4fee-a708-9d9a3b94c0db": "377b652d-8ff7-4828-b7e1-31deae5b2faa",
"severity": "major"
},
"spotTemplateID": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"ticketID": 3,
"updatedAt": 1652933097739,
"archived": false,
"createdBy": 1413,
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
}
400 Bad Request. The request is invalid. This may occur if required parameters are missing or invalid. Ensure that all required parameters are included and valid.
- application/json
- Schema
- Example (from schema)
Schema
A detailed description of the error, providing more context or information about what went wrong. This is intended to help understand the cause of the error and how to resolve it.
A code representing the specific error that occurred. This can be used to programmatically identify and handle the error.
{
"errorDescription": "permission denied",
"error": "Forbidden"
}
401 Unauthorized. Authentication is required and was not provided or is invalid. Ensure that the correct credentials or tokens are included in the request.
- application/json
- Schema
- Example (from schema)
Schema
A detailed description of the error, providing more context or information about what went wrong. This is intended to help understand the cause of the error and how to resolve it.
A code representing the specific error that occurred. This can be used to programmatically identify and handle the error.
{
"errorDescription": "permission denied",
"error": "Forbidden"
}
403 Forbidden. The client does not have permission to perform this action. This might happen if the client lacks the necessary privileges to interact with the specified entity.
- application/json
- Schema
- Example (from schema)
Schema
A detailed description of the error, providing more context or information about what went wrong. This is intended to help understand the cause of the error and how to resolve it.
A code representing the specific error that occurred. This can be used to programmatically identify and handle the error.
{
"errorDescription": "permission denied",
"error": "Forbidden"
}
404 Not Found. The specified entity does not exist. Verify that the reference given is correct and that the entity is available.
- application/json
- Schema
- Example (from schema)
Schema
A detailed description of the error, providing more context or information about what went wrong. This is intended to help understand the cause of the error and how to resolve it.
A code representing the specific error that occurred. This can be used to programmatically identify and handle the error.
{
"errorDescription": "permission denied",
"error": "Forbidden"
}
500 Internal Server Error. An error occurred on the server while processing the request. Retry the operation or contact support if the issue persists.
- application/json
- Schema
- Example (from schema)
Schema
A detailed description of the error, providing more context or information about what went wrong. This is intended to help understand the cause of the error and how to resolve it.
A code representing the specific error that occurred. This can be used to programmatically identify and handle the error.
{
"errorDescription": "permission denied",
"error": "Forbidden"
}