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
  • Authentication
    • Merge Link
    • Prompt guide for Merge Link
    • Magic Link
    • Single integration
  • Reading data
    • Syncing best practices
  • Supplemental data
    • Overview
    • Remote Data
      • Remote Field Classes
      • Pulling data
      • Pushing data
    • Custom objects
  • Writing data
    • Overview
  • Platform and account metadata
    • Integration metadata
    • Linked Accounts
  • Testing
    • Testing Merge's Unified API via Postman
  • Specifications
    • Schema properties
    • Model Context Protocol (MCP)
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
On this page
  • Overview
  • How is this different from Remote Data and Field Mapping?
  • Supported categories
Supplemental dataRemote Field Classes

Remote Field Classes

Beta

Read and write non-mapped data in a standardized format via Merge’s Unified API.

Was this page helpful?
Previous

Async Passthrough

Next

Pulling Remote Field Classes

Built with

This feature is only available to customers on our Professional and Enterprise plans. View the Merge Plans to learn more.

Overview

Merge’s Remote Field Classes feature allows you to programmatically access additional fields that are not mapped to Merge’s Common Model fields. These non-mapped fields can be both standard fields on the third-party platform and custom fields on a Linked Account.

Remote Field Classes also surfaces metadata about each field, such as display name and type.

Merge will generally leave field values untouched, but will normalize values into a standardized format if necessary, such as DateTime fields.

How is this different from Remote Data and Field Mapping?

Remote Data is all the raw data from a model in the original format Merge received it in.

Field Mapping and Remote Field Classes both build on top of Remote Data to return fields in a normalized format:

  • Field Mapping is best for reading fields from the third-party by mapping them to a Merge Common Model
  • Remote Field Classes is best for accessing highly variable custom fields and writing those fields back to your users’ third-party platform

Supported categories

Remote Field Classes are currently available for:

  • Accounting Beta
  • CRM Beta
  • Ticketing Beta

Please reach out via our Product Feedback form if you are interested in other categories!