Source Systems & Freshness
Technical reference for DataHawk source systems, schemas, account requirements, and freshness fields.
Use this page when you need to map a business data type to its source API, account requirement, schema, or freshness field. For a business-friendly explanation of public vs. private data, see How DataHawk Sources Your Data.
Schema mapping by data type
DataHawk organizes datasets into schemas based on source system and modeling layer.
| Data type | Primary schemas | Account required |
|---|---|---|
| Product listings, prices, Buy Box, sales estimates | PRODUCT, MARKET, REPORTS | No account connection for tracked public data |
| Keyword rankings and search volume | SEO, REPORTS | No account connection, but keyword tracking is required |
| Category and market data | MARKET, REPORTS | No account connection, but category tracking is required |
| Seller orders, finance, fees, profit, returns | FINANCE, SELLING_PARTNER | Seller Central account |
| Inventory and FBA movement data | SELLING_PARTNER, RAW_INVENTORY | Seller Central account |
| Vendor sales, inventory, and purchase-order data | SELLING_PARTNER, REPORTS | Vendor Central account |
| Amazon and Walmart advertising | ADVERTISING | Advertising account |
| Marketplace, account, currency, and tracked-entity references | REFERENTIAL | Varies by table |
For the full schema map, see Technical Reference.
Data history and refresh by channel
Two different questions get confused often: "how far back does my history go" (how much data DataHawk retrieves when you first connect) and "how long until I see any data" (the processing time before that historical data appears at all, roughly 24 hours for any source — see Before Starting). The table below answers the first question.
| Channel | Historical backfill on connection | Refresh frequency | Typical delay on recent data |
|---|---|---|---|
| Seller | Up to 2 years | Daily | Latest 48 hours may be incomplete. See Seller account setup. |
| Vendor | Up to 3 years | Daily | About 72 hours (roughly 3 days), due to Amazon API limitations. Demand Forecasts specifically refresh weekly, not daily. See Vendor account setup. |
| Advertising | Up to 60 days (the maximum Amazon's Ads API allows) | Daily | Latest 24–48 hours may still be incomplete while Amazon finishes processing. See Advertising account setup. |
Regardless of channel, DataHawk keeps accumulating history day by day after connection, so your usable history grows past the initial backfill the longer you stay connected.
Source systems
| Source system | What DataHawk collects |
|---|---|
| Amazon public storefront | Product attributes, pricing, BSR, offers, category rank, and search visibility signals |
| Amazon Selling Partner API (SP-API) | Seller, Vendor, inventory, finance, returns, replenishment, and Brand Analytics reports |
| Amazon Advertising API | Sponsored Ads and DSP performance data |
| Walmart Marketplace API | Walmart Marketplace seller data |
| Walmart Connect API | Walmart advertising performance data |
| DataHawk collection and modeling layer | Sales estimates, competitor detection, listing quality analysis, keyword research, and curated report tables |
Freshness and delay fields
Many tables expose one or more fields that help you determine whether a row is current, historical, or recently refreshed.
| Field pattern | Typical use |
|---|---|
DATE_DAY / OBSERVATION_DATE | Business date represented by the row |
OBSERVATION_TIME | Timestamp of a collected snapshot when more precision is available |
UPDATED_AT | Time when the row was last updated in DataHawk |
TIME_INTERVAL_START_DATE / TIME_INTERVAL_END_DATE | Start and end of an aggregated period |
REPORTING_DATE / report date fields | Source-report date from Amazon or Walmart |
For current-state tables such as inventory or listing snapshots, filter to the latest available date instead of querying all history. For event or ledger tables, use the business date and transaction status fields documented in the relevant dataset page.