Create a fee item

post

/fscmRestApi/resources/11.13.18.05/publicSectorFeeItems

Request

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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Agency ID
    Default Value: 1
    The identifier for a public sector agency.
  • Title: Department
    Maximum Length: 30
    The department identifier for a fee item.
  • Title: Description
    Maximum Length: 50
    The description of the fee item.
  • Title: Enabled
    Maximum Length: 1
    Indicates whether this fee item is enabled for use or not. The default value is true.
  • Title: Fee Item
    Maximum Length: 30
    The unique identifier for a fee item.
  • Maximum Length: 30
    Indicates the options for the revenue recognition accounting date.The options are fee paid, fee assessed, and fee refunded. The default value is none.
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 : publicSectorFeeItems-item-response
Type: object
Show Source
Back to Top