What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To set a WhatsApp link preview image with APITemplate.io, create an image template, generate an image URL using its Direct URL feature, then put that URL in your webpage’s og:image metadata. APITemplate.io documents this Open Graph workflow, including using different query-string values for different pages. Whether a particular WhatsApp client displays the image—and how quickly it updates—must be checked separately; the available APITemplate.io documentation does not establish WhatsApp’s current image rules or cache behavior.
How the webpage preview image is selected
A preview image is associated with the webpage being shared, not attached to the WhatsApp message itself. In the workflow documented by APITemplate.io, the page’s Open Graph metadata points to an image URL. The image URL can be generated from a reusable template, with text or image values supplied in the URL.
The key metadata element looks like this:
<meta property="og:image" content="GENERATED_IMAGE_URL" />
Replace GENERATED_IMAGE_URL with the complete image URL produced by APITemplate.io. The tag belongs in the page’s HTML head. The documentation supports this Open Graph setup, but does not establish WhatsApp’s current metadata precedence, supported image dimensions or formats, or preview-refresh behavior. Treat those as platform-specific items to verify rather than guaranteed outcomes.
Create a reusable image template in APITemplate.io
- In APITemplate.io, open Manage Templates and create a new image template.
- Choose a preset or custom dimensions, then open the visual editor.
- Add the elements needed for the image, such as text, images, and shapes.
- Give dynamic elements clear names. You will use those names when providing values in a Direct URL or API request.
- Save the template. For example, a text element named
headlinecan later receive a value through aheadline.textparameter.
APITemplate.io describes the editor and template setup in its image-template guide.
Free tools Windows power users keep installed
One-click scans. No signup required.
Generate a Direct URL and add it to the page
- In the image editor, open the Direct URL tab.
- Create an auth code. The documentation describes configuring a quota and expiration, then saving those settings.
- Build the URL using the template ID, auth code, and properties for the template’s named elements.
- URL-encode values when constructing URLs in application code, especially values containing spaces, punctuation, or non-ASCII characters.
- Use the completed image URL as the value of the page’s
og:imagemetadata tag. - Publish the page and check both its HTML metadata and the generated image URL independently.
The documented URL pattern is:
https://rest.apitemplate.io/v2/create-image-url/{template_id}?auth={auth_code}&{element.property}={value}
For example, a template element called headline can use headline.text as a query parameter. An image element can use an image property such as background.src. Use the actual template ID, auth code, and element names from your APITemplate.io account; the values shown in the pattern are notation, not literal credentials.
APITemplate.io’s Direct URL image-generation documentation explains the URL workflow and its use in Open Graph metadata. Keep the auth code’s quota and expiration settings in mind when deciding where and how to use the generated URL.
Give each page its own image
Use one reusable template, then generate a URL with page-specific query-string values. For example, each article can supply a different headline.text and, where appropriate, a different image source. Put that generated URL in that article’s own og:image tag. APITemplate.io documents changing query parameters to create unique preview images for pages.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #2
Build the URL with a proper URL-encoding function rather than concatenating unescaped text. A title containing an ampersand or question mark can otherwise change how the query string is parsed.
Use the POST API when values belong on a backend
If your site already has a backend or integration that assembles image data, APITemplate.io documents a separate POST workflow. Send a request to the v2 create-image endpoint with the template ID, an X-API-KEY header, and JSON overrides containing the template element names and replacement values. The API Console in the editor supports sample JSON and previewing generated output.
The guide lists US, EU, Australia, and Singapore API endpoints. Select the endpoint appropriate to your deployment using the vendor’s current documentation; do not assume a particular region or endpoint without checking it.
Keep the API key on the server. Do not place it in public page source. The Direct URL process uses its own auth code and settings, while the POST API uses an API key; check APITemplate.io’s current security and access guidance for the way you deploy either method. See the vendor’s API documentation for the current v2 details.
| Route | How values are supplied | Useful when | Credential handling |
|---|---|---|---|
| Direct URL | Template ID, auth code, and element properties in the image URL’s query string | You want the generated URL available to place directly in page metadata, or to vary template values by page | Uses a Direct URL auth code with configurable quota and expiration settings |
| POST API | JSON overrides sent with a template ID and API key | A backend or existing integration already assembles the values and makes the request | Uses an X-API-KEY header; keep the key server-side |
The documented sources do not provide a reliable basis for comparing these routes by price, speed, or likelihood of success in WhatsApp. Choose based on where your page-specific values are assembled and which integration style fits your site.
Or skip the browser setup
If you also need a screenshot of a webpage, ScreenshotNeo can return a screenshot or PDF from one GET request. That is a separate option from APITemplate.io’s image-template workflow: it captures a webpage rather than creating an image from a reusable social-card template.
Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo documentation for request options. ScreenshotNeo can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; those steps can each be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Recommended Free Tools
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Check the page and diagnose a missing or stale preview
After publishing, validate each piece of the chain separately. A page can have a correct template while its metadata points to the wrong URL, or metadata can be correct while a sharing client still displays a previous result.
- Inspect the page source: Confirm the intended page has an
og:imagetag and that itscontentvalue is the complete generated URL. - Open the image URL directly: Confirm it returns the intended image, with the expected text and visual elements, rather than an error or an unexpected output.
- Check dynamic values: Compare the query-string property names with the element names and properties in the template. Verify that URL-sensitive characters are encoded.
- Check the Direct URL settings: Confirm the auth code is valid and that its configured quota and expiration allow the request.
- Verify the exact shared page: Make sure the metadata belongs to the URL being sent, including any page-specific path or variation.
- Test in the target WhatsApp context: The collected APITemplate.io material does not establish how quickly a WhatsApp preview refreshes or how to force a refresh. Do not assume that changing the image URL will immediately replace an already-seen preview in every client.
Common problems and fixes
The image is missing from the preview
First check that the page’s og:image tag exists in the published HTML and points to the generated image URL. Open that URL directly to separate metadata problems from image-generation problems. The documented APITemplate.io workflow does not specify WhatsApp’s current image constraints or fetching rules, so confirm platform-specific requirements in current WhatsApp or Meta documentation before treating a metadata check as a guarantee.
The preview shows an old image
Inspect the current page source and generated URL to see whether the page is serving the new value. If both are correct, the remaining behavior may depend on the sharing client’s preview-fetching or cache behavior. The available APITemplate.io sources do not establish a WhatsApp cache-clearing procedure or refresh timetable.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe image is generated, but the text or background is wrong
Check that the query parameter uses the correct named element and property, such as headline.text or background.src. Confirm that the page-specific value is encoded correctly and that the URL contains the value you intended to pass.
The Direct URL no longer works
Review the auth code and the quota and expiration settings configured in the Direct URL tab. The generated link depends on that Direct URL setup; create or adjust it in APITemplate.io if its settings no longer permit the request.
The POST request is rejected or returns the wrong output
Check that the request uses the current v2 create-image route, includes the X-API-KEY header, and sends JSON overrides with names matching the template elements. Use the editor’s API Console to preview sample JSON, and consult the current API documentation for the region and endpoint you selected.
Frequently asked questions
Can one template create a different WhatsApp preview image for every page?
Yes. APITemplate.io documents using page-specific query parameters with a reusable template. Each page still needs its own generated image URL in its own og:image metadata.
Does setting og:image guarantee WhatsApp will show the image?
No such guarantee is established by the APITemplate.io documentation cited here. It documents generating an image and placing its URL in Open Graph metadata, not WhatsApp’s current fetching or display rules.
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.
