Zoho CRM API

Integrate Zoho CRM with your product—along with any other
CRM
 application

Connect your product to all the applications your customers use via Merge's

CRM

 

Unified API to close more deals, retain customers, and expand to new markets

Get a demo
Your Product
Merge
Your customers' data
Accounts
Association Types
Associations
Async Passthroughs
Audit Trails
Contacts
Custom Object Classes
Custom Objects
Engagement Types
Engagements
Field Mappings
Leads
Notes

Top integration use cases for Zoho CRM

Read more

Sync Zoho CRM Data

Accounts

The Account object is used to represent a company in a CRM system.

Docs
Contacts

The Contact object is used to represent an existing point of contact at a company in a CRM system.

Docs
Engagements

The Engagement object is used to represent an interaction noted in a CRM system.

Docs
Engagement Types

The Engagement Type object is used to represent an interaction activity. A given Engagement typically has an Engagement Type object represented in the engagement_type field.

Docs
Leads

The Lead object is used to represent an individual who is a potential customer.

Docs
Notes

The Note object is used to represent a note on another object.

Docs
Opportunities

The Opportunity object is used to represent a deal opportunity in a CRM system.

Docs
Stages

The Stage object is used to represent the stage of an opportunity.

Docs
Tasks

The Task object is used to represent a task, such as a to-do item.

Docs
Users

The User object is used to represent a user with a login to the CRM system.

Docs

FAQ on integrating with Zoho CRM’s API

How does Merge interact with Zoho CRM's API endpoints?

Here’s a look at some of the data types and fields Merge can retrieve:

1. Events

Merge uses the GET /v2/Events/{event_id} endpoint to fetch event or engagement details. Fields accessed include:

  • Timing Details:some text
    • start_time: When the event begins
    • end_time: When the event concludes
  • Event Metadata:some text
    • subject: The title or subject of the event
    • content: A description or additional details of the event
    • remote_id: A unique identifier for the event in Zoho CRM

2. Deals (Opportunities)

Through the GET /v2/Deals/{opportunity_id} endpoint, Merge retrieves opportunity-related data. Key fields include:

  • Opportunity Details:some text
    • name: The name or title of the deal
    • description: A brief overview or summary of the opportunity
  • Lifecycle and Timing:some text
    • last_activity_at: The timestamp of the last activity on the deal
    • remote_created_at: The creation date of the deal in Zoho CRM
    • close_date: The expected closing date for the opportunity
  • Financials:some text
    • amount: The monetary value associated with the deal
  • Ownership and Progress:some text
    • stage: The current stage or phase of the deal (e.g., Negotiation, Closed Won)
    • owner: The person responsible for managing the opportunity
    • account: The associated account or customer for the deal

3. Leads

Lead data is retrieved to track prospective customers and their activities. Common fields include:

  • Identification and Status:some text
    • name: Name of the lead
    • email: Contact email for the lead
    • phone: Phone number for communication
    • status: Current status (e.g., Open, Contacted)
  • Source Details:some text
    • lead_source: The source from which the lead originated (e.g., Email Campaign, Referral)

Learn more about the endpoints that Merge can interact with.

What are the sync frequencies for Zoho CRM data in Merge?

Merge requests data from Zoho CRM at intervals based on your sync plan. 

Here’s what you can expect:

  • Daily: Sync data once per day
  • Standard: Sync data every hour
  • High: Sync data every 10 or 30 minutes, depending on the Common Model
  • Highest: Sync data every 5 or 15 minutes, depending on the Common Model

For syncing outside of normal intervals, you can use Merge’s Force Resync endpoint or Automatic Webhooks feature.

Learn more about Merge’s sync frequencies for Zoho CRM.

Aside from Zoho CRM, what CRM integrations can Merge add to my product?

Once you’ve built to Merge’s CRM Unified API, you can add more than 20 CRM integrations to your product. This includes:

  • Salesforce
  • HubSpot
  • Pipedrive
  • Microsoft Dynamics 365 Sales
  • Insightly
  • SugarCRM
  • Copper
  • Close
  • Vtiger
  • Zendesk Sell

Learn more about the CRM integrations Merge supports.

What companies use Merge’s integration with Zoho CRM?

A broad range of companies use it, including Rilla, Banyan Infrastructure, and Telescope. Learn more about how these companies use Merge’s Zoho CRM integration—along with Merge's other CRM integrations—here.

Are there any days you’ll be closed for the holidays in 2024?
Trusted to power integrations globally
Build Smarter

Make integrations your competitive advantage

More sales, less code, fewer headaches

Focus on your core product

Stop diverting your engineers to yet another integration and let them get back to work.

Give customer success a break

Manage your simplified integration issues in a single pane. No therapist required.

Stop losing sales due to integrations

Launch integrations in days, not quarters. Your sales team will thank you.

Seamless Account Linking

Integration authentication that feels like magic

Merge seamlessly manages authentication and authorization on behalf of your customers.

Offer account linking and permission controls to your users with Link for a customizable frontend or with Magic Link for URL-based authorization

View docs
APIs Made Simple

The toolkit for all your integration needs

We make integrations painless with accessible API design, dead-simple SDKs, and beautiful documentation that we agonize over.

View docs
Get Employee Data
Python
Ruby
Node
Go
Java
.NET
import merge
from merge.client import Merge
merge_client = Merge(api_key="<YOUR_API_KEY>", account_token="<YOUR_ACCOUNT_TOKEN>")
employee = merge_client.hris.employees.list()

import { MergeClient, Merge } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});
employee = await merge.hris.employees.list()

ApiClient.instance.authentications.tokenAuth = {
  type: 'bearer',
  accessToken: 'API_KEY',
};
new EmployeesApi().employeesList('ACCOUNT_TOKEN', {}, (data) => {
  console.log(data);
});

import (
  "context"
  "fmt"
  merge "github.com/fern-api/merge-go"
  mergeclient "github.com/fern-api/merge-go/client"
  "github.com/fern-api/merge-go/hris"
)

client := mergeclient.NewClient(
  mergeclient.ClientWithAuthApiKey("<YOUR_API_KEY>"),
  mergeclient.ClientWithHeaderAccountToken("<YOUR_ACCOUNT_TOKEN>"),
)
employee, err := client.Hris().Employees().List(
  context.TODO(),
  &hris.EmployeesRetrieveRequest{
    IncludeRemoteData: merge.Bool(true),
  },
)
if err != nil {
  return err
}
fmt.Printf("Retrieved employee with ID %q\n", *employee.Id)

ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath('https://api.merge.dev/api/ats/v1');
ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
tokenAuth.setApiKey('API_KEY');
CandidatesApi apiInstance = new CandidatesApi(client);
apiInstance.candidatesList('ACCOUNT_TOKEN');

import com.merge.api.MergeApiClient;
import com.merge.api.resources.hris.employees.requests.EmployeesRetrieveRequest;
import com.merge.api.resources.hris.types.Employee;
MergeApiClient mergeClient = MergeApiClient.builder()
    .accountToken("ACCOUNT_TOKEN")
    .apiKey("API_KEY")
    .build();
Employee employee = mergeClient.hris().employees().list(
    EmployeesRetrieveRequest.builder()
        .includeRemoteData(true)
        .build());

{
"id": "0958cbc6-6040-430a-848e-aafacbadf4ae",
"remote_id": "19202938",
"employee_number": "2",
"company": "8d9fd929-436c-4fd4-a48b-0c61f68d6178",
"first_name": "Dirna",
"last_name": "Emanuel",
"display_full_name": "Dirna Emanuel",
"username": "dirnaemanuel",
"groups": [
  "21a54124-397f-494d-985e-3c5b330b8a68"
],
"work_email": "dirna@merge.dev",
"personal_email": "dirnaemanuel@gmail.com",
"mobile_phone_number": "+1234567890",
"employments": [
  "17a54124-287f-494d-965e-3c5b330c9a68"
+ More languages
Meta Endpoint

Programmatically access required schemas

Third-party providers require specific (and often different) fields to write data to their APIs, making your code a mess.

Dynamically fetch required data schemas from Merge’s /meta endpoint to make POST or PATCH requests that just work.

View Docs
Beyond Building

Rely on the best integration observability system

Let our logs, issue detection, and automated alerts save your customer success team time, money, and headaches.

Forget maintenance - let your developers focus on building!

Start for free

How Drata helps thousands streamline their SOC 2 with Merge

Read case study

​​”Working with Merge’s Unified API and beautiful React component took less than a sprint to integrate, test, and release.”

Daniel Marashlian of profile photo
Daniel Marashlian
Co-Founder & CTO

Read more about building and maintaining multiple integrations

A guide to maintaining your product integrations
A guide to maintaining your product integrations
Blog
Blog Posts
10/27/2023
A guide to integrating multiple APIs
A guide to integrating multiple APIs
Blog
Blog Posts
11/13/2023
The top challenges of normalizing multiple API integrations
The top challenges of normalizing multiple API integrations
Blog
Blog Posts
11/20/2023
One Step Ahead

We're the cheat code to your integrations strategy

Revolutionize your integrations strategy for HR, payroll, directory, ATS, project management, ticketing, accounting and CRM platforms.

Start for free or talk to our sales team and learn how Merge makes it easy to add all your integrations in days – not years.
Get a demo
Create free account
CRM
CRM
Read more