Update a gatekeeping rule annex
patch
/admin/gatekeepingRuleAnnexes/{id}
Request
Path Parameters
-
id(required): string
The id of the GatekeepingRuleAnnex to be updated
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
array-
Array of:
object PatchDocument
A JSONPatch document as defined by RFC 6902
Nested Schema : PatchDocument
Type:
objectA JSONPatch document as defined by RFC 6902
Show Source
-
from: string
A string containing a JSON Pointer value.
-
op(required): string
Allowed Values:
[ "add", "remove", "replace", "move", "copy", "test" ]The operation to be performed -
path(required): string
A JSON-Pointer
-
value: object
value
The value to be used within the operations.
Nested Schema : value
Type:
objectThe value to be used within the operations.
Response
Supported Media Types
- application/json
200 Response
OK
Nested Schema : DestinationSelection
Type:
Show Source
object-
api-id: string
Pattern:
^[a-z0-9]{1,8}-[0-9]{1,4}$ -
api-version: string
-
criteria: array
criteria
-
description: string
-
include-in-sparse-query-results: object
include-in-sparse-query-results
400 Response
Bad Request
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
401 Response
Unauthorized
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
403 Response
Forbidden
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
404 Response
Not Found
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
409 Response
Conflict
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
500 Response
Internal Server Error
Root Schema : Error
Type:
objectUsed when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
Examples
The following example shows how to update a gatekeeping rule annex by submitting a post request on the REST resource using cURL.
cURL Command
curl --<username:password> --request PATCH
'{FABRIC_HOST}/admin/gatekeepingRuleAnnexes/{id}' --header 'Authorization:
Bearer <accessToken> --header 'Content-Type: application/json'
Example of Request Body
The following shows an example of the request body in JSON format.
[
{
"op": "replace",
"path": "/destination-selection/0/criteria/0/rank",
"value": "21"
}
]
Example of Response Body
The following shows an example of the response body in JSON format.
{
"gatekeepingrule-name": "gkr-external-rest-buying",
"destination-selection": [
{
"api-id": "tmf-671",
"api-version": "v4",
"criteria": [
{
"rank": 21,
"resource-ids": [
"promotion"
],
"criterion-link": "WILDCARD"
}
],
"include-in-sparse-query-results": {
"enabled": true
}
}
],
"id": "gkr-external-rest-buying-annex-gragsw66"
}