Seller.json Lookup
Fetch a live seller.json file and search for specific seller IDs, names, or domains when supply-path questions depend on locating the exact record fast.
Search seller.json for a seller ID or name instead of scanning a huge file manually.
What you can do here
- Look up a seller ID from a buyer audit.
- Check whether a named reseller appears in seller.json.
- Confirm the entity behind a seller-domain record.
Before you start
- Provide a public seller.json domain and a search term.
About Seller.json Lookup
The Seller.json Lookup fetches a live seller file and filters the seller records by seller ID, name, or domain so support and ad ops teams can locate the right entity quickly.
Use it during onboarding, audits, or buyer escalations when a specific seller record matters more than a top-level file summary.
Best uses for Seller.json Lookup
- Look up a seller ID from a buyer audit.
- Check whether a named reseller appears in seller.json.
- Confirm the entity behind a seller-domain record.
How to use Seller.json Lookup
- Enter an SSP or exchange domain.
- Provide a seller ID, name, or domain fragment.
- Review the matching seller records.
What to paste in
- Provide a public seller.json domain and a search term.
What you should see
- Matching seller records with seller ID, type, and domain details.
Example checks
These are simple checks you can run when you want a real sample and a clear result to compare against.
Provide a public seller.json domain and a search term.
Why run it: Look up a seller ID from a buyer audit.
What to look for: Matching seller records with seller ID, type, and domain details.
Finding the Right Seller Record in Large Seller Files
Why seller lookup is a different job from seller inspection
A broad seller.json inspection tells you whether the file looks healthy overall. Seller lookup solves a different problem. It answers the urgent question of where a specific seller ID, name, or domain appears inside the file when a ticket or audit depends on one record.
That distinction matters because large seller files are not pleasant to search manually. During onboarding, buyer questions, or support escalations, teams often know the identifier they care about before they care about the whole file summary. A lookup tool makes that the starting point.
This is exactly the type of narrow debugging workflow a niche site should target. It is operationally real and much closer to what searchers actually need.
How targeted lookup improves supply-path work
Lookup makes seller-file evidence easier to use in conversations. A buyer ticket may name a seller ID. A publisher review may start from a domain. An onboarding note may reference a reseller name. Instead of scanning a giant file, the team can fetch the live metadata and search directly for the matching records.
That shortens the path to an actionable answer. Once the record is found, teams can compare its seller type, domain, and completeness against the commercial question in front of them.
It also pairs naturally with the broader seller inspector. One tool gives the file-level picture, the other gives the record-level answer. Together they make seller.json much easier to use in production support workflows.
Why this belongs in the ads.txt cluster
Seller lookup supports the same supply-path and authorization questions that start in ads.txt. Ads.txt tells the market who is authorized. Seller.json helps explain who those entities are. A lookup workflow makes that second step faster when one specific seller matters most.
From an SEO perspective, this is also a stronger niche target than a broad seller.json keyword. People searching for seller ID lookup or seller record search are much closer to a real operational task.
That is the core value: faster answers during audits and escalations, and a better bridge between seller IDs in the market and the public metadata that describes them.
Troubleshooting
What to look for
- Matching seller records with seller ID, type, and domain details.
Common issues
- No result does not always mean the commercial relationship is absent; public metadata may be incomplete.
- The search is text-based, so broad queries can return many records.
Best practices
- Include the full URL (with https://) for best results.
- If a fetch fails, confirm the endpoint is publicly reachable.
- Some hosts block automated requests; try a different URL if needed.
Related tools
More tools in the ads.txt category.
- Ads.txt Analyzer - Fetch a publisher's ads.txt file, verify that it exists, lint the syntax, and surface duplicate or missing seller signals that can confuse buyers. Built for publisher monetization teams and ad-ops engineers who need a fast first pass on seller-file health.
- Ads.txt Duplicate Seller Detector - Identify repeated exchange-domain and seller-ID pairs in ads.txt files, including conflicting DIRECT and RESELLER declarations that make publisher authorization harder to reason about.
- App-ads.txt Analyzer - Fetch a live app-ads.txt file from an app developer domain, lint the seller lines, and surface malformed or duplicate records before mobile monetization QA starts.
- Ads.txt Hosting Checker - Check where a publisher ads.txt request really resolves, whether the final host and path stay correct, and whether hosting or redirect behavior is likely to confuse crawlers or buyers.
Related reading
More specific pages for the exact jobs this tool supports.
Find a Specific Seller in Seller.json Fast
A narrow lookup workflow for large seller files and urgent seller-ID questions.
Find a Seller ID During a Buyer Ticket
A support-ticket workflow for seller ID lookups.
Search Seller.json by Domain Before an SPO Review
A domain-first workflow for seller-file research.
Locate Confidential Seller Neighbors in a Large Seller File
A contextual lookup workflow for opaque seller records.
Check Seller Name Matches Before Onboarding a Reseller
An onboarding workflow for seller-name verification.
Look Up Seller Records Before a Publisher Escalation
A publisher-escalation workflow for seller-file lookup.
Frequently asked questions
Is it free to use?
Yes. Core tools are free and accessible without signup.
Does it upload my data?
This tool makes server-side fetches to the URLs you provide so results can be rendered. We do not store the fetched content beyond the request.
What if I spot a bug?
Please reach out via the Contact page with a reproduction example.
How is this different from the Seller.json Inspector?
The inspector summarizes the file broadly; the lookup tool is optimized for finding one seller or a small set of related records quickly.
Can I search by seller ID or name?
Yes. The tool matches seller ID, seller name, and seller domain text.
Does it fetch the live file?
Yes. Provide a public SSP or exchange domain.
Helpful links
Standards & references
Official specs that inform how this tool interprets data.