Stronger custom integrations
Teams can build more useful internal workflows when search is available across major recruiting entities.
July 2026 Integrations
Public Search APIs and Native Kynzo Integration
ATZ CRM expanded Public API search coverage for major entities and added a native Kynzo integration for teams that need more connected recruiting workflows.
Public API search endpoints now cover major CRM entities
Integration teams can find records across more parts of ATZ CRM
Custom applications can use broader search access
Native Kynzo Integration is now available
Recruiters get more connected workflow options inside their tech stack
Quick answer
What changed for recruiters?
Search APIs for all public entities give technical teams broader ways to find ATZ CRM records through integrations and custom applications. The native Kynzo integration gives recruiters another connected workflow path without relying on a loose manual handoff.
What changed
What this update changes
ATZ CRM Public API now includes search endpoints for all major public entities. This gives development and operations teams stronger ways to locate records when building integrations, internal tools, reporting workflows, or custom applications around recruiting data.
The update reduces friction for teams that need to search candidates, jobs, contacts, organizations, deals, or other available entities through connected systems.
ATZ CRM also added Native Kynzo Integration. Recruiters using Kynzo can connect it more directly with their ATZ CRM workflow instead of relying on scattered manual steps.
Both updates are about better connectivity: one for custom systems and technical teams, the other for recruiters using Kynzo as part of their daily process.
Why it matters
Why it matters to recruiters
Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.
Less manual record lookup
Connected applications can search ATZ CRM data more directly instead of asking users to copy record details between tools.
More flexible recruiter workflows
Native Kynzo support gives recruiters another connected path for work that previously may have sat outside the CRM.
Better data movement across systems
Search endpoints help integrations identify the right record before updating, linking, or presenting information elsewhere.
Before and after
How the workflow changes
Before
Custom applications had narrower search options and sometimes needed extra workarounds to locate records.
After
Search endpoints across public entities give integration teams a cleaner way to find the right ATZ CRM data.
Before
Recruiters using Kynzo had fewer native connection options inside their recruiting workflow.
After
Native Kynzo Integration gives teams a more direct connection path with ATZ CRM.
Before
Operations teams sometimes had to design entity-specific search behavior for each workflow.
After
Broader search coverage makes custom integration planning more consistent.
How recruiters use it
How the workflow works
The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.
1
Identify the integration need
Decide which records the external system needs to search, such as candidates, jobs, contacts, organizations, or deals.
2
Use public entity search endpoints
Build the connected workflow around the entities your team needs to locate in ATZ CRM.
3
Review permissions and data use
Keep API access aligned with workspace permissions, user roles, and the information the external system genuinely needs.
4
Connect Kynzo where relevant
Use the native Kynzo path when that tool is part of the recruiter workflow.
5
Validate with real recruiter scenarios
Test the connection using records and workflows that recruiters actually use during active hiring work.
Feature-specific details
Extra context for this update
Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.
Connected systems
What broader search access can support
Search endpoints are most useful when another system needs to find the correct ATZ CRM record before showing, updating, or connecting information.
- Internal dashboards can search for the records behind pipeline or productivity views.
- Custom applications can look up the right candidate, job, company, or deal before a workflow continues.
- Automation tools can reduce manual copy-paste when they can identify records reliably.
- Integration owners should still limit access to the data needed for the workflow.
Best fit
Teams that benefit most
Recruiting teams with custom applications
Operations users connecting ATZ CRM with internal tools
Agencies using Kynzo in their recruitment workflow
Enterprise teams that need broader record search through APIs
Technical teams building integrations around recruiting data
Helpful next steps
Related ATZ CRM pages
Integrations hub Review the broader integration ecosystem available around ATZ CRM workflows. Kynzo integration Learn how Kynzo fits into a connected recruiter workflow with ATZ CRM. Zapier integration Use automation paths when teams need no-code workflow connections around recruiting data. n8n integration Explore integration options for teams building more customized workflow automation. MCP Server Compare API-led workflows with the AI-client connectivity released in June 2026. Enterprise Teams See how larger recruiting teams manage connected workflows and operational control.
Quick answers
Common questions
What changed in ATZ CRM Public API?
Search endpoints are now available for all major public entities, giving integrations broader ways to locate records.
Which teams benefit from search APIs?
Teams with custom tools, internal dashboards, data workflows, or connected applications benefit most.
Does this mean every external tool should access every entity?
No. API access should match the workflow need, permissions, and data policies of the recruiting team.
What is Native Kynzo Integration?
It is a direct ATZ CRM integration with Kynzo so recruiters have a more connected workflow path.
How can search endpoints reduce manual work?
Connected systems can find the right record programmatically instead of asking recruiters to copy details between tools.
Should integrations be tested with real recruiting data flows?
Yes. Test with practical recruiter scenarios so the integration supports daily work rather than only passing a technical check.
See it in context
Review this update inside your recruiting workflow
Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.