Update Lifecycle

pending -> in_progress -> completed
                       -> failed

Status	Description	What to do
`pending`	Request submitted, queued for processing.	Wait for webhook or poll.
`in_progress`	Method is actively retrieving data from the source.	Wait. Direct Updates typically complete within seconds to minutes depending on the institution.
`completed`	Data is available. The liability-type object (e.g., `credit_card`) is populated.	Read the data, update your local store, display to user.
`failed`	Retrieval was unsuccessful. The `error` object is populated with details.	See Handling Failures.

Snapshot Updates: Cannot be requested on demand. An update.snapshot subscription creates them when new bureau data is available. Retrieve them from the Updates list or from the path in the webhook.
Direct Updates: Asynchronous. Typical completion time varies by institution. Most complete within seconds, some may take up to a few minutes. Design your UI to show a loading state and handle the webhook.

Event	When it fires
`update.create`	An Update has been created (status: `pending`).
`update.update`	An Update’s status has changed (typically `pending` to `completed` or `pending` to `failed`).

Subscribe to update.update to react when data is ready. The webhook payload includes the path to retrieve the full Update object.

If you need to retry a failed Update, use idempotency keys to avoid creating duplicate requests.

​Update Lifecycle