Create an opportunity source

post

/crmRestApi/resources/11.13.18.05/opportunities/{OptyNumber}/child/OpportunitySource1

Request

Path Parameters
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: Conflict ID
    Default Value: 0
    The value used to guarantee the uniqueness of the row when duplicates are created in different databases in case of a disconnected mobile such as mobile databases, or the server.
  • Maximum Length: 32
    The session login associated to the user who last updated the record.
  • The unique Identifier of the opportunity.
  • Title: Opportunity Number
    Maximum Length: 30
    The number of the opportunity which is the unique public identifier of the opportunity.
  • The unique Identifier of the source of the opportunity.
  • Title: Source Code
    Maximum Length: 100
    A unique number indicating the source of the marketing event for the opportunity, such as campaign, new product line, a marketing seminar, and so on.
  • The date and time when the opportunity was last updated from mobile.
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 : opportunities-OpportunitySource1-item-response
Type: object
Show Source
Back to Top

Examples

The following example shows how to create an opportunity source code by submitting a get request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X @example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/opportunities/CDRM_341580/child/OpportunitySource1

Example of Request Body

The following shows an example of the request body in JSON format.

{
"SrcNumber": 100000016526077
}

Example of Response Body

The following shows an example of the response body in JSON format.

{
    "OptySrcId" : 300100092629931,
    "SrcNumber" : 100000016526077,
    "CreatedBy" : "MHoope",
    "CreationDate" : "2016-11-16T05:15:38-08:00",
    "LastUpdateDate" : "2016-11-16T05:15:43-08:00",
    "LastUpdatedBy" : "MHoope",
    "LastUpdateLogin" : null,
    "OptyId" : 300100092516122,
    "UserLastUpdateDate": null
}
 
Back to Top