Get an opportunity deal

get

/crmRestApi/resources/11.13.18.05/opportunities/{OptyNumber}/child/OpportunityDeal/{OptyDealId}

Request

Path Parameters
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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-OpportunityDeal-item-response
Type: object
Show Source
  • Title: Approved Date
    Read Only: true
    The date and time when deal was approved.
  • 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.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the opportunity deal record.
  • Title: Creation Date
    Read Only: true
    The date and time when the opportunity deal record was created.
  • Title: Expiration Date
    Read Only: true
    The date and time when the deal is set to expire.
  • Title: Deal ID
    The unique identifier of the deal.
  • Title: Deal Name
    Read Only: true
    Maximum Length: 250
    The name of the opportunity deal.
  • Title: Registration Number
    Maximum Length: 30
    The alternate key identifier of the deal registration.
  • Title: Deal Size
    Read Only: true
    The size of the deal associated with the opportunity.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the opportunity deal record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the opportunity deal record.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 32
    The session login associated with the user who last updated the opportunity deal record.
  • Links
  • Title: Opportunity Deal ID
    Read Only: true
    The unique identifier of the opportunity deal.
  • Title: Opportunity ID
    The unique identifier of the opportunity.
  • Title: Opportunity Number
    Maximum Length: 30
    The unique alternate identifier for the opportunity.
  • Title: Partner ID
    Read Only: true
    The unique identifier of the partner tracked in the deal.
  • Title: Partner
    Read Only: true
    Maximum Length: 360
    The name of the partner.
  • Title: Status
    Read Only: true
    Maximum Length: 30
    The code indicating the status of the opportunity deal. A list of valid values is defined in the lookup ORA_MKL_DEAL_REG_STATUS.
Back to Top

Examples

The following example shows how to get an opportunity deal 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_335580/child/OpportunityDeal/300100092363935

Example of Response Body

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

{
"PartyName": "Stryker Corp.",
"StatusCode": "ORA_APPROVED",
"DealName": null,
"OptyDealId": 300100092363935,
"OptyId": 300100092363928,
"DealExpirationDate": "2017-01-16",
"CreatedBy": "JLOPEZ",
"CreationDate": "2016-11-16T05:02:42-08:00",
"LastUpdateDate": "2016-11-16T05:03:04-08:00",
"LastUpdateLogin": "3F16A2DC2AF92E0FE05354C0F20A6B55",
"LastUpdatedBy": "JLOPEZ",
"PartnerId": 100000016934002,
"DealId": 300100092363896,
"DealNumber": "CDRM_47006",
"ApprovedDate": "2016-10-18",
...
}
Back to Top