Create a set of hearing body week recurrences

post

/fscmRestApi/resources/11.13.18.05/publicSectorHearingBodyWeekRecurrences

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 unique identifier of the agency.
  • Title: Enabled
    Maximum Length: 1
    Indicates if the hearing body week recurrence is available to use.
  • Title: Hearing Body Code
    Maximum Length: 60
    The unique identifier of the hearing body.
  • Title: Occurrence
    Maximum Length: 15
    The frequency within which the hearing body meets in a month. For example First Sunday, Second Tuesday.
  • Title: Weekday
    Maximum Length: 15
    The day of the week when the hearing body meeting is scheduled.
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 : publicSectorHearingBodyWeekRecurrences-item-response
Type: object
Show Source
Back to Top