Sellers.json is a public file that identifies the entities allowed to sell digital advertising inventory and shows how each participant fits into the supply chain. It gives buyers more visibility into who is involved in an impression path, supporting due diligence and helping detect unauthorized or misleading resale activity.
What Sellers.json Is For in Digital Advertising
Sellers.json is a transparency control for programmatic advertising. It helps buyers and intermediaries see which entities are authorized to sell inventory, how each participant fits in the supply chain, and whether a seller relationship is direct or indirect.
That visibility matters because ad inventory often moves through multiple platforms, exchanges, and resellers before a bid or impression is completed. A published seller roster gives the market a shared reference point for who is participating in the transaction path.
How Sellers.json Supports Supply-Chain Trust
The core value of Sellers.json is provenance. It does not guarantee that every impression is high quality, but it gives downstream buyers a way to compare declared sellers against known participants and to spot mismatches, opaque intermediaries, or relationships that deserve closer review.
In practical terms, the file supports due diligence by making supply-chain roles easier to inspect. That helps organizations distinguish between authorized resale, legitimate representation, and activity that may be unauthorized or misleading.
Why Buyers and Platforms Use It
Buyers use Sellers.json to reduce ambiguity in a fragmented marketplace. When multiple sellers or resellers touch the same inventory, the file provides context for commercial trust decisions, vendor review, and internal controls around approved supply paths.
Platforms use it to publish a stable, machine-readable view of seller identity and relationship status. That makes it easier for ecosystem participants to automate checks, compare records across partners, and maintain consistency as supply chains change over time.
Common Limitations and What It Does Not Do
Sellers.json is a visibility mechanism, not a guarantee of legitimacy. A seller can still be present in the file while inventory quality, transaction integrity, or business conduct varies, so the file should be treated as one input among several.
It also does not replace commercial verification, contract controls, or fraud detection. The practical benefit comes from combining published seller information with broader review of supply paths, payment relationships, and trafficking behavior.
Risk and Threat Considerations
When seller identity or supply-chain role is unclear, buyers can be exposed to unauthorized reselling, misrepresentation, and lower-value inventory that was not sourced through the intended channel. In digital advertising, that weakens trust in the transaction path and can undermine spend efficiency and brand controls.
Failure mechanism: A false, incomplete, or ignored seller record lets an intermediary appear legitimate while concealing where inventory actually came from or who benefits from the sale.
Impact: Buyers may pay for misrepresented inventory, lose visibility into upstream participants, and miss signs of inventory laundering or other fraudulent resale patterns.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OC-01 — Organizational Context | Sellers.json supports understanding supply-chain participants and business context. |
| GV.SC-04 — Cyber Supply Chain Risk Management | The file helps assess trust in third-party advertising supply paths. | |
| PR.AT-01 — Awareness and Training | Operators need to recognize what seller transparency data can and cannot prove. | |
| Recommendation — Document approved seller roles and use them in supply-chain governance reviews. Compare declared sellers against approved supply-chain relationships and exception records. Train buyers and operations staff to interpret seller records as one trust input. | ||
| ISO/IEC 27001:2022 | A.5.19 — Information security in supplier relationships | Seller transparency is part of managing supplier trust and oversight. |
| A.5.20 — Addressing information security within supplier agreements | Seller roles and resale expectations belong in contractual controls. | |
| Recommendation — Use supplier oversight checks to validate advertising intermediaries and resellers. Specify seller disclosure and resale requirements in partner agreements. | ||
Practitioner Guidance
What practitioners should watch for: Treat Sellers.json as a reconciliation input, not a standalone trust signal. The most useful operational question is whether the seller declared in the file matches the trading relationship and the inventory path seen elsewhere in the ecosystem.
Governance implication: Teams responsible for ad supply assurance should define who reviews seller records, what discrepancies trigger escalation, and how exceptions are documented so the control stays actionable rather than informational only.
Related resources from NHI Mgmt Group
- Why do marketplaces need fraud controls across both buyers and sellers?
- How should marketplaces reduce fake listings fraud without blocking legitimate sellers?
- What breaks when npm packages execute code through binding.gyp instead of package.json scripts?
- How should marketplaces handle fraud when sellers are independent merchants?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 26, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
