SUPPORT

Get help

ogshot is a small, independent product — you'll reach a real person.

Email us

The fastest way to get help is support@ogshot.dev. To help us help you quickly, include:

  • your account (GitHub username) or API key prefix (the ogs_1234… part — never the full key);
  • the endpoint and roughly when the request happened;
  • the error code and message you got back (for example quota_exceeded or blocked_by_policy), and the URL or a snippet of the HTML you were rendering.

Check the docs first

Many questions are answered faster in the reference:

  • API docs — every endpoint, parameter, and error code.
  • Signed URLs — embedding a render in a public og:image without exposing a key.
  • Errors — what each status code means and how to fix it.
  • Playground — reproduce and tweak a render in the browser.

Common fixes

  • 401 unauthorized — missing or revoked API key. Check the x-api-key header, or your signature on a signed URL.
  • 402 quota_exceeded — you've used your plan's monthly renders. Cached hits are free; upgrade or wait for the reset.
  • 403 blocked_by_policy — the target resolves to a private or disallowed address. ogshot only renders public hosts.
  • Render looks wrong — try increasing timeout or setting wait_until=networkidle so the page fully loads first.

What to expect

We aim to reply to support email within a couple of business days. ogshot currently runs as a single instance, so brief maintenance windows can happen; if something looks down, email us and we'll take a look.