EndPoints for Zoho CRM Connector
On this page you will see possible API actions you can perform with Zoho CRM connector. We will refer this as API EndPoint or just EndPoint.
| Label | Name | Description |
|---|---|---|
| Read Data (Query Mode - Max 200 Rows Only) | get_module_data_coql | |
| List Modules | get_modules | [API reference] |
| List Territories | get_territories | [API reference] |
| List Module Settings | get_module_settings | To get the metadata for a specific module. Specify the API name of the module, such as Leads, Accounts or Deals in your API request. [API reference] |
| List Tags | get_tags | List tags for module. [API reference] |
| Gets record count for specific tag for module | get_tag_record_count | Add tags for specified module and specified record id(s). [API reference] |
| Add / Update Tags for records | post_tags | Add tags for specified module and specified record id(s). [API reference] |
| List Module Fields | get_module_fields | To get the field meta data for the specified module. The fields displayed are from all layouts for the module and the response does not contain layout-specific fields like mandatory fields or picklist values. |
| List Views | get_module_views | |
| Read [$parent.module_name$] | get_[$parent.api_name$] | This endpoint reads records using bulk approach. Default API Version is V2 (set connection level) and its almost 2 times faster than higher API version (e.g. V3+) but V2 may return less number of columns compared to new API versions (e.g. v3...v7+). API V2 makes less number of requests and returns more records per call (200 rows), on the other side V3+ has limits of max 50 fields in each Get Records API calls. To avoid this limitation in V3+ API we used /{module}?ids={150 ids} workaround but this is still slower compred to older API (v2) approach. Choose new API if you have a valid reason (e.g. you need additional new columns exposed in v3+) else stick with older version V2 (its default setting) [API reference] |
| Read [$parent.module_name$] (Use this for fewer than 50 Fields in v3+) | get_[$parent.api_name$]_fast | Use this endpoint if you have fewer than 50 fields and you like to utilize newer APi e.g. V3+, If you calling older API V2 then you can use any endpoint (e.g. get_contacts or get_contacts_fast or Contacts table all yeilds same speed in V2). [API reference] |
| Search [$parent.module_name$] | search_[$parent.api_name$] | Search records by criteria or email or phone or word or id (specify only one parameter for search and keep other blank) [API reference] |
| Delete [$parent.module_name$] | delete_[$parent.api_name$] | [API reference] |
| Insert [$parent.module_name$] | post_[$parent.api_name$] | |
| Update [$parent.module_name$] | put_[$parent.api_name$] | |
| Upsert [$parent.module_name$] (Update or Insert) | upsert_[$parent.api_name$] | |
| Generic Request | generic_request | This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. |
| Generic Request (Bulk Write) | generic_request_bulk_write | This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. |