You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to Merge's documentation, there is a way of fetching a category agnostic link token from this endpoint: https://api.merge.dev/api/integrations/create-link-token
In this SDK, it seems that you are forced to select a category specific client client (ats(), accounting(), etc.) in order to fetch a link token. E.g. From the README:
And that link token is fetched from a different endpoint: <base_url>api/ats/v1/link-token
Is there a way to fetch a category agnostic link token so that Merge Link can be powered? Otherwise we would have to create custom UI to figure out what category the user would like to create the link for, then fetch the link token for that category, then use that to power Merge Link.
Ideally we would fetch a link token that's not tied to a category, and use that to power the Merge Link UI component without going through the first step.
The text was updated successfully, but these errors were encountered:
According to Merge's documentation, there is a way of fetching a category agnostic link token from this endpoint:
https://api.merge.dev/api/integrations/create-link-token
In this SDK, it seems that you are forced to select a category specific client client (
ats()
,accounting()
, etc.) in order to fetch a link token. E.g. From the README:And that link token is fetched from a different endpoint:
<base_url>api/ats/v1/link-token
Is there a way to fetch a category agnostic link token so that Merge Link can be powered? Otherwise we would have to create custom UI to figure out what category the user would like to create the link for, then fetch the link token for that category, then use that to power Merge Link.
Ideally we would fetch a link token that's not tied to a category, and use that to power the Merge Link UI component without going through the first step.
The text was updated successfully, but these errors were encountered: