Detailed Error Messaging

What is Detailed Error Messaging and where is it supported?

Yash Gogri avatar
Written by Yash Gogri
Updated over a week ago

Merge now offers Detailed Error Messaging to provide to provide guidance to both you and your end-users on resolving any errors that come up, whether it's during Authentication in Merge Link, or at a later time.

Please check out our 3 Minute Demo below!

Merge Link

When your end-user does through Merge Link to authenticate their account, we will run a check to identify 1) if the Credentials are Valid, and 2) if the API Credentials have provided proper permissions to access the information required by the Merge customer (respecting scopes).

In the example below, an end-user who had valid credentials, and provided API Access to the endpoints in which we interact with for Employee, Employment, Location, Team, Group.

The API Credentials did not have access the endpoint for Time-Off, so we surfaced the exact directions your end-user needs to complete to remediate this issue!

Issues Dashboard / API

End-users can also make changes to their API Access after the point of linking, and we also want your CSM's to surface detailed remediation steps back to your customers. The Issues Dashboard will have these detailed remediation steps under "Description". The Issues API will also have the detailed error messaging under "Error Details". You can send these messages right back to your customers to remediate any Issues that get generated!

Below are the Integrations in which we currently have support for Detailed Error Messaging for:


  • BambooHR

  • Hibob

  • Trinet

  • UKG Pro

  • UKG Ready

  • Paylocity

  • Workday

  • SAP Successfactors

  • Zenefits

  • Namely

  • Paychex

  • Ceridian Dayforce

  • Personio

  • Humaans


  • Lever

  • Greenhouse

We're continuing to add Detailed Error Messaging on an Integration by Integration basis.

If there are any integrations that are top of mind for you, or if you have any questions, please reach out to us at [email protected]!

Did this answer your question?