Integrate every ticketing system with one API
Offer integrations in days, not quarters. Power your app with customers' ticketing data.
Trusted to power integrations at
Supported ticketing platforms
Abstract away API complexity with Merge
Use cases
Read and write financial data
Search and select specific files to share
- File data
Search across all documents
- Drive
- Folder
- File data
Download documents
- Folder
- File data
Upload and organize documents
- File
- Folder data
Update existing tickets and fields
- PATCH Tickets
Create new to-dos directly from your app
- POST Tickets
Visualize and analyze the status of projects and teams
- GET Tickets from Asana and Jira
Add Closed Won customers to a customer success tracker
- Opportunities
- Accounts
- Engagements data
Know what stage an opportunity is in
- Opportunities
- Accounts
- Engagements data
Create & track customer interactions
- Opportunities
- Accounts
- Engagements data
Monitor customer health & sentiment
- Opportunities
- Accounts
- Engagements data
Add sourced contacts or companies to a CRM
- creating Notes
Create notes in a CRM
- creating Notes
Assign tasks created in CRM
- creating Tasks
Pull information on prospects/leads
- Accounts
- Contacts
- Leads
- Opportunities data
Update details to track calls and meetings
- Pulling or posting Opportunities
- Accounts
- Engagements information
Provide data visualizations based on customer data
- Accessing Accounts
- Opportunities
- Leads data
Calculate values of opportunities and leads
- Opportunities
- Leads data
Read $ Amount from Opportunities to understand financial health of a company
- Pulling Opportunities data
Update details on opportunities, leads & contacts
- Creating and updating Opportunities
- Leads
- Contacts
Pull details on opportunities and accounts
- Accounts
- Contacts information
Add candidates to your recruiting pipeline
- Candidate data
Manage headcount planning
- Jobs data
Track new hires
- Offer
- Candidate data
Track candidates through their entire interview process
- Application
- Interviews
- Job Interview States
- Notes data
Power rich analytics about your customers’ talent pipeline
- Interviews data
Pull information from multiple ATS providers into a platform / dashboard
- Candidate
- Offer
- Jobs data
Pull EEOC demographic data
- Candidate data
Manage employee referrals
- Candidates
- Job data
Manage candidates during the recruitment lifecycle
- Candidate
- Offer
- Jobs data
Connect different HR platforms
- Employee data
Deprovision employees when they leave a company
- User
- Group
- Teams data
Autoprovision user accounts, credit cards, device management, and software licenses
- User
- Group
- Teams data
Pull time off (PTO) information
- Time Off
- Employee data
Onboard and offboard employees once they’re hired
- Employee data
Construct org charts
- Employee
- Teams data
Pull salary information
- Employments data
Pull benefit information, employee, and company contributions
- Benefits data
Understand who was paid, when, benefits, deductions, and taxes
- Payroll
- Payroll Run data
Track company spend
- Transaction data
Automatically create purchase orders
- Purchase Order data
Receive payments
- Payments
Track vendor bills
- Invoices
Transfer money
- Journal Entries
Invoice customers
- Invoice data
Record credit card purchases
- Transaction data
Forecast revenue
- Transaction data
Create dashboards
- Transaction data
Candidates partnership qualifications
- Balance Sheet
- Income Statement
- Cash Flow data
Candidate's application for tax credits
- Balance Sheet
- Income Statement
- Cash Flow data
Candidate's fitness for a loan
- Balance Sheet
- Income Statement
- Cash Flow data
The financial health of a company
- Balance Sheet
- Income Statement
- Cash Flow data
Case studies
%201%20(1).webp)
%201%20(1).webp)
The Account object is used to represent the account that a ticket is associated with. The account is a company that may be a customer. This does not represent the company that is receiving the ticket.
The Collection object is used to represent one or more Tickets. There can be a hierarchy of Collections, in which a sub-collection belongs to a parent-collection.
The Contact object is used to represent the customer, lead, or external user that a ticket is associated with.
The Role object is used to represent the set of actions & access that a user with this role is allowed to perform.
The Team object is used to represent one or more Users within the company receiving the ticket.
Whether you need to read or write, Merge makes your build easy
API-based data schemas
Merge builds API-first integrations so your app is always supplied with fresh data. You won't need to re-authenticate regularly, or wait for a manual data sync.
Battle-tested by thousands
Thousands of companies use Merge in production today.
Legacy APIs have painful quirks: Merge doesn’t.
Trusted partner
HR-tech leaders trust Merge to build into their platforms to expand their reach. Merge users trust Merge to expand their future partners.
Make integrations your competitive advantage
Stay in touch to learn how Merge can unlock hundreds of integrations in days, not years
