| GET | /company/{companyId}/users | Get Users by CompanyId |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| companyId | path | Guid | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | List<TypeUser> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | form | Guid | No | |
| FirstName | form | string | No | |
| LastName | form | string | No | |
| form | string | No | ||
| FullName | form | string | No | |
| IsActive | form | bool | No | |
| CompanyId | form | Guid? | No | |
| Roles | form | string | No | |
| Id | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /company/{companyId}/users HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
result:
[
{
userId: 00000000000000000000000000000000,
firstName: String,
lastName: String,
email: String,
fullName: String,
isActive: False,
companyId: 00000000000000000000000000000000,
roles: String,
id: String
}
],
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}