Kaizen #30 - Parameters in Zoho CRM APIs [Part 2/2]
Hello everyone!
Welcome back to another week of Kaizen!
In this post, we will shed some light on the parameters in Search Records API and other generic parameters available in Zoho CRM APIs.
A. Parameters in Search Records API
1. criteria
Use this parameter to search for records in a particular module based on criteria.
Syntax:
(({api_name}:{starts_with|equals}:{value})and/or({api_name}:{starts_with|equals}:{value})and/or...)
You can set a maximum of 10 conditions (starts_with & equals). When you use parentheses or commas in the value of criteria, you must escape them using a backslash. Further, you must encode the value.
Consider the search term:
((Last_Name:equals:Burns,B)and(First_Name:starts_with:M))
After escaping the comma and parenthesis in the value: ((Last_Name:equals:Burns\,B)and(First_Name:starts_with:M))
After encoding the value:
((Last_Name:equals:Burns%5C%2CB)and(First_Name:starts_with:M))
To use conditions other than starts_with or equals, refer to the Query API.
2. email
Use this parameter to search for records based on email IDs. All the fields with the field type "Email" in a particular module will be searched and listed. For instance, Primary Email, Secondary Email, and so on.
3. phone
Use this parameter to search for records based on phone numbers. All the fields with the field type "Phone" in a particular module will be searched and listed.
4. word
Use this parameter to perform a module-wise global search by word.
Note:
- You cannot search for records with two or more above mentioned parameters in one API call.
- If you specify two or more parameters simultaneously, preference will be given in the following order: criteria, email, phone, and word, and only one of them would work.
B. Other Generic Parameters
1. module
Use the module parameter to perform module-specific operations. For instance, to fetch module-specific metadata like fields, layouts, custom views, and so on. Specify the API name of the module as value. The module API names that can be passed differs from API to API. Refer to the corresponding API documentation to know the supported modules.
APIs in which the "module" parameter can be used:
Fields Metadata API, Layouts Metadata API, Specific Layout Metadata API, Related List Metadata API, Custom View Metadata API, Specific Custom View Metadata API, Get List of Deleted Records API, Get Tags API, Get Record Count For a Specific Tag API, Create Tags, Update a Specific Tag, Update Multiple Tags.
The API call in the example below retrieves the details of the fields in Leads module.
2. ids
Use the ids parameter to perform record specific operations. The "id" key in the Get Records API, represents the unique ID of the record.
APIs in which "ids" parameter can be used:
Delink Related Lists, Delete Variables, Remove Tags from Multiple Records, Delete Notes, and Get Records.
The API call in the example below deletes CRM variables based on ID.
Refer to Kaizen #25 Zoho CRM API - Common Errors and Error Handling to know about the errors related to parameters.
We hope you found this post useful. Let us know your thoughts in the comment section or reach us out 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
Sneha Sridharan
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セミナー