publishable_key_not_allowed

Publishable key used for a server call · HTTP 403

What causes this

A cc_pub_… key is minted to sit in web page source. Anyone who can view the page holds it, so it cannot create a trigger or read a customer's provider records.

How to fix it

Call this with a secret key (cc_live_… or cc_test_…) that includes the proxy scope. Keep the publishable key in the connect widget only.

What the response looks like

{
  "error": {
    "code": "publishable_key_not_allowed",
    "status": 403,
    "message": "…",
    "hint": "…",
    "request_id": "req_…",
    "docs_url": "https://cloud.ngentix.ai/docs/errors/publishable_key_not_allowed"
  }
}

Quote the request_id if you contact support — it identifies your exact request in our logs.