Every page that gets shared needs an og:image, and wiring up an HTML-to-image endpoint per project is the kind of yak-shave that eats an afternoon. This workflow gives you the endpoint instead. POST a title and a description, get back a hosted image URL, and drop it in your og:image tag.
How it works
- POST to the webhook. Send a JSON body with the fields your card shows, a title and a description at minimum.
- A card renders from the payload. The workflow maps those fields onto your template and renders the social card. Long titles auto-fit instead of overflowing.
- You get back a hosted URL. The response carries a hosted Orshot image URL for that render. It does not post anywhere, it is yours to use.
- Use it as og:image. Put the URL in the page's og:image tag. When the link is shared, the preview is your rendered card.
Where developers use it
Blogs
One POST per post from the CMS or build step, so every article has a card built from its own title.
Docs sites
A card per page rendered from the page title and section, generated at build time.
Dashboards
Shareable snapshots where the title and a key number come straight from the request payload.
User-generated pages
Profiles and listings that each get a card from their own fields, no screenshot service in the stack.
Design the card once in the studio, and every route that can build a title and a description has a matching social image on demand.
