Skip to main content
Use the @bijection/connectors/plaid entrypoint to declare Plaid resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Transactions

sync: Page-set sync with stated coverage and verified webhook hints

The following example matches configuration webhooks.

Configuration: standard

Case: plaid/transactions/sync/standard. Connection and resource configuration are declared by this exact case. Credential kind: plaid. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: transactions
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: plaid/transactions/sync/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: plaid. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: transactions
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a plaid credential (plaid.credential): a body_fields envelope carrying client_id, secret and the Item’s access_token, which the host writes into every request body at dispatch. Identity is the Item’s item_id from POST /item/get. environment selects https://sandbox.plaid.com or https://production.plaid.com. transactions.sync reads POST /transactions/sync as an incremental snapshot of one Item, 100 transactions per page:
  • The resume position advances per page set. has_more says whether next_cursor continues this pass or is the position the next pass resumes from. TRANSACTIONS_SYNC_MUTATION_DURING_PAGINATION discards the pass’s staged pages and restarts it from the cursor it began at.
  • The record key is a function of the record: a posted transaction is keyed by the pending_transaction_id it settled from, otherwise by its own transaction_id. A settlement (removed names the pending id, added carries the posted one) is one record changing state. A removal is provisional until the pass is consumed: a presence for the same key anywhere in the pass supersedes it.
  • transactions_update_status is read on every page. INITIAL_UPDATE_COMPLETE publishes rows without a population certificate, HISTORICAL_UPDATE_COMPLETE with one, and NOT_READY is a declared unavailability that publishes nothing.
  • ITEM_LOGIN_REQUIRED and INVALID_ACCESS_TOKEN fail as authentication; PRODUCT_NOT_READY as unavailable.
Known limits. A removal of a posted transaction that settled from a pending one names the posted id, which is not the record’s key, so it withdraws nothing and the record stays until the Item is re-read from no cursor. amount is a JSON double kept as the shortest text that round-trips it, not an exact decimal. A pass reads at most 1,024 pages, so an Item above 102,400 transactions cannot complete a first pass. With updates: "webhooks", a delivery verified as an ES256 JWS in Plaid-Verification (key fetched per kid from POST /webhook_verification_key/get, retired keys refused, body digest claim request_body_sha256, five-minute iat bound) requests another pass. The key request carries the connection’s body fields; whether Plaid accepts access_token beside key_id there has not been observed. Nothing here has run against Plaid or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.