sellers.json Validator
Ek sellers.json document ko IAB Tech Lab spec ke against apne browser mein validate karein. Jo file aap paste karte hain woh aapke device par rehti hai.
sellers.json Validator poori tarah aapke browser mein chalta hai. Jo document aap paste karte hain woh aapke device par parse aur check hota hai aur kabhi ek URL se fetch ya ArrayKit ko upload nahi hota.
ads.txt Validator kholein
sellers.json Validator ke baare mein
sellers.json Validator ek IAB Tech Lab sellers.json document ko us pal lint karta hai jab aap use paste karte hain. Yeh required top-level version aur sellers[] array confirm karta hai, phir har seller entry par chalta hai: har ek ko ek seller_id chahiye jo file ke across unique ho aur ek seller_type jo PUBLISHER, INTERMEDIARY, ya BOTH (case-insensitive) ho. name aur domain required hain jab tak seller is_confidential mark na ho, aur is_passthrough ek clean boolean hona chahiye. Findings ek pass/fail verdict, per-seller error messages jo array index aur seller_id ke saath tagged hain, aur ek summary ke roop mein aate hain jo sellers ko type se plus confidential aur passthrough entries se ginti hai. Ad-ops aur supply-path teams apni ya ek partner ki file yahan audit karti hain bina use kisi third-party service ko POST kiye — sab kuch aapke device par chalta hai.
Features
- sellers.json spec ke hisaab se required top-level version aur sellers[] array check karta hai
- Verify karta hai ki har seller_id present aur file ke andar unique hai
- seller_type ko PUBLISHER, INTERMEDIARY, aur BOTH (case-insensitive) ke against validate karta hai
- name aur domain enforce karta hai jab tak seller is_confidential = 1 set na kare
- Confirm karta hai ki is_confidential aur is_passthrough clean 0/1 boolean flags hain
- Har error ko sellers[] index aur offending seller_id ke saath tag karta hai
- seller_type se counts plus confidential aur passthrough totals summarise karta hai
- Document ko aapke browser mein parse aur validate karta hai — file kabhi aapke device se bahar nahi jaati
sellers.json Validator kaise use karein
- Apna sellers.json document paste karein, ya expected shape dekhne ke liye sample load karein
- Pass/fail verdict aur seller-type summary counts padhein
- Message mein diye index aur seller_id se har flagged sellers[i] entry par jump karein
- Offending field fix karein aur re-validate karein jab tak document pass na ho
Example
Input
{
"version": "1.0",
"sellers": [
{ "seller_id": "1001", "seller_type": "RESELLER" }
]
}
Output
Invalid sellers.json — 3 issues
sellers[0] (seller_id 1001) — Invalid "seller_type" "RESELLER". Must be one of PUBLISHER, INTERMEDIARY, or BOTH.
sellers[0] — "name" is required unless the seller is confidential.
sellers[0] — "domain" is required unless the seller is confidential.
seller_type sirf PUBLISHER, INTERMEDIARY, ya BOTH accept karta hai; non-confidential sellers ko name aur domain chahiye.
Common errors aur troubleshooting
- Ek file par "Missing required top-level field version" jismein saaf sellers hain. — sellers.json ko top level par sellers[] ke saath ek string version field (jaise "1.0") chahiye. Use add karein — akela sellers array kaafi nahi hai.
- Ek confidential seller ek missing name ya domain ke liye flag hota hai. — name aur domain sirf tab optional hain jab us seller par is_confidential = 1 ho. Unhe omit karne ke liye is_confidential ko 1 set karein, ya dono fields supply karein.
- seller_type reject hota hai bhale hi value sahi lagti ho. — Sirf PUBLISHER, INTERMEDIARY, aur BOTH valid hain (case-insensitive). RESELLER, SSP, ya EXCHANGE jaise values spec ka hissa nahi hain aur fail honge.
- Un IDs par "Duplicate seller_id" jinhe aap distinct maante hain. — seller_id ek string ke roop mein compare hoti hai, isliye 1001 aur "1001" collide karte hain. Har seller_id file ke andar unique honi chahiye — entries ko renumber ya de-duplicate karein.
Aksar pooche jaane wale sawaal
- sellers.json Validator kya check karta hai?
- Yeh required top-level version aur sellers[] array confirm karta hai, phir check karta hai ki har seller ke paas ek unique seller_id, ek seller_type jo PUBLISHER, INTERMEDIARY, ya BOTH ho, aur name aur domain hai jab tak seller confidential na ho — har problem ko uske index aur seller_id ke saath flag karke.
- Ek seller name aur domain kab omit kar sakta hai?
- Sirf jab woh seller is_confidential = 1 set kare. sellers.json spec ek confidential account ko apna name aur domain hide karne deta hai, isliye validator un entries ke liye name/domain requirement skip karta hai aur unhe summary mein alag ginti hai.
- sellers.json mein kaunse seller_type values valid hain?
- PUBLISHER (inventory owns karta hai), INTERMEDIARY (doosre account ki inventory resell karta hai), aur BOTH. Check case-insensitive hai, isliye publisher aur PUBLISHER dono pass hote hain, lekin koi doosri string jaise RESELLER ek invalid seller_type report hoti hai.
- Ek seller_id duplicate kyun report hoti hai?
- Har seller_id ek single sellers.json file ke andar unique honi chahiye. Validator compare karne se pehle IDs ko strings mein normalize karta hai, isliye ek numeric 1001 aur ek string "1001" same ID maani jaati hain aur doosri occurrence ko pehli par ek pointer ke saath flag kiya jaata hai.
- Kya validator meri sellers.json ko uske URL se fetch karta hai?
- Nahi. Yeh kabhi ek remote URL ya ad endpoint fetch nahi karta. Aap document text paste karte hain aur yeh aapke device par parse aur validate hota hai, isliye file ke baare mein kuch bhi ArrayKit ya kisi third party ko upload nahi hota.
Related tools
Saare ArrayKit tools