The Store is Deck’s persistent memory. It captures and organizes everything Jobs produce — not just during a single session, but across all sessions and all connections related to an end-user or entity. It’s the place where developers retrieve the actual value generated by their Jobs.

​
Structure of the Store

  • Entity-centric: All data is indexed by the real-world entities that Jobs act on (e.g. accounts, locations, meters)
  • Time-aware: Every output is timestamped and stored with Job lineage
  • Job-aware: You can query data from a specific Job or across Jobs of a given type

​
Why It Matters

  • Stability across connections: Even if credentials change or expire, data remains linked to the same account or entity
  • Structured access: Developers can query the Store via simple API endpoints — by account, Job type, or time range
  • Enables product logic: Timelines, dashboards, monitoring, history comparisons, and more

​
What Lives in the Store

  • Documents — statements, confirmations, exports
  • Normalized records — balances, usage, payments, statuses
  • Messages — confirmations, error logs, or audit trails

​
When to Use the Store

Typically, when an agent extracts data from a website, that data is returned as JSON via a webhook. However, when the volume of data is too large for a webhook payload, the data is written to a CSV file and saved to the Store. In such cases:
  1. The webhook returns a URL pointing to a document filtered specifically for the data extracted.
  2. This document list can be accessed via the /jobs/documents/list endpoint.
  3. Each document includes a document ID, which can be used to download the file from /jobs/documents/file.
This mechanism ensures large or structured results are preserved, retrievable, and accessible in a consistent and scalable way.