publishable_key

HTTP 403Publishable keyIngest APIRead API

What happened

A publishable key (pk_…) was used for something publishable keys cannot do: pushing observations, uploading a feed file, or a bulk export. They are read-only by construction, because they are meant to be safe inside a web page.

How to fix it

Use a secret key (sk_…) from your server. If the call really does belong in the browser, it belongs on the public read tier instead.

What you received

{
  "type": "https://docs.sidelineexchange.com/errors/publishable_key",
  "title": "Publishable key",
  "status": 403,
  "detail": "…"
}

Worth understanding

Publishable key — pk_test_… / pk_live_… — read-only, public-tier, safe to ship inside a web page. What the calendar widget uses.
Secret key — sk_test_… / sk_live_… — full authority: push, read, manage webhooks. Server-side only, shown once at creation.

← All errors