Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetching a category agnostic link token #32

Open
terratrue-daniel opened this issue Feb 1, 2024 · 1 comment
Open

Fetching a category agnostic link token #32

terratrue-daniel opened this issue Feb 1, 2024 · 1 comment

Comments

@terratrue-daniel
Copy link

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:

LinkToken linkToken = mergeClient.ats().linkToken().create(EndUserDetailsRequest.builder()
    .endUserEmailAddress("[email protected]")
    .endUserOrganizationName("acme")
    .endUserOriginId("1234")
    .categories(List.of(CategoriesEnum.ATS))
    .build());

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.

@dsinghvi
Copy link
Collaborator

@rmkonnur do you have any insight here -- it sounds like there should be a non-category specific endpoint for create-link-token ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants