Who offers it?
Seller
The party that owns or offers the inventory: a dealer, retailer, brand, auction house, or private seller.
Data Standards
Clear identity. Attributable evidence. Comparable offers.
This technical reference describes the information model used to evaluate partner data. Interface-specific schemas and transport details can be agreed per integration.
Back to PartnersCanonical identity
The reference is the organizing anchor.
Listings and source identifiers change. A stable canonical identity allows observations from different sources and times to remain comparable without assuming every listing represents the same object.
BrandCollectionModelReferenceVariant
Integration vocabulary
Seller is not channel is not source.
These roles can coincide, but they answer different questions. Preserving the distinction supports attribution, licensing, deduplication, seller evaluation, and meaningful comparison.
Where is it offered?
Sales channel
The venue where the collector can transact: a dealer website, marketplace, auction platform, showroom, or private market.
How did we learn?
Source
The route through which Standard Time Labs learned about the offer: an API, affiliate feed, direct partner feed, licensed provider, or other permitted input.
Example
A dealer may be the seller, a marketplace the sales channel, and the marketplace's approved API the source.
Useful integration fields
Context makes offers comparable.
No single source must provide every field. Reliable, attributable signals are most useful when they improve identity, availability, economics, and the collector's understanding of transaction terms.
Identity
- Manufacturer reference
- Model and variant
- Structured attributes
- Source identifiers
Offer
- Seller
- Sales channel
- Condition
- Availability
Economics
- Price and currency
- Shipping
- Geography
- Known fees
Terms
- Warranty
- Returns
- Fulfillment
- Membership requirements
Evidence
- Observation timestamp
- Update timestamp
- Provenance
- Usage and retention rights
Evidence controls
Useful data still needs boundaries.
Preserve provenance
Source, source identifiers, timestamps, and relevant usage terms should remain traceable through normalization.
Retain history where permitted
Price and availability changes should not blindly erase earlier observations when applicable rights allow historical retention.
Gate low-confidence matches
Incomplete or fuzzy identity evidence can support investigation, but it must not silently drive high-confidence alerts, assignments, or recommendations.
Technical conversation
Have a feed, API, catalog, or sample data set to evaluate?
A small representative sample is enough to discuss identity quality, available fields, rights, update cadence, and technical fit.