Free tools Windows power users keep installed
One-click scans. No signup required.
Seedha jawab: WordPress ke server-side PHP code se Browshot API ko call kijiye—API key ko server par rakhein, target URL aur instance_id bhejein, phir response status ke mutabik screenshot dikhayein ya processing handle karein. Browshot ka official WordPress plugin is guidance se establish nahi hota; neeche diya integration pattern Browshot aur WordPress ke official developer documentation par aadharit custom implementation hai, tested plugin nahi.
Integration ka flow kya hai?
WordPress site ka backend Browshot ko authenticated HTTP request bhejta hai. Browser-side JavaScript mein API key rakhne ke bajay WordPress HTTP API, jaise wp_remote_get(), istemal karein. Isse key public page source ya visitor ke browser network requests mein expose nahi hoti.
As an Amazon Associate I earn from qualifying purchases.
- Browshot dashboard se API key lein.
- Apne WordPress plugin ya server-side PHP component mein key ko private configuration ke roop mein rakhein.
- Target page ka URL aur Browshot ka chuna hua
instance_idbhejein. - Response code aur body check karke image, in-progress status, redirect ya error ko alag handle karein.
- Screenshot ko apne page, admin screen ya kisi anya UI mein dikhayein—yeh display design aapki implementation ka hissa hai, Browshot ki prescribed WordPress setting nahi.
Browshot documentation API host https://api.browshot.com/ aur API version 1.31 batati hai. API key dashboard mein dikhayi jaati hai. Apni key ko source control mein commit na karein; production mein ise server configuration ya kisi secret-management mechanism mein rakhna behtar hai.
Recommended Free Tools
Simple API ya complete screenshot API?
| Vikalp | Flow | Kab chunen |
|---|---|---|
| Simple API | Ek request se minimal capture flow. Browshot ise complete API se aasan, lekin dheema batata hai. Ismein screenshot ya thumbnail response, failure image, aur processing ke dauran redirect aa sakta hai. | Chhota demonstration ya simple request jab aap redirect-following aur response handling implement kar sakte hon. |
| Complete screenshot API | Screenshot creation aur status/image retrieval ko alag operations mein handle karne wala zyada explicit flow. Create response JSON status, jaise in_process ya finished, dikha sakta hai. |
Plugin ya workflow jahan status, retries aur baad mein image retrieval par control chahiye. |
Yeh documented request patterns ka farq hai, speed benchmark nahi. Agar WordPress integration ko processing state dikhani hai, complete API flow aam taur par zyada spasht control deta hai. Endpoint aur parameters apne selected Browshot instance ke current documentation se verify karein.
#1 Best Overall
WordPress mein API key aur code kahan rakhein?
Browshot key ko plugin ke public settings output, shortcode markup, theme JavaScript, ya browser request mein na bhejein. WordPress ke server-side HTTP API ka istemal karein. WordPress Developer Resources mein HTTP API ke liye wp_remote_get() aur response code/body nikalne ke helpers documented hain.
Production ke liye apne plugin mein key ko configuration se read karna ek implementation choice hai. Neeche ke example mein YOUR_BROWSHOT_API_KEY aur YOUR_INSTANCE_ID ko apni private configuration se badlein; code ko public page se run na karein. Browshot API version 1.31 ka zikr karta hai, lekin code mein endpoint ke exact parameter names aur response fields current Browshot API reference ke hisaab se confirm karna zaroori hai.
Complete API ke liye server-side PHP example
Yeh example WordPress HTTP API ke madhyam se Browshot par screenshot-create request bhejne aur response ko inspect karne ka pattern dikhata hai. Endpoint path aur response fields Browshot documentation se apne account, instance aur current API version ke liye verify karein. Neeche url aur instance_id required inputs hain; API key ko query parameter ke roop mein bhejne ka tareeqa Browshot API ke documented authentication pattern ke mutabik hai.
<?php
function mysite_request_browshot_screenshot( $target_url ) {
$api_key = 'YOUR_BROWSHOT_API_KEY'; // Is value ko private server configuration se load karein.
$instance_id = 'YOUR_INSTANCE_ID';
$endpoint = 'https://api.browshot.com/api/v1/screenshot/create';
$request_url = add_query_arg(
array(
'key' => $api_key,
'url' => $target_url,
'instance_id' => $instance_id,
),
$endpoint
);
$response = wp_remote_get(
$request_url,
array(
'timeout' => 30,
'redirection' => 3,
)
);
if ( is_wp_error( $response ) ) {
return array(
'state' => 'transport_error',
'error' => $response->get_error_message(),
);
}
$status_code = wp_remote_retrieve_response_code( $response );
$body = wp_remote_retrieve_body( $response );
$data = json_decode( $body, true );
if ( 200 > $status_code || 300 <= $status_code ) {
return array(
'state' => 'http_error',
'status_code' => $status_code,
'body' => $body,
);
}
if ( ! is_array( $data ) ) {
return array(
'state' => 'invalid_response',
'status_code' => $status_code,
);
}
// Browshot ke documented response fields ke mutabik ID/status read karein.
return array(
'state' => isset( $data['status'] ) ? $data['status'] : 'response_received',
'data' => $data,
);
}
?>Yeh code network request aur broad error checks ka runnable WordPress pattern hai, lekin /api/v1/screenshot/create path aur status field ko apne istemal wale Browshot endpoint ke current API docs mein verify kiye bina production mein copy na karein. Browshot ke docs create, status aur image retrieval operations alag batate hain; complete flow mein create response ke baad returned identifier se status/image operation karna pad sakta hai.
Request options chunein
Browshot ke create endpoint mein capture ko prabhavit karne wale documented controls mein screenshot size, caching, delay, desktop viewport width/height, optional rendered-HTML capture, JavaScript execution, custom headers aur CSS selector targeting shamil hain. Har option har instance ya endpoint par ek jaisa supported ho, yeh assume na karein; parameter names aur values current endpoint docs se check karein.
- Screen ya full page: chhota viewport chahiye ya poori page capture karni hai, uske mutabik size option set karein.
- Viewport: desktop viewport width aur height ko target layout ke saath match karein.
- Delay: page ko render hone ke liye waqt dene ke liye hi use karein; anavashyak delay processing ko lamba karega.
- Cache: repeated capture ko control karne ke liye Browshot ka caching option dekhein.
- HTML capture: rendered HTML save karna optional hai aur Browshot documentation ke mutabik har screenshot par ek credit lagta hai.
- JavaScript, headers, selector: sirf tab set karein jab target page ya use case ko waqai zaroorat ho.
Simple API ka minimal request aur response handling
Simple API ek chhota request path deta hai, par response ko hamesha seedha PNG samajhkar save ya embed na karein. Browshot is endpoint ke liye 200, 302, 400 aur 404 jaise HTTP status document karta hai. Kuch pages ko capture hone mein do minute tak lag sakte hain aur documentation 302/307 redirects follow karne ki salah deti hai. Isliye apne HTTP client mein redirect behavior samjhein aur final response ka status verify karein.
Rank #4
<?php
function mysite_get_browshot_simple_result( $target_url ) {
$api_key = 'YOUR_BROWSHOT_API_KEY'; // Private server configuration se load karein.
$request_url = add_query_arg(
array(
'key' => $api_key,
'url' => $target_url,
),
'https://api.browshot.com/api/v1/simple'
);
$response = wp_remote_get(
$request_url,
array(
'timeout' => 150,
'redirection' => 5,
)
);
if ( is_wp_error( $response ) ) {
return array( 'state' => 'transport_error' );
}
$status_code = wp_remote_retrieve_response_code( $response );
$body = wp_remote_retrieve_body( $response );
$content_type = wp_remote_retrieve_header( $response, 'content-type' );
if ( 200 !== $status_code ) {
return array(
'state' => 'http_status',
'status_code' => $status_code,
'body' => $body,
);
}
return array(
'state' => 'image_response',
'content_type' => $content_type,
'body' => $body,
);
}
?>Yeh minimal pattern response body aur content type deta hai; yeh file ko disk par store, WordPress media library mein import, ya public URL generate nahi karta. Aapki site ko image persist karni ho to storage, filename, access policy aur cleanup ka alag design banayein. Browshot simple API successful screenshot/thumbnail par PNG image de sakta hai; uska default not-found image bhi possible hai, isliye sirf HTTP 200 ko page ki safalta ka proof na maanein.
Status, redirects aur image ko WordPress mein dikhana
Complete API: create se retrieval tak
- Create request bhejein aur JSON body parse karein.
- Agar state
in_processhai, turant image tag render na karein. Returned screenshot identifier ko apne workflow ke mutabik rakhein aur Browshot ke status operation se baad mein check karein. - Jab state
finishedho, documented image retrieval operation se image hasil karein. - Image ko display karne se pehle response aur content type validate karein; error payload ko image URL ki tarah render na karein.
WordPress REST API is call ke liye zaroori nahi hai. WordPress REST API WordPress resources ke saath HTTP interaction ke liye hai; WordPress backend ka Browshot ko call karna alag kaam hai aur uske liye WordPress HTTP API kaafi hai. Agar aap apna custom admin endpoint ya block data route banana chahte hain, tab REST API ek optional design choice ho sakti hai.
Best Value
Simple API: redirect ya error
- 200: body image ho sakti hai, lekin expected image/content type aur valid result ko check karein.
- 302 ya 307: processing/redirect flow ho sakta hai; Browshot ki salah ke mutabik redirects follow karne ka behavior configure karein.
- 400: request parameters invalid ho sakte hain; URL, key aur required values verify karein.
- 404: capture perform nahi hua ho sakta; response ko normal screenshot samajhkar display na karein.
Security, load aur kharch ke practical points
- API key: private rakhein. WordPress server se Browshot call karein, public browser JavaScript se nahi.
- Untrusted target URLs: agar visitor URL submit kar sakta hai, input ko validate aur restrict karein. Warna aapka server unintended destinations ko request karne wala proxy ban sakta hai.
- Request timeout: simple API docs kuch pages ke liye do minute tak ka case batati hain. Bahut chhota timeout capture ko beech mein rok sakta hai; bahut lamba synchronous WordPress page request ko latka sakta hai. Lambi jobs ke liye asynchronous/background processing par vichar karein.
- Repeat requests: cache settings ko use case ke mutabik chunen taaki har page view par anavashyak nayi capture request na chale.
- HTML capture cost: Browshot docs optional HTML capture ke liye ek credit per screenshot batati hain.
- Quota: referenced Browshot API pages free instance ke liye 100 screenshots per month batati hain. Yeh service term badal sakti hai; account ya implementation plan banane se pehle current Browshot docs/account terms dekhein.
- Authorized pages: scripted actions ya screenshots sirf un pages par chalayein jinhe access karne ki aapko anumati hai.
Common errors aur unka fix
| Symptom | Likely cause | Kya karein |
|---|---|---|
wp_remote_get() se WP_Error |
WordPress server se network/DNS/TLS failure ya timeout. | Error message log karein, server outbound HTTPS connectivity check karein, aur timeout ko page ke expected render time ke hisaab se set karein. |
| HTTP 400 | Invalid/missing parameter, malformed URL, ya galat request format. | Required url aur instance_id check karein; endpoint ke documented parameter names se compare karein. |
| HTTP 404 ya not-found image | Browshot capture perform nahi kar saka, ya simple API default failure image de raha hai. | Status, response body aur content type inspect karein; ise successful target screenshot ke roop mein publish na karein. |
| Request pending ya 302/307 | Capture abhi complete nahi, ya simple API redirect-based wait flow de raha hai. | Redirect following configure karein, response ko dobara check karein, ya complete API ke status/retrieval flow par jaayein. |
| JSON parse fail | Response JSON ke bajay image, redirect body ya error text hai. | HTTP status aur content type dekhkar hi body parse karein; simple aur complete API ke response formats ko mix na karein. |
| Screenshot blank ya adhura | Page render ko aur waqt, JavaScript, ya viewport/selector-specific configuration chahiye. | Relevant delay, JavaScript execution, viewport ya selector options ko Browshot docs ke mutabik adjust karein; zaroorat na ho to extra delay na jodein. |
| API key leak hone ka risk | Key public HTML/JavaScript ya repository mein likhi gayi. | Key rotate karein, server-side configuration se load karein, aur browser ko Browshot call na karne dein. |
Advanced case: scripted browser steps
Browshot automation documentation steps JSON array mein click, type, sleep, navigate aur screenshot jaise actions batati hai. Aise steps ko sirf authorized pages aur legitimate workflows tak seemit rakhein; login, account access ya kisi control ko bypass karne ki automation bina anumati na karein. Is feature ko tabhi jodein jab seedhe URL capture se kaam na chale.
Or skip the browser setup
Agar aap WordPress server par browser setup aur capture handling khud nahi banana chahte, ScreenshotNeo ko alternative ke roop mein dekh sakte hain: ScreenshotNeo website screenshot API aur MCP server hai. Ek GET request ke saath target URL bheja ja sakta hai; is example mein Stripe ki jagah apna URL rakhein.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpEndpoint aur options ke liye ScreenshotNeo API documentation dekhein. ScreenshotNeo capture se pehle cookie/consent banner accept karta hai aur 60 se zyada known consent platforms, newsletter popups aur chat widgets hata sakta hai; har step ko off kiya ja sakta hai. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads aur cache hits bill nahi hote, aur response mein X-Page-Verdict aur X-Billed headers hote hain. Claude, Cursor ya kisi MCP client ke liye iska MCP server take_screenshot, get_page_info aur capture_pdf tools deta hai. Free plan mein 1,000 screenshots/month bina card ke milte hain; paid plans $5 mein 3,000 se shuru hote hain.
ScreenshotNeo par free sign up karein—1,000 screenshots per month, no card.
Frequently Asked Questions
Kya Browshot ka official WordPress plugin hai?
Yahan cite kiye gaye Browshot aur WordPress official sources ready-made Browshot WordPress plugin establish nahi karte. Isliye integration ko custom server-side implementation samjhein.
Kya WordPress REST API Browshot ko call karne ke liye zaroori hai?
Nahi. WordPress backend se external Browshot request ke liye WordPress HTTP API istemal ki ja sakti hai.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
