This feature is only available to customers on our Professional or Enterprise plans. View the Merge Plans to learn more.
Send POST requests to the URL below with the required body parameters to create a Passthrough Requests.
Replace CATEGORY in the URL with hris, ats, accounting, ticketing, crm, mktg, or filestorage depending on the relevant category you’re making an API request to.
Reference the integration’s API documentation to accurately fill out the body parameters for the specific Passthrough Request you’re looking to make.
Some third-party APIs require you to include credentials directly in the path or request body (data) when making Passthrough Requests to the third-party API on behalf of a linked account. You can securely access a linked account’s stored credentials programmatically by including variables in double brackets (e.g. {{USERNAME}}).
Below is the full list of variables available for use in Passthrough Requests:
This is an example request body that demonstrates how the API_URL_SUBDOMAIN variable can be used for Passthrough Requests to Paylocity’s API.
Some third-party APIs require you to encode credentials using Base64 encoding. You can specify what needs to be encoded into Base64 format in your third-party request by wrapping that content between {BASE-64} tags in the passthrough request body.
This is an example request body that demonstrates how the BASE-64 method can be used for Passthrough Requests to Workday’s API.
See below for an example of how to create an authenticated Passthrough Request with Merge’s SDK:
The response to your query will look like the following:
The Passthrough Request endpoint will return a 408 status if there is a timeout in getting the response. If you have experienced delays or timeouts with normal Passthrough Requests we recommend switching to use Merge’s Async Passthrough requests.