Create a consent agreement
post
/fscmRestApi/resources/11.13.18.05/hedElectronicConsents
Request
Header Parameters
-
Metadata-Context: string
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".
-
REST-Framework-Version: string
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.
-
Upsert-Mode: string
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
- application/json
Root Schema : schema
Type:
Show Source
object-
ConsentCode(required): string
Title:
Consent CodeMaximum Length:80The user-defined code of the consent agreement. -
consentDetails: array
Consent Details
Title:
Consent DetailsConsent details represent the details that are associated with the consent agreement. For example, retrieving the details of a payment plan agreement will return a summary, terms and conditions, and agreement text. -
ConsentLanguage(required): string
Title:
Primary LanguageMaximum Length:4The primary language of the consent agreement text. -
PartyId(required): integer
(int64)
Title:
Party IDUnique identifier of the student. -
SourceObjectCode(required): string
Title:
Agreement Source CodeMaximum Length:30Code of the source of the agreement. -
SourceObjectId(required): integer
(int64)
Title:
Agreement Source IDUnique identifier of the source of the agreement.
Nested Schema : Consent Details
Type:
arrayTitle:
Consent DetailsConsent details represent the details that are associated with the consent agreement. For example, retrieving the details of a payment plan agreement will return a summary, terms and conditions, and agreement text.
Show Source
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
Root Schema : hedElectronicConsents-item-response
Type:
Show Source
object-
ConsentCode: string
Title:
Consent CodeMaximum Length:80The user-defined code of the consent agreement. -
consentDetails: array
Consent Details
Title:
Consent DetailsConsent details represent the details that are associated with the consent agreement. For example, retrieving the details of a payment plan agreement will return a summary, terms and conditions, and agreement text. -
ConsentLanguage: string
Title:
Primary LanguageMaximum Length:4The primary language of the consent agreement text. -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:trueDate that the consent agreement was created. -
ElectronicConsentId: integer
(int64)
Title:
Electronic Consent IDRead Only:trueUnique identifier of the consent agreement. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
PartyId: integer
(int64)
Title:
Party IDUnique identifier of the student. -
PartyName: string
Title:
NameRead Only:trueMaximum Length:360Name of the student. -
SourceObjectCode: string
Title:
Agreement Source CodeMaximum Length:30Code of the source of the agreement. -
SourceObjectId: integer
(int64)
Title:
Agreement Source IDUnique identifier of the source of the agreement. -
SourceObjectMeaning: string
Title:
Agreement Source MeaningRead Only:trueMaximum Length:80The object that's the source of the agreement. -
SourceObjectName: string
Title:
Agreement Source NameRead Only:trueMaximum Length:255Name of the source of the agreement, such as a tax document that requires consent or a payment plan that requires agreement to terms and conditions.
Nested Schema : Consent Details
Type:
arrayTitle:
Consent DetailsConsent details represent the details that are associated with the consent agreement. For example, retrieving the details of a payment plan agreement will return a summary, terms and conditions, and agreement text.
Show Source
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : hedElectronicConsents-consentDetails-item-response
Type:
Show Source
object-
ConsentCode: string
Title:
Consent CodeRead Only:trueMaximum Length:30The user-defined code of the consent agreement. -
ConsentDetail: string
(byte)
Title:
Consent DetailRead Only:trueThe details of the consent agreement. -
ConsentDetailId: integer
(int64)
Title:
Consent Detail IDRead Only:trueUnique identifier of the consent agreement details. -
ConsentMeaning: string
Title:
Consent NameRead Only:trueMaximum Length:80Name of the consent details. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- consentCodesLOV
-
Parameters:
- finder:
ByLookupTypeFinder%3BLookupCode%3D{ConsentCode}%2CLookupType%3DORA_HEY_CONSENT_DETAIL_TYPE
The following properties are defined on the LOV link relation:- Source Attribute: ConsentCode; Target Attribute: LookupCode
- Display Attribute: Meaning
- finder:
- consentDetails
-
Operation: /fscmRestApi/resources/11.13.18.05/hedElectronicConsents/{ElectronicConsentId}/child/consentDetailsParameters:
- ElectronicConsentId:
$request.path.ElectronicConsentId
Consent details represent the details that are associated with the consent agreement. For example, retrieving the details of a payment plan agreement will return a summary, terms and conditions, and agreement text. - ElectronicConsentId:
- sourceObjectsLOV
-
Parameters:
- finder:
ByLookupTypeFinder%3BLookupCode%3D{SourceObjectCode}%2CLookupType%3DORA_HEY_CONSENT_SOURCE_TYPE
The following properties are defined on the LOV link relation:- Source Attribute: SourceObjectCode; Target Attribute: LookupCode
- Display Attribute: Meaning
- finder: