Introducing requested data in Merge Link

Whether it's personally identifiable information (like a social security number or home address) or more general info like first name/last name, one thing holds true for your product: your users trust you with a lot of data.

Merge now allows you to display requested data from inside of Merge Link.

Read on to learn about our latest update to Merge Link, and how you can display requested data in your product’s linking flow.

Why we display requested data in Merge Link

Transparency is a core tenant at Merge.

Earlier this year, we released Scopes to let you define exactly which models and fields Merge accessed when pulling user data. Scopes allowed you to assure your customers you only process the data you absolutely needed.

Now, by displaying requested data in Merge Link you can be as transparent as possible to your users about how you use their data.

With a flip of a switch, you can accurately display the data models and fields you request from your users. Merge displays this on two levels:

  1. The fields are requested from a specific integration. This is completely dynamic: if an integration doesn’t have a common model field represented, then it won’t be displayed.
  2. The data model and field scope settings that the customer is using.

Want to get started?

In your Merge portal, head to Configuration > Common Models > Settings.

Enable the “Show Requested Data Screen In Linking Flow” setting by flipping the toggle.

And that’s it! You’re now able to have Merge Link display the data you're requesting from your users!

But Merge isn’t just a Unified 
API product. Merge is an integration platform to also manage customer integrations.  gradient text
“It was the same process, go talk to their team, figure out their API. It was taking a lot of time. And then before we knew it, there was a laundry list of HR integrations being requested for our prospects and customers.” gradient text
“It was the same process, go talk to their team, figure out their API. It was taking a lot of time. And then before we knew it, there was a laundry list of HR integrations being requested for our prospects and customers.” gradient text
“It was the same process, go talk to their team, figure out their API. It was taking a lot of time. And then before we knew it, there was a laundry list of HR integrations being requested for our prospects and customers.” gradient text

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6
“It was the same process, go talk to their team, figure out their API. It was taking a lot of time. And then before we knew it, there was a laundry list of HR integrations being requested for our prospects and customers.”

Daniel Marashlian - Co-Founder & CTO

This is a link inside of a rich text

  • List item
  • List item
  • List item
  1. List item
  2. List item
  3. List item
Caption goes here
This is some text inside of a div block.
Table of contents
Add hundreds of integrations to your product through Merge’s Unified API
Get a demo
Just for you

Introducing requested data in Merge Link

Fed Finjap
@Merge

Whether it's personally identifiable information (like a social security number or home address) or more general info like first name/last name, one thing holds true for your product: your users trust you with a lot of data.

Merge now allows you to display requested data from inside of Merge Link.

Read on to learn about our latest update to Merge Link, and how you can display requested data in your product’s linking flow.

Why we display requested data in Merge Link

Transparency is a core tenant at Merge.

Earlier this year, we released Scopes to let you define exactly which models and fields Merge accessed when pulling user data. Scopes allowed you to assure your customers you only process the data you absolutely needed.

Now, by displaying requested data in Merge Link you can be as transparent as possible to your users about how you use their data.

With a flip of a switch, you can accurately display the data models and fields you request from your users. Merge displays this on two levels:

  1. The fields are requested from a specific integration. This is completely dynamic: if an integration doesn’t have a common model field represented, then it won’t be displayed.
  2. The data model and field scope settings that the customer is using.

Want to get started?

In your Merge portal, head to Configuration > Common Models > Settings.

Enable the “Show Requested Data Screen In Linking Flow” setting by flipping the toggle.

And that’s it! You’re now able to have Merge Link display the data you're requesting from your users!

“It was the same process, go talk to their team, figure out their API. It was taking a lot of time. And then before we knew it, there was a laundry list of HR integrations being requested for our prospects and customers.”

Name
Position
Fed Finjap
@Merge

Read more

6 ways we’ve elevated our accounting integrations

Product

Merge now lets you add candidates AND applications to customers’ ATS applications with a single endpoint!

Product

How Merge SFTP enables your customers to easily sync file-based reports with your product 

Product

Subscribe to the Merge Blog

Subscribe to the Merge Blog

Subscribe

Make integrations your competitive advantage

Stay in touch to learn how Merge can unlock hundreds of integrations in days, not years

Get a demo

Make integrations your competitive advantage

Stay in touch to learn how Merge can unlock hundreds of integrations in days, not years

Get a demo