Issues

Merge opens an Issue when requests to a third party start failing in a way that someone has to act on, most often expired credentials or a permission the end user never granted. One Issue covers one problem on one Linked Account, so repeated failures of the same kind update the existing Issue rather than piling up new ones.

Because resolution waits out that day, a connection that has just been fixed can still show an ongoing Issue for a while.

error_description is a short label for the failure, such as Invalid login credentials, Missing permission, or Expired multi-factor authentication, and error_details lists the specific requests or scopes involved. Linked Accounts that Merge syncs from report files instead of an API carry descriptions about the file, such as Unrecognized file name.

Most of what a developer needs from Issues arrives without polling. The Linked Account issues webhook delivers Issue.new, Issue.reopened, Issue.muted, and Issue.resolved, which is enough to keep a connection-health indicator in your own product accurate. Use the endpoints below to backfill state, to reconcile after downtime, or to show the current issue list for one Linked Account with the linked_account_id filter.

Mute an Issue you have decided not to act on from the Issues page in your dashboard. Muted issues stay out of GET /issues unless you pass include_muted=true, and muting emits Issue.muted with is_muted set to true in the payload.