Open API
1,400+ endpoints, documented in OpenAPI 3.1. Whatever the screens do can also be done in code.
A large organization does not replace its ERP for a recruiting system. LinkMatch enters the existing environment: calendar, meetings, signature and messaging are built in, and the organization’s core systems connect through an enterprise connector.
Employees, org structure and payroll stay in the system that manages them. LinkMatch reads from them and writes to them.
Employee, org-structure and position sync
ConnectorEmployee, org-structure and position sync
ConnectorEmployee, org-structure and position sync
ConnectorEmployees, customers and orders
ConnectorEmployee, org-structure and position sync
ConnectorEmployee, org-structure and position sync
ConnectorPayroll and employee data
ConnectorOnboarding and offboarding forms
ConnectorNightly attendance pull
Built inPayroll and balance report intake
Built inAccounts, opportunities and orders arrive from the CRM, and status flows back to it.
Accounts, opportunities and orders
ConnectorCompanies and contacts
ConnectorBoards and workflows
ConnectorAlerts to team channels
ConnectorScenarios through the open API
ConnectorScenarios through the open API
ConnectorAlready have an ATS? Bring its history over, or run alongside it. Publishing channels are managed from inside the role.
Import candidates and roles, or run side by side
ConnectorImport candidates and roles, or run side by side
ConnectorImport candidates and roles, or run side by side
ConnectorImport candidates and roles, or run side by side
ConnectorImport candidates and roles, or run side by side
ConnectorImport candidates and roles, or run side by side
ConnectorProfile enrichment and channel management
Built inA structured job feed for Google
Built inJob publishing through a connector
ConnectorJob publishing through a connector
ConnectorAn interview is scheduled against the interviewers’ real calendar, and leaves with a meeting link.
Interview sync with the calendar
Built inA meeting and link from the interview
Built inInterview sync with the calendar
Built inA Meet link for every interview
Built inZoom meeting creation
Built inSelf-scheduling through a connector
ConnectorAn offer goes out for signature, a reminder leaves on WhatsApp, and the team signs in with the company account.
Contracts and offers for signature, with status tracking
Built inAn alternative signature provider
Built inMessages and reminders to candidates and staff
Built inSMS and WhatsApp
Built inJobs mailbox: an emailed CV becomes a candidate
Built inOutgoing system email
Built inSign-in with a Microsoft account
Built inSign-in with a Google account
Built inEnterprise SSO in the rollout project
ConnectorWhat runs the system behind the scenes.
Hosted payment page, Israel
Built inGlobal payments
Built inThe primary AI model
Built inFallback model and embeddings
Built inHosting in the Tel Aviv region
Built inFile storage
Built inS3-compatible storage
Built inError monitoring
Built in“Built in” means an interface that exists in the product. “Connector” means a connection delivered for the customer through the open API, scheduled files or SSO, in a scope agreed in the rollout project. System names appear to indicate compatibility only.
No two enterprise systems look alike, even under the same name. So an enterprise connector starts by mapping what you have, and is built on one of four routes.
1,400+ endpoints, documented in OpenAPI 3.1. Whatever the screens do can also be done in code.
Inbound events, such as a signature status or a message delivery, are verified by signature before they are processed.
For systems that do not speak API: intake of Excel and CSV reports, with validation before the data enters.
Sign-in with a Microsoft or Google account is built in. Other identity providers connect in the rollout project.
Which systems, which fields, in which direction, and who owns each piece of data.
The connection is built and tested against sample data, without touching production.
One unit or one process runs on the live connection, under close monitoring.
Expansion to the whole organization, with monitoring and an alert when a sync fails.
LinkMatch’s own screens run on the same API that is open for connections. A full OpenAPI 3.1 specification is available from inside the system.
# served by the system at /api/docs openapi: 3.1.0 info: title: LinkMatch API paths: # 1,400+ endpoints /api/jobs /api/candidates /api/matches /api/interviews /api/applications /api/clients /api/employees … inbound webhooks: # signature verified e-signature status message delivery inbound e-mail
Send us your list of systems, and get back what is built in, what connects, and how long it takes.