For Opportunities with Products, the Amount field is a derived field that sums the Total Price of the related Opportunity Products. As a result, the Amount field is not directly editable for such records via the REST API, even though the API call itself may report success.
This article explains why a REST API PATCH request to update the Amount field on an Opportunity with related Opportunity Products returns a 204 success status code, even though the Amount value doesn't actually change.
A REST API request to update the Amount on an Opportunity record returns a 204 status code in the API response if there's no error, regardless of whether the Opportunity has related Products.
Updating the Amount field of an Opportunity record using REST API sObject Rows:
/services/data/v62.0/sobjects/Opportunity/<Record ID>{ "Amount": 5000}The status code returned is 204, as shown in the "Raw Response" in the image above - indicating the request succeeded, even though the Amount value on the Opportunity was not changed because it has related Products.
004052228

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.