For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Resources
Log inGet a demo
Get startedAPI referenceImplementation
Get startedAPI referenceImplementation
    • Overview
    • Introduction
    • Unified API
    • Linked Account
    • Merge Link
    • Use cases
      • Analyze compensation
      • Analyze payroll runs
      • Analyze project status
      • Analyze spend
      • Assign trainings
      • Auto provision
      • Automate gifts
      • Candidate journey recruiters
      • Candidate journey
      • Candidate matchmaking
      • Career development
      • Collect security evidence
      • Contact information
      • Create invoices
      • Create purchase orders
      • Customer payment reconciliation
      • Deal notifications
      • Employee analysis (GRC)
      • Enrich compliance data
      • Financial analysis
      • Forecast revenue
      • Headcount planning
      • Historical payroll
      • Internal database
      • Onboard and offboard
      • Opportunity recommendations
      • Org chart
      • Sales rep performance
      • Share specific documents
      • Source candidates
      • Source leads
      • Surface open jobs
      • Surface screening questions
      • Sync customers or suppliers
      • Sync expenses
      • Talent pool visibility
      • Track compliance
      • Track contracts
      • Track security controls
      • Train AI accounting
      • Train AI ATS
      • Train AI CRM
      • Train AI HRIS
      • Train AI ticketing
      • Upload contracts file
      • Vendor reconciliation
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
Use cases

Surfacing open jobs

Ingest job information from an ATS relating to a specific industry or vertical

Key models and fields

JobsGET
name
job_posting_urls
status
name

Key features

  • Field Mappings

Typical sync frequency
Highest

Industries

Job Search Sites
Talent Sourcing Applications
Was this page helpful?
Previous

Source leads

Next

Surface screening questions

Built with

1. Authentication and connection

Your users authorize your application to access their ATS platform by going through an authorization flow using Merge Link.

Your Product's Frontend and Merge

You can set up Field Mapping to pull in custom fields that your end users want to surface for their jobs.

2. Data retrieval from ATS Platform

Utilize Merge’s GET /jobs endpoint to programmatically pull all job requisitions that exist within your customers’ ATS platform.

There may be additional custom fields your customer wants to be surfaced for open jobs. This will be in the Field Mapping section within the Jobs Object.

Merge and Third-Party Platforms

3. Identifying what jobs to surface within your product

On the initial pull from Merge, you can filter to only pull Jobs that are currently Open during that point in time.

Moving forward, you can pull job requisition updates from the ATS system to ensure you are keeping an accurate list of open job requisitions for your customers.

Your Product's Backend

4. Surface open jobs to customers

After identifying the specific jobs and relevant information the customer wants to surface, you can build a frontend experience to show open requisitions in your product. Now your customers’ open job listings are automatically pulled and surfaced.

Your Product's Frontend
Get started in automating your customers

Integrate today or talk to our sales team to learn how Merge unlocks hundreds of integrations in days - not years.


Get a demo