Kaizen #53 - Sales Orders #API
Hello everyone!
Welcome back to another week of Kaizen.
In this post, we will discuss inserting, updating, and deleting a Sales Order via an API.
What is a Sales Order?
A Sales Order is a document sent to your customers to confirm the items and prices of a sale. It is usually created after a quote is accepted by your customers, and your items are ready to be shipped or delivered to them.
Getting a Sales Order
Use the Get Records API to get the record(s) from the Sales Order module.
Request URL: {api-domain}/crm/v2/Sales_Orders (or)
{api-domain}/crm/v2/Sales_Orders/ {record_id}
Request Method: GET
Sample Response
Creating a Sales Order
Request URL: {api-domain}/crm/v2/Sales_Orders
Request Method: POST
Sample Input
{ "data": [ { "Account_Name": { "id": "3652397000000624046" }, "Subject": "SO Kaizen 53", "Product_Details": [ { "product": { "id": "3652397000000416001" }, "quantity": 10, "Discount": 20, "Unit Price": 1000, "line_tax": [ { "percentage": 10, "name": "Sales Tax" }, { "percentage": 1, "name": "VAT" } ] } ] } ] } |
Request JSON
Key | Description |
Account_Name Mandatory, JSON object | The record ID of the account you want to associate the sales order with. Use the Get Records API to fetch the Account_Name. |
Subject Mandatory, string | The subject line of your sales order. |
Product_Details Mandatory, JSON array | An array of details of the product you want to generate the sales order for. For more details on the keys inside this array, refer to our post on Handling product line items in the inventory modules. |
Owner Optional, JSON object | The record ID of the owner you want to assign this sales order record to. Use the Get Users API to fetch the owner's details. |
Deal_Name Optional, JSON object | The record ID of the deal you want to associate with this sales order. Use the Get Records API to fetch the Deal_Name. |
Quote_Name Optional, JSON object | The record ID of the quote that is associated with the sales order. |
Contact_Name Optional, JSON object | The record ID of the contact you want to associate with the sales order. Use the Get Records API to fetch the Contact_Name. |
Discount Optional, integer | The discount you want to offer on the sales order. |
Description Optional, string | A description of the sales order. |
Customer_No Optional, string | The customer number that you are generating the sales order for. This is for your own internal reference. |
Tax Optional, integer | The tax you want to apply for the sales order (this is different from the tax inside the product details section, which pertains to the taxes levied on that product). |
Carrier Optional, string | The name of the carrier that will ship the sales order. You can get the possible values through the Fields Metadata API. |
Sales_Commission Optional, integer | The commission that is applicable for the sale. |
Due_Date Optional, string | The date in the yyyy-mm-dd format on which the sales order is due. |
Adjustment Optional, integer | The adjustment in the sale, if any, that is added to the grand total of that product. |
Terms_and_Conditions Optional, string | The terms and conditions of the sales order, if any. |
Excise_Duty Optional, integer | The excise duty levied on the sale of the product, if any. |
$line_tax Optional, JSON array | The tax that you want to apply to the Sub Total of the line items while generating the sales order. For more details, refer to Handling product line items in the inventory modules. |
Status Optional, string | The status of the sales order. You can get the possible values through the Fields Metadata API. |
Apart from the above keys, you can also specify the keys about the billing and shipping details. Go to Setup > Developer Space > APIs > API Names > Sales Orders to know the API names of these fields. You can also use the Fields Metadata API.
Sample Response
Note
- You can insert a maximum of 100 sales orders in an API call.
- You can associate up to 200 products with a sales order. Add a JSON object for each product in the Product_Details section.
Updating a Sales Order
Use the Update Records API to update the record(s) in the Sales Order module.
Request URL: {api-domain}/crm/v2/Sales_Orders/record_id (or)
{api-domain}/crm/v2/Sales_Orders (with record IDs in the input body)
Request Method: PUT
Sample Input
In this example, we have updated the product associated with the sales order.
Sample Response
Note
- You can update a maximum of 100 sales orders in an API call.
- When you update multiple sales orders in a single call, pass the record ID of each sales order in the JSON object under the root key "data". Example:{"data": [{"id":"3652397000002791035",},{"id":"3652397000002791004",}]}
Deleting a Sales Order
Use the Delete Records API to delete the record(s) in the Sales Order module.
Request URL: {api-domain}/crm/v2/Sales_Orders/{record_id} (or)
{api-domain}/crm/v2/Sales_Orders?ids=record_id1,record_id2
Request Method: DELETE
Sample Response
Note
You can delete a maximum of 100 sales orders in a single API call.
We hope you found this post useful. Let us know your questions and feedback in the comments section, or write to us at support@zohocrm.com.
Cheers!
New to Zoho LandingPage?
Zoho LandingPage Resources
New to Zoho Survey?
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Bigin?
Topic Participants
Shylaja S
MR Sales PLC
Sunderjan Siddharth
Atishay Jain
Andres
Sticky Posts
Extension pointers for integrating Zoho CRM with Zoho products #8: Upload and manage Zoho Workdrive folders and files from within Zoho CRM
Keeping records on your customers and business prospects is essential for tracking data, conducting follow-ups, and running a business smoothly. When you use two separate applications, and store relevant data in each, checking and tracking data becomesExtension pointers: Handle cases with personalized solutions using custom actions
In our last post, we detailed the steps involved in creating a custom action and the workflow from the developer and end user's side. Now let's look at a working example of how we can create a custom action and implement it in a Zoho CRM account to makeExtension pointers - Simple yet significant pointers #13: On change of field value for CRM variables
CRM variables provide global access to a variable across an entire extension. They also help in the storage of user-specific data provided by the user at the time of installation, which can later be fetched to perform data functionalities. Additionally,Extension pointers: Extend end-user benefits and allow personalization by implementing extensions with custom actions
From our earlier post on custom actions, we know that we can create templated actions, share them with end users, and allow them to reuse those actions to achieve personalized outcomes. In this post, we'll look at how custom actions make it easy for usersExtension pointers - Simple yet significant pointers #12: Functions for Zoho CRM extensions
Functions are essential in achieving logical functionality for an extension. You can easily code your functions in Deluge using drag-and-drop tools to meet your requirements. How to create functions for Zoho CRM extensions in Sigma Go to Sigma and select
New to Zoho TeamInbox?
Zoho TeamInbox Resources
Zoho DataPrep Resources
Zoho CRM Plus Resources
Zoho Books Resources
Zoho Subscriptions Resources
Zoho Projects Resources
Zoho Sprints Resources
Qntrl Resources
Zoho Creator Resources
Zoho WorkDrive Resources
Zoho Campaigns Resources
Zoho CRM Resources
Design. Discuss. Deliver.
Zoho Show Resources
Get Started. Write Away!
Writer is a powerful online word processor, designed for collaborative work.
Zoho CRM コンテンツ
-
オンラインヘルプ
-
Webセミナー
-
機能活用動画
-
よくある質問
-
Ebook
-
-
Zoho Campaigns
- Zoho サービスのWebセミナー