Validate internal location rules
post
/spms/v2/ships/{shipId}/gatewaySecurity/internalGate/validations
This is to check if a person complies with the internal location rules
Request
Supported Media Types
- application/json
Path Parameters
-
shipId(required): number
Ship Id
Root Schema : Internal Gate Validations Request Body
Type:
object
Title:
Show Source
Internal Gate Validations Request Body
-
gateDirection(required):
integer
Minimum Value:
0
Maximum Value:2
Allowed Values:[ "0", "1", "2" ]
The internal gate direction: * 0 - Bothways * 1 - Outward * 2 - InwardExample:0
-
gatewaySecurityRuleIds:
array gatewaySecurityRuleIds
-
locationId(required):
integer(int64)
Minimum Value:
0
Maximum Value:100000000000000000000000000000000000000
Internal gate location id.Example:12345678
-
profileId(required):
integer(int64)
Minimum Value:
0
Maximum Value:100000000000000000000000000000000000000
Profile Id.Example:12345678
Nested Schema : gatewaySecurityRuleIds
Type:
Show Source
array
-
Array of:
integer
Minimum Value:
0
Maximum Value:100000000000000000000000000000000000000
Gateway security rules id
Example:
[
"123",
"456"
]
Response
Supported Media Types
- application/json
200 Response
OK
Root Schema : Internal Gate Rules Validations Response
Type:
object
Title:
Internal Gate Rules Validations Response
Internal Gate Rules Validations Response
Show Source
-
gateMovement:
string
The value to show internal gate movement.Example:
Pass In Gate
-
movementMessages:
array movementMessages
-
profileId:
integer
Profile IdExample:
12345678
Nested Schema : movementMessages
Type:
Show Source
array
-
Array of:
object MovementMessages
List of messages that may require user attention.
Nested Schema : MovementMessages
Type:
object
List of messages that may require user attention.
Show Source
-
description:
string
The description of the message.Example:
Do you want to allow this person to exit from the previous location G2 then move into this location?
-
type:
string
Allowed Values:
[ "error", "confirmation", "preconfirmation" ]
The movement message type: * error - Indicate the message is error type. * confirmation - Indicate the message is confirmation type. * preconfirmation - Indicate the message is preconfirmation type.Example:confirmation
400 Response
Bad Request
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"HTTP://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Bad Request",
"detail":[
{
"errorPath":"profileId",
"message":"must be greater than or equals to 0"
},
{
"errorPath":"gateDirection",
"message":"Value must be between 0 and 2"
},
{
"errorPath":"locationId",
"message":"must be greater than or equals to 0"
}
]
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
401 Response
Unauthorized
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"HTTP://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2",
"title":"Unauthorized",
"detail":"Valid token is required to access this resource"
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
403 Response
Forbidden
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4",
"title":"Forbidden",
"detail":"Access to this resource is forbidden"
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
404 Response
Not Found
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"HTTP://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5",
"title":"Not Found",
"detail":"Profile Id 12345678 not found."
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
405 Response
Method Not Allowed
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.6",
"title":"Method Not Supported",
"detail":"HTTP method not supported for this resource"
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
406 Response
Not Acceptable
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"HTTP://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7",
"title":"Not Acceptable",
"detail":"PASS IN NOT ALLOWED. GATE IS OUTWARDS ONLY. PLEASE USE ANOTHER GATE."
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
500 Response
Internal Server Error
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"HTTP://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1",
"title":"Internal Server Error",
"detail":"Issue fulfilling request. Please retry or contact support"
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source
503 Response
Service Unavailable
Root Schema : schema
Match All
Show Source
-
object
Error Response
Title:
Error Response
Error Response returned when encountered error
Example:
{
"type":"https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.4",
"title":"Service Unavailable",
"detail":"Service Unavailable. Try again later"
}
Nested Schema : Error Response
Type:
object
Title:
Error Response
Error Response returned when encountered error
Show Source