Create an expertise for a partner
post
/crmRestApi/resources/11.13.18.05/partners/{CompanyNumber}/child/expertises
Request
Path Parameters
-
CompanyNumber(required): string
The alternate key identifier of the partner's company.
Header Parameters
-
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.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
ExpertiseCode: string
Maximum Length:
30
The code indicating the expertise of the partner. For example, COMPUTER_HARDWARE, or MANAGEMENT_CONSULTING. -
PartnerCompanyNumber: string
Title:
Partner Number
Maximum Length:30
The unique identifier of the partner company. -
PartnerMultivalLovId: integer
(int64)
Title:
Expertise ID
The unique identifier for partner expertise.
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 : partners-expertises-item-response
Type:
Show Source
object
-
CreatedBy: string
Read Only:
true
Maximum Length:64
The user who created the record. -
CreationDate: string
(date-time)
Read Only:
true
The date when the record was created. -
ExpertiseCode: string
Maximum Length:
30
The code indicating the expertise of the partner. For example, COMPUTER_HARDWARE, or MANAGEMENT_CONSULTING. -
ExpertiseName: string
Title:
Meaning
Read Only:true
Maximum Length:80
The display name of the partner expertise. -
LastUpdateDate: string
(date-time)
Read Only:
true
The date when the record was last updated. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
The user who last updated the record. -
LastUpdateLogin: string
Read Only:
true
Maximum Length:32
The login of the user who last updated the record. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
PartnerCompanyNumber: string
Title:
Partner Number
Maximum Length:30
The unique identifier of the partner company. -
PartnerMultivalLovId: integer
(int64)
Title:
Expertise ID
The unique identifier for partner expertise.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed 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
- PartnerExpertisesLOV
-
Parameters:
- finder:
LookupTypeActiveEnabledOrBindCodeFinder%3BBindLookupType%3DZPM_PARTNER_EXPERTISE
The lookups resource is used to view standard lookup codes. - finder:
Examples
cURL Command
The following example shows how to create an expertise for a partner by submitting a create request on the REST resource using cURL.
curl -u <username:password> \ -X POST -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/partners/100001/child/expertises
Example of Request Body
The following example shows the contents of the request body in JSON format.:
{ "LookupType" : "ZPM_PARTNER_EXPERTISE", "LookupCode" : "FINANCE_CONSULTING", "ExpertiseCode" : "FINANCE_CONSULTING", "ExpertiseName" : "Finance Consulting" }
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "items" : [ { "PartnerMultivalLovId" : 300100036771990, "PartyId" : 100000016934002, "LookupType" : "ZPM_PARTNER_EXPERTISE", "LookupCode" : " FINANCE_CONSULTING ", "ExpertiseCode" : " FINANCE_CONSULTING ", "ExpertiseName" : "Finance Consulting", ..., }