cross_feed — this key is issued for a different feed
What happened
Every pk_live_ key is bound to exactly one feed at mint time. The api-key you pasted belongs to Feed A, but the feed-id attribute on the widget says Feed B. We block the request so one customer’s key can never read another’s content.
Fix
- Open Console → Keys. Each row shows which feed the key is scoped to.
- Compare that feed slug to the
feed-idattribute in your embed snippet — they must match exactly. - If you manage multiple feeds, use one key per feed and label each row (Console → Keys → Label) so you can tell them apart at a glance.
- The safest fix: go to Console → Feeds → <the feed you actually want to embed> → Settings → Embed Code and copy that page’s pre-filled snippet. Both attributes come out matched.