Create a bill type

post

/fscmRestApi/resources/11.13.18.05/publicSectorBillTypes

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
  • Default Value: 1
    The unique identifier of the agency receiving an incoming customer payment. This is usually the name of a city or county.
  • Title: Bill Type
    Maximum Length: 15
    The bill type. Used to classify invoices into groups of invoice documents that have similar characteristics. They are also used to assign sequence numbers to invoices.
  • Title: Description
    Maximum Length: 100
    Description of the bill type. Enables a business to store more information about the bill type.
  • Title: Invoice Form
    Maximum Length: 20
    The unique identifier of the invoice format assigned to the bill type.
  • Title: Invoice Series
    Maximum Length: 20
    The unique identifier of the invoice number generation rule assigned to a bill type.
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 : publicSectorBillTypes-item-response
Type: object
Show Source
  • Default Value: 1
    The unique identifier of the agency receiving an incoming customer payment. This is usually the name of a city or county.
  • Title: Bill Type
    Maximum Length: 15
    The bill type. Used to classify invoices into groups of invoice documents that have similar characteristics. They are also used to assign sequence numbers to invoices.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the agency.
  • Title: Creation Date
    Read Only: true
    The date and time that the agency was created.
  • Title: Description
    Maximum Length: 100
    Description of the bill type. Enables a business to store more information about the bill type.
  • Title: Invoice Form
    Maximum Length: 20
    The unique identifier of the invoice format assigned to the bill type.
  • Title: Invoice Series
    Maximum Length: 20
    The unique identifier of the invoice number generation rule assigned to a bill type.
  • Title: Last Updated Date
    Read Only: true
    The last date and time that the agency was updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the agency.
  • Links
Back to Top