Skip to main content

Widget errors — what each one means

When something goes wrong on the widget’s side, we log a specific reason code to the browser console so you can turn the failure into a fix without opening a support ticket.

How to find the reason code

  1. Open the page where the widget lives.
  2. Open your browser’s DevTools console (⌥⌘I on Mac, F12 on Windows).
  3. Look for a line prefixed with [podsaid-widget]. The reason will be one of the codes below.

If you don’t see any [podsaid-widget] line at all, the widget script hasn’t loaded. Check that the <script src="https://widget.podsaid.com/v1/widgets.iife.js"> tag is present in your HTML.

Reason code index

  • key_missing — the widget never sent an API key. Usually a missing or misnamed api-key attribute.
  • key_unknown — we received a key but don’t recognize the value. Typo or environment mismatch.
  • key_revoked — the key was intentionally shut off. Mint a new one.
  • origin_denied — the site’s origin isn’t in your key’s allowlist. See Allowed origins.
  • cross_feed — the key is real, but for a different feed than the feed-id attribute names.

When to email support

If the error persists after following the fix steps on the specific reason page, or if none of these codes match what you’re seeing, email support@podsaid.com with:

  • The URL of the page you’re embedding on
  • A screenshot of the browser console showing the full error line
  • Your feed ID and (if you can) the last 4 characters of your pk_live_ key