Source Organizations can create Share Tokens to share end user data with data sharing partners (Destination Organizations). Destination Organizations can use Share Tokens to copy and verify the end user’s data.
Source Organizations can create Share Tokens via API, Dashboard, or Workflows.
To create a Share Token via API, the Source Organization provides the Connection ID and a Source ID. The connection-id specifies which partner organization can access the specified source-id, and only that partner organization is able to redeem the created Share Token. The source-id can be an Inquiry, Transaction, or Account ID (e.g., inq_ABC123, txn_ABC123, or act_ABC123).
Use expires-in-seconds to set a TTL for Share Tokens, between 1 minute and
21 days. When omitted, Share Tokens default to expiring 14 days after
creation.
Source Organizations can also create Share Tokens using their Dashboard under the Connect > Share Tokens page. This can be helpful for testing and one-off data shares. Creating the Share Token requires selecting a Connection and providing a Source ID (an Inquiry, Transaction, or Account ID). Only the specified Destination Organization will be able to redeem the Share Token.

Source Organizations can use Workflows to automate Share Token creation. For example, the Source Organization can use a Workflow to automatically create a Share Token upon Inquiry completion. Similarly, the Destination Organization can use a Workflow to automatically redeem the created Share Token. This can be helpful for integrating into Connect with minimal development work.

After creating a Share Token, the Source Organization can send it to the Destination Organization using the Destination Organization’s API or SDK, or another secure channel. Alternatively, the Destination Organization can use a Workflow to automatically get notified about and redeem Share Tokens when they are created.
Source Organizations receive the following events related to Share Tokens. These events can be used to trigger Webhooks and Workflows.
connect/share-token.outbound-created — Occurs in the Source Organization when it creates a Share Token for a Destination Organization. Use this event to confirm creation and notify downstream systems.connect/share-token.outbound-redeemed — Occurs in the Source Organization when the Destination Organization’s Share Token redemption has finished. At this point, the Share Token’s status is redeemed.