Skip to content

Glossary · 2026-11-05

sellers.json: definition and how it works in advertising

sellers.json is a public file where ad exchanges and SSPs list the sellers they represent. Learn the fields, a worked example, and how buyers check it.

Every SSP and ad exchange that follows the IAB Tech Lab standard posts a public file called sellers.json at the root of its domain (for example, exchange.com/sellers.json). The file lists each seller account the exchange works with, who gets paid for that inventory, and whether that company is the publisher or an intermediary.

Buyers compare it with a publisher's ads.txt file to confirm who they are buying from.

What sellers.json means

Think of it as a list of who an ad exchange sells for. sellers.json is a JSON file posted by supply-side platforms (SSPs) and exchanges that names the company behind every seller account in their system. When you buy an ad programmatically, the bid request reaches you with an account ID. The file tells you whose account that is.

The IAB Tech Lab created it so buyers could find out which companies are direct sellers of an ad opportunity and which ones are intermediaries reselling it. The spec was part of a broader effort to stop anyone from profiting from counterfeit inventory, meaning ad space that claims to be on one site or app but isn't. The Tech Lab put out a draft for public comment in April 2019 (IAB Tech Lab). As InMobi's explainer on ads.txt vs sellers.json puts it, ads.txt is a publisher initiative, while sellers.json gives SSPs and exchanges a way to add their own transparency.

How sellers.json works with ads.txt and the SupplyChain object

sellers.json rarely works alone. Buyers combine it with two other standards, and each comes from a different party in the chain.

ads.txt (Authorized Digital Sellers) is published by the publisher on its own domain. It lists the ad systems and account IDs allowed to sell its inventory. The IAB Tech Lab notes on its ads.txt and app-ads.txt page that all of its supply chain validation specs, including sellers.json, now live in one GitHub repository.

The seller file itself is published by the SSP or exchange at /sellers.json on its root domain. It names the legal entity behind each seller ID.

The SupplyChain object (often shortened to schain) travels inside each bid request. It holds one node per company that sold or resold that specific impression, and each node records the ad system's domain and the seller ID it used. Each company that handles the request adds its own node without changing the ones before it, and marks the chain incomplete if it didn't receive upstream information.

The IAB Tech Lab's OpenRTB Working Group finalized sellers.json and the SupplyChain object for industry adoption on July 31, 2019. One practical benefit of a lookup file: buyers can fetch and cache seller identities ahead of time, so less data has to ride along with every bid request.

StandardWho publishes itWhere it livesQuestion it answers
ads.txt / app-ads.txtPublisherpublisher.com/ads.txtWho is allowed to sell my inventory?
sellers.jsonSSP or exchangeexchange.com/sellers.jsonWhich company is behind this seller ID?
SupplyChain objectEvery paid party in the requestInside the bid requestWho touched this impression on its way to me?

The fields in a sellers.json entry

