Convert karne ke liye collection kaise export karein?

Collection par hover karein, ⋯ menu kholein, Export chunein aur Collection v2.1 rakhein. Jo JSON milta hai wahi ye converter padhta hai: requests, folders, variables, auth aur bodies us ek file mein hain.

Kya Postman environment variables resolve hote hain?

Collection-level ke haan; environment ek alag export hai jo collection file mein hota hi nahin. Unresolved names report hote hain aur visible {{placeholders}} ki tarah rahte hain.

Postman auth kaise convert hota hai?

Bearer -H "Authorization: Bearer …" banta hai; basic base64 hokar standard header mein aata hai. Request-level auth priority leta hai jab dono exist karte hain.

Command share karne se pehle secrets redact kyun karein?

Commands travel karte hain — tickets, chat, terminal history mein — aur live tokens saath travel karte hain. Redaction sensitive headers chhupata hai jabki request ki shape shareable rehti hai.

Postman se cURL

Postman Collection v2.1 export ko runnable cURL commands mein badlein — folders traverse, variables resolve, auth convert.

Postman se cURL poori tarah aapke browser mein chalta hai. Aapke collections — tokens sahit — device par parse hote hain aur kabhi upload nahin hote.

HAR se cURL converter kholein

Postman to cURL ke baare mein

Postman se cURL poore collection export ko terminal commands mein convert karta hai jinhe aap run, script aur commit kar sakte hain. Collection v2.1 ka JSON drop karein aur har request — nested folders sahit — ek cURL command ban jaati hai: {{baseUrl}} jaise collection variables export ki apni variable list se substitute hote hain, bearer tokens aur basic credentials correct Authorization headers ban jaate hain (base64 sahit), aur raw JSON, urlencoded, form-data aur GraphQL bodies apne correct flags mein translate hoti hain. Quoting wahi cheez hai jo hath se sab galat karte hain: quotes se bhare bodies aur cookies POSIX-style escaped niklte hain. Bina value wale placeholders visible reh kar report hote hain, silently emit nahin hote, aur ek redact switch Authorization, Cookie aur API-key headers ko mask kar deta hai isse pehle ki command kisi ticket ya chat mein jaaye.

Features

Folders recursively traverse hote hain — collection ki har request
Collection variables substitute hote hain; unresolved report hote hain
Bearer aur basic auth Authorization headers mein convert hote hain
Raw, urlencoded, form-data aur GraphQL bodies handle hote hain
Hamesha POSIX-safe single-quote escaping
Per-request view plus poore collection ka script

Postman to cURL kaise use karein

Postman se export karein: Collection → ⋯ → Export → v2.1
JSON yahan drop karein ya paste karein
Ek request chunein, ya sab commands ko script ki tarah copy karein
Kuch bhi share karne se pehle redaction on karein

Example

Input

Collection with {{baseUrl}}/users and bearer auth

Output

curl 'https://api.example.com/users' \
  -H 'Authorization: Bearer tok…'

Variable collection se resolve; token REDACTED mein convert-able.

Common errors aur troubleshooting

Commands mein abhi bhi {{placeholders}} hain. — Wo variables Postman environment mein rehti hain, collection mein nahin — environments separately export hote hain. Converter har unresolved naam list karta hai; shell mein bharein ya values collection variables mein daalke re-export karein.
Export parse nahin hoti. — Sirf Collection v2.x ka JSON hi item tree rakhta hai jo yahan traverse hota hai. Postman mein Export → Collection v2.1 chunein, jo current versions ka default hai.
Form-data mein file uploads @FILE dikhate hain. — Export file content store nahin karta, sirf ye ki ek file field thi. Run karne se pehle @FILE ko real path se replace karein.

Aksar pooche jaane wale sawaal

Convert karne ke liye collection kaise export karein?: Collection par hover karein, ⋯ menu kholein, Export chunein aur Collection v2.1 rakhein. Jo JSON milta hai wahi ye converter padhta hai: requests, folders, variables, auth aur bodies us ek file mein hain.
Kya Postman environment variables resolve hote hain?: Collection-level ke haan; environment ek alag export hai jo collection file mein hota hi nahin. Unresolved names report hote hain aur visible {{placeholders}} ki tarah rahte hain.
Postman auth kaise convert hota hai?: Bearer -H "Authorization: Bearer …" banta hai; basic base64 hokar standard header mein aata hai. Request-level auth priority leta hai jab dono exist karte hain.
Command share karne se pehle secrets redact kyun karein?: Commands travel karte hain — tickets, chat, terminal history mein — aur live tokens saath travel karte hain. Redaction sensitive headers chhupata hai jabki request ki shape shareable rehti hai.

Related tools

HAR to cURL — HAR ki requests ko chalne waale cURL commands mein badlein.
cURL se Fetch — Ek curl command ko JavaScript fetch() call mein convert karein.
curl to Python — Ek curl command ko Python requests code mein convert karein.
API Client — HTTP requests bhejein, headers aur params banayein aur responses inspect karein; aapki aakhri 25 save hoti hain.
URL Builder aur UTM Generator — UTM parameters ke saath encoded production URLs banayein aur validate karein.
curl to Node.js — Ek curl command ko Node.js axios code mein convert karein.