Insightly API

Integrate Insightly 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

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 Insightly

Sync Insightly Data

FAQ on integrating with Insightly’s API

How frequently does Merge sync data from Insightly?

Merge offers various sync frequencies, depending on your plan.

  • Daily Sync: Syncs data once per day at a specified time
  • Standard Sync: Syncs data every 6 hours
  • High Sync: Syncs data every 3 hours
  • Highest Sync: Syncs data every hour

You can also trigger immediate re-syncs using the Force Resync endpoint or enable Automatic Webhooks to receive real-time updates directly from Insightly.

Learn more about Merge’s sync frequencies for Insightly.

What are some common endpoints Merge can access when integrating with Insightly?

Merge interacts with several key endpoints from Insightly, including:

  • Opportunities: Access opportunity data, such as amount, stage, and status
  • Organizations: Retrieve organization details, like phone numbers, website, and addresses
  • Contacts: Fetch contact details, including email addresses, phone numbers, and names
  • Tasks: Access task information, like status, due dates, and owners
  • Leads: Retrieve lead data, such as title, company, and converted status

Learn more about the endpoints Merge interacts with.

What other CRM integrations does Merge support?

Merge’s CRM Unified API enables you to add dozens of CRM integrations to your product—in addition to Insightly. This includes:

  • Salesforce
  • HubSpot
  • Pipedrive
  • Zoho CRM
  • Microsoft Dynamics 365 Sales
  • Zendesk Sell
  • ActiveCampaign
  • Capsule
  • Copper

Learn more about the CRM integrations Merge supports.

How is your customer's Insightly data encrypted and where is it stored?

Customer data from Insightly, like all other integrations Merge supports, is encrypted both in transit and at rest using industry-standard encryption protocols. Merge also stores this data in secure, SOC 2 compliant, cloud-based environments, ensuring that your customers’ Insightly data is protected and managed in compliance with best practices in the industry.

How long does it take developers to set up an Insightly integration?

Setting up an integration with Insightly via Merge typically takes between 1-3 days. Moreover, once you’ve integrated with Merge’s Unified API, you can access the dozens of other CRM integrations Merge supports, making it easy to scale your CRM integrations, fast.

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.

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
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"
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.
Read more