The file has a top-level object with contact details and a version number, then a list of sellers. Equativ's sellers.json documentation walks through the fields in each seller entry:

  • seller_id: the account ID in that ad system. It matches field 2 (the publisher's account ID) in the publisher's ads.txt line and the sid value in the SupplyChain node.
  • name: the company that is paid for inventory sold under that seller_id.
  • domain: the business domain of that company.
  • seller_type: PUBLISHER if the seller owns and operates the site or app, INTERMEDIARY if it doesn't, or BOTH if it sells some of each.
  • is_confidential: 0 if the seller's identity is public, 1 if it is confidential.

The specification also sets the delivery rules: the file must be reachable over HTTP or HTTPS at the path /sellers.json on the ad system's domain, served with the Content-Type: application/json header.

Worked example: tracing one impression

Here is one made-up impression, using the sample seller entry from the Equativ documentation: seller_id 1234, name mypublisher, domain mypublisher.com, seller_type PUBLISHER, is_confidential 0. The exchange domain below is a placeholder.

  1. A bid request arrives. Its SupplyChain object has one node, with asi set to exchange.com and sid set to 1234, and the chain is marked complete (complete: 1).
  2. You open exchange.com/sellers.json and search for 1234. The entry names mypublisher, domain mypublisher.com, seller type PUBLISHER, not confidential.
  3. You open mypublisher.com/ads.txt and look for a line that lists exchange.com with account ID 1234 and the relationship DIRECT.
  4. All three records agree: the exchange says account 1234 belongs to mypublisher, the publisher says that same account may sell its inventory directly, and the bid request shows one hop. This is a short, verifiable path.

Now change the facts. The same request arrives with a second node naming a reseller's domain and a different seller ID. You look that ID up in the reseller's own sellers.json file and it isn't there. Or the chain shows complete: 0, which means at least one company upstream didn't pass along its information. In both cases you can't confirm who you'd be paying. Buyers who check this often lower the bid on paths like this or skip them.

What sellers.json does not tell you

An entry in the file proves a relationship existed when it was last updated. It doesn't prove the inventory is live, available, or still sold through that account. Files go stale when publishers and exchanges stop working together and nobody removes the line.

The domain field can also be blank. It may be left out when is_confidential is set to 1, or when the seller has no web presence, so some entries tell you an account exists without telling you who owns it.

Maintenance is the ongoing problem. Verve wrote in 2025 that outdated or incomplete files still cost publishers revenue and waste advertiser spend, even though these standards are now baseline expectations for buyers.

The file identifies accounts, not transactions. To see every company involved in one specific impression you need the SupplyChain object, and even then you're relying on each party to fill in its node honestly. sellers.json makes fraud harder to hide, but it doesn't guarantee clean inventory.

Why sellers.json matters to advertisers

For a buyer, these files answer a basic question: who is getting my money? With ads.txt, sellers.json and the SupplyChain object together, you can verify that every seller in a path is authorized, spot paths that run through several resellers, and lower the risk of paying for unauthorized or spoofed inventory. Cutting those long paths in favor of short, direct ones is the core of supply path optimization explained in our glossary.

The industry checks these files too. Under its Supply Chain Validation program (version 1.0, released May 2021), the IAB Tech Lab runs a weekly, unannounced automated check of publishers' ads.txt and app-ads.txt files and the sellers.json files of the sellers they reference. For each DIRECT line, it checks whether the seller's file lists the publisher's account ID, and it emails publishers whose entries come back in an error or alert state.

You don't have to read JSON files by hand to benefit. On the Waveband DSP, ads.txt-only supply is on by default, so campaigns buy only from sellers the publisher has authorized. You can tighten things further with exchange allow and block lists and domain and app allow and block lists on each line item. If you're comparing tools, our guide to choosing a self-serve CTV platform covers which supply controls to look for.

Frequently asked questions about sellers.json

Who has to publish a sellers.json file?

SSPs, ad exchanges and other intermediaries that sell or resell ad inventory publish sellers.json. Publishers don't need one for their own sites; they publish ads.txt (or app-ads.txt for apps and streaming TV apps) instead.

How do I view an exchange's sellers.json?

Add /sellers.json to the end of the exchange's root domain in your browser, the same way you'd open a publisher's ads.txt. The file is public, so anyone can read it.

What is the difference between sellers.json and ads.txt?

ads.txt is the publisher's list of companies authorized to sell its inventory. The seller file is the seller's list of the accounts it represents and who owns them. InMobi sums up the pairing this way: combined, they let buyers identify the final seller of a bid request and let publishers check whether an SSP is falsely claiming to represent them.

Related glossary terms

  • Supply path optimization: choosing the shortest, most direct routes to inventory. See our SPO definition.
  • ads.txt: the publisher's public list of authorized sellers.
  • app-ads.txt: the version of ads.txt for mobile and connected TV apps.
  • SSP: the supply-side platform that sells a publisher's inventory and posts the sellers.json file.
  • Real-time bidding: the auction in which each bid request, and its SupplyChain object, reaches buyers.

Browse more terms in our full ad-tech glossary.

See how it works in Waveband

By Waveband Team