Get user list by company
GET/api/inspect/v1/user
Fetch the list of users in a company.
Request
Query Parameters
Company ID for which users are to be fetched.
Responses
- 200
- 400
- 401
- 403
- 404
- 500
200 response
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
data
object[]
The list of users.
URL of the user's profile picture
Possible values: [0
, 1
, 6
, 2
, 3
, 5
]
Role of the user. 0 = Normal, 1 = Owner, 6 = Admin, 2 = Manager, 3 = Inspector, 5 = Viewer
Whether the user is active
Email address of the user
First name of the user
Unique identifier (ID) for the user
Last name of the user
{
"data": [
{
"pictureURL": "https://example.com/user.jpg",
"role": 1,
"active": true,
"email": "user@example.com",
"firstName": "John",
"id": 1413,
"lastName": "Doe"
}
]
}
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"
}