All Collections
Supplemental Data
Different Types of Supplemental Data
Different Types of Supplemental Data

Information on the difference between Remote Data, Passthrough Requests, and Field Mappings.

Pritak Patel avatar
Written by Pritak Patel
Updated over a week ago


Merge supports different types of supplemental data in case you need more information from the third-party apart from what's available through our Common Models. While we aim to standardize data across multiple platforms as much as possible, there might be cases where you might need additional modification. We've accounted for this through our multiple supplemental data sources!

Supplemental Data Types

Remote Data is most helpful to use when you're looking for data that is part of an endpoint that Merge does call. If you need an extra field specific to an integration's standard response that is not included in Merge’s standardized format, utilizing remote data will help you avoid an additional API request to the integration platform.

If you're looking for data from an endpoint that Merge does not make requests to, we suggest creating an Authenticated Passthrough Request. These requests are sent directly to an integration's API and follow each integration's specific API format instead of Merge's unified format. This approach is ideal for when you're looking to fetch data not included in Merge's common models.

Merge also allows you to create Field Mappings to map custom fields and other non-mapped data from your users' platforms to target fields on your Merge Common Models. Viewable in the Advanced section of the Merge Dashboard, you or your end users can create Integration, Organization, or Linked Account Level Field Mappings.

Below is a quickstart video to learn more about the feature. Field Mappings is offered to customers on our Professional or Enterprise plans, and requires remote_data to be enabled.

Remote Fields is a feature that you should use if you wish to access standardized metadata about the information included in Remote Data, push values for custom fields back to an end users’ platform, or pull custom fields back in a standardized way. Standardized metadata in Remote Fields includes information such as field type (string, bool, number, etc.), string formats, available options, display name, and whether or not the field is custom to an account or standard to the 3rd party.

Did this answer your question?