Ship OG Images via API
Hit one endpoint per URL and get a share-ready PNG back — currently invite-only while we harden the contract with the first teams shipping against it.
curl -X POST https://oginify.com/api/og \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}' \
--output card.pngWhat You Can Call
Three endpoints cover the loop most teams need — generate, validate, iterate.
Generate from URL
POST a page URL, get back a 1200×630 PNG generated by the same Firecrawl → LLM → image pipeline that powers oginify.com.
Generate from prompt or image
Text-to-OG and image-to-OG variants for marketing pages, launches and AI-driven content where there's no URL to scrape yet.
Validate any URL
Score Open Graph and Twitter Card tags on any page, return per-platform previews and a list of fixes — same engine as the public Validator.
How to Generate Open Graph Images via API
One POST per URL, one PNG back. The same Firecrawl to LLM to image pipeline that powers oginify.com, wrapped in a versioned HTTP contract.
- Step 1
Send a POST Request
Hit POST /v1/og with a bearer key and a JSON body containing a url or prompt. Rate-limited at 60 requests per minute.
- Step 2
We Read, Paint and Bake
Firecrawl scrapes the page, an LLM extracts brand, tagline, palette and page type, and a Gemini-grade model paints one on-brand card plus three wildcards.
- Step 3
Retrieve the PNG URL
Get back a JSON response with a strict 1200×630 PNG on our CDN, cached for 365 days. Optional webhook for async pipelines.
Who It's For
Headless CMS
Auto-generate og:image on publish for Sanity, Contentful, Payload — without maintaining a Satori template per content type.
CI / build pipelines
Regenerate cards as part of a deploy: hit the API per changed slug, write the PNG to your CDN, ship.
SaaS dashboards
Give your users branded share cards for the pages they create — invoices, reports, public profiles.
AI agents & MCP
A drop-in tool for autonomous agents that publish content. Pairs with our open-source Skills repo for prompt-side guidance.
Tech & Limits
Authentication
Bearer tokens issued per workspace. Test and live keys are separated; rotate at any time.
Format
JSON in, JSON out. PNG is returned as a hosted URL (1200×630), or inline base64 on request.
Latency
Typically 8–15 seconds end-to-end per card. Cache-friendly — repeat URLs return instantly.
Rate limits
Tuned per workspace during private beta. We'll publish public tiers when the API leaves beta.
Reliability
Runs on the same edge stack as oginify.com. Idempotent by URL — safe to retry.
API FAQ
Is the API publicly available?
Not yet. It's in private beta — we're onboarding a small set of teams to lock the contract before opening self-serve sign-ups. Email us if you'd like in.
What's the pricing?
Private-beta partners get usage credits in exchange for feedback. Public pricing will line up with the existing Supporter tier philosophy — fair, predictable, no surprise bills.
Can I self-host the pipeline instead?
Yes. The same generation logic is published as the open-source social-cards-skills repo. The hosted API is the convenience layer on top — no infra, no model keys, no scraping to maintain.
Do you support webhooks for async jobs?
Not in the first version — calls are synchronous. If your use case needs async (long batches, scheduled regen), tell us in the access request and we'll factor it in.
What about rate limiting and abuse?
Per-workspace limits during beta. When the API opens publicly, rate limiting and quota enforcement will live in an external gateway, not in the worker — so noisy neighbours can't impact other tenants.
How do I get started?
Email api@oginify.com with what you're building, expected volume, and your stack. We'll send back keys and a short integration guide.
Wire Oginify Into Your Build Pipeline
Same endpoint powering the demos on this page — one POST per URL, 1200×630 PNG back, cached on the edge for a year. Keys go out by email, usually same day.