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
          • The Employment object
          • GET/employments
          • GET/employments/{id}

Get started

  • Overview
  • Introduction
  • Unified API
  • Linked Account
  • Merge Link
  • Use cases

Implementation

  • Sandboxes
  • SDKs
  • API access
  • Syncing data
  • Writing data
  • Data minimization
  • Supplemental data
  • Errors
  • Integration metadata

API reference

  • ATS
  • HRIS
  • Accounting
  • Ticketing
  • CRM
  • File Storage
  • Knowledge Base
  • Chat

Resources

  • Help Center
  • Merge.dev
  • Changelog
© Merge 2026Terms of usePrivacy policy
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
Common ModelsEmployments

The Employment object

The Employment Object
1{
2  "id": "string",
3  "remote_id": "string",
4  "created_at": "2023-01-01T00:00:00Z",
5  "modified_at": "2023-01-01T00:00:00Z",
6  "employee": "string",
7  "job_title": "string",
8  "pay_rate": 1,
9  "pay_period": "HOUR",
10  "pay_frequency": "WEEKLY",
11  "pay_currency": "XUA",
12  "pay_group": "string",
13  "flsa_status": "EXEMPT",
14  "effective_date": "2023-01-01T00:00:00Z",
15  "employment_type": "FULL_TIME",
16  "remote_was_deleted": true,
17  "field_mappings": {
18    "organization_defined_targets": {
19      "string": {}
20    },
21    "linked_account_defined_targets": {
22      "string": {}
23    }
24  },
25  "remote_data": [
26    {
27      "path": "string",
28      "data": {}
29    }
30  ]
31}
Was this page helpful?
Previous

/employer-benefits/{id}

Next

/employments

The Employment object is used to represent a job position at a company.

If an integration supports historical tracking of employments, it will be reflected in the data. If not, a new Employment object will be created whenever there is a change in job title or pay. The effective_date field should be used to order Employment objects, with the most recent date corresponding to the latest employment record for an employee.

idstringOptionalRead-onlyformat: "uuid"
remote_idstring or nullOptional
created_atdatetimeOptionalRead-only
The datetime that this object was created by Merge.
modified_atdatetimeOptionalRead-only
The datetime that this object was modified by Merge.
employeestring or nullOptionalformat: "uuid"
The employee holding this position.
job_titlestring or nullOptional
The position's title.
pay_ratedouble or nullOptional
The position's pay rate.
pay_periodenum or nullOptional
The time period this pay rate encompasses.
pay_frequencyenum or nullOptional
The position's pay frequency.
pay_currencyenum or nullOptional
The position's currency code. The currency code in ISO 4217 format.
pay_groupstring or nullOptionalformat: "uuid"
The employment's pay group
flsa_statusenum or nullOptional
The position's FLSA status.
Allowed values:
effective_datedatetime or nullOptional
The position's effective date.
employment_typeenum or nullOptional
The position's type of employment.
Allowed values:
remote_was_deletedbooleanOptionalRead-only
field_mappingsobject or nullOptionalRead-only
remote_datalist of objects or nullOptionalRead-only