Submit additional results for a tax credit package

post

/hcmRestApi/resources/11.13.18.05/recruitingTaxCreditsCandidateResults/{recruitingTaxCreditsCandidateResultsUniqID}/child/packages/{PackageResultId}/child/AdditionalResultsAttributes

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • This is the hash key of the attributes which make up the composite key--- PartnerId, RequisitionNumber and CandidateNumber ---for the Recruiting Tax Credits Results resource and used to uniquely identify an instance of Recruiting Tax Credits Results. The client should not generate the hash key value. Instead, the client should query on the Recruiting Tax Credits Results collection resource with a filter on the primary key values in order to navigate to a specific instance of Recruiting Tax Credits Results.

    For example: recruitingTaxCreditsCandidateResults?q=PartnerId=<value1>;RequisitionNumber=<value2>;CandidateNumber=<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
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 : recruitingTaxCreditsCandidateResults-packages-AdditionalResultsAttributes-item-response
Type: object
Show Source
Back to Top