Update a payment adapter configuration

patch

/fscmRestApi/resources/11.13.18.05/publicSectorAdapterConfigs/{publicSectorAdapterConfigsUniqID}

Request

Path Parameters
  • 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
  • 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".
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Agency ID
    Default Value: 1
    The unique identifier of the agency receiving incoming customer payments.
  • Title: Configuration Name
    Maximum Length: 100
    The name of the payment adapter configuration.
  • Title: Configuration Value
    Maximum Length: 300
    The individual payment processing option within the payment adapter configuration.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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.
Body ()
Root Schema : publicSectorAdapterConfigs-item-response
Type: object
Show Source
  • Title: Payment Adapter ID
    Maximum Length: 100
    The unique identifier of the payment adapter.
  • Title: Agency ID
    Default Value: 1
    The unique identifier of the agency receiving incoming customer payments.
  • Title: Configuration ID
    Maximum Length: 15
    The unique identifier of the payment adapter configuration.
  • Title: Configuration Name
    Maximum Length: 100
    The name of the payment adapter configuration.
  • Title: Configuration Value
    Maximum Length: 300
    The individual payment processing option within the payment adapter configuration.
  • Links
Back to Top