Update a payment adapter configuration
patch
/fscmRestApi/resources/11.13.18.05/publicSectorAdapterConfigs/{publicSectorAdapterConfigsUniqID}
Request
Path Parameters
-
publicSectorAdapterConfigsUniqID(required): string
This is the hash key of the attributes which make up the composite key--- AdapterId, ConfigurationId and AgencyId ---for the Adapter Configs resource and used to uniquely identify an instance of Adapter Configs. The client should not generate the hash key value. Instead, the client should query on the Adapter Configs collection resource with a filter on the primary key values in order to navigate to a specific instance of Adapter Configs.
For example: publicSectorAdapterConfigs?q=AdapterId=<value1>;ConfigurationId=<value2>;AgencyId=<value3>
Header Parameters
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
AgencyId: integer
(int32)
Title:
Agency ID
Default Value:1
The unique identifier of the agency receiving incoming customer payments. -
ConfigurationName: string
Title:
Configuration Name
Maximum Length:100
The name of the payment adapter configuration. -
ConfigurationValue: string
Title:
Configuration Value
Maximum Length:300
The individual payment processing option within the payment adapter configuration.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context(required):
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version(required):
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : publicSectorAdapterConfigs-item-response
Type:
Show Source
object
-
AdapterId: string
Title:
Payment Adapter ID
Maximum Length:100
The unique identifier of the payment adapter. -
AgencyId: integer
(int32)
Title:
Agency ID
Default Value:1
The unique identifier of the agency receiving incoming customer payments. -
ConfigurationId: string
Title:
Configuration ID
Maximum Length:15
The unique identifier of the payment adapter configuration. -
ConfigurationName: string
Title:
Configuration Name
Maximum Length:100
The name of the payment adapter configuration. -
ConfigurationValue: string
Title:
Configuration Value
Maximum Length:300
The individual payment processing option within the payment adapter configuration. -
links: array
Links
Title:
Links
The link relations associated with the resource instance.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.