capabilities.work

Ticketing Link an Account

A 3-step recipe with Merge. We can help you get access.

Recipe · 3 steps

Ticketing Link an Account

with Merge

Link a new end user to a ticketing platform and obtain a usable account token.

  1. Create a single-use Link token scoped to the ticketing category from the end user's identifying details.
  2. Exchange the public token returned by the Merge Link frontend flow for a durable account token used on all subsequent data requests.
  3. Read the linked account details to confirm the integration completed and surface the connected ticketing platform.
What you'll need to have ready
  • authorization: Production access token with the required "Bearer " prefix.
  • endUserEmailAddress: The end user's email address, used purely for identification.
  • endUserOrganizationName: The end user's organization name.
  • endUserOriginId: A unique identifier for the end user in your own database.
  • publicToken: The public token returned by the Merge Link frontend after the user finishes linking.
For your developer

Arazzo workflow merge:link-ticketing-account, 3 operations: {$sourceDescriptions.subpackageLinktokenApi.url}#/paths/~1ticketing~1v1~1link-token/post → {$sourceDescriptions.subpackageAccounttokenApi.url}#/paths/~1ticketing~1v1~1account-token~1{public_token}/get → {$sourceDescriptions.subpackageAccountdetailsApi.url}#/paths/~1ticketing~1v1~1account-details/get. Specs on APIs.io.

More recipes with Merge

Accounting Bulk Create Expenses and Poll the BatchAccounting Bill a CustomerAccounting Link an AccountATS Advance an Application StageATS Add a Candidate and ApplicationATS Link an AccountCRM Create an Account with a ContactCRM Open an OpportunityCRM Link an AccountCRM Log an Engagement on a Contact