Get your project key

The project key is the public identifier the widget uses to send reports to the right project. It starts with pr_.

Find it in the dashboard

1. Open the dashboard at room.patchrooms.com and select your project.

2. Go to the Settings tab.

3. Copy the value under Project key — it looks like pr_abc123….

If you don’t have a project yet, create one first — see the Quickstart.

What pr_ is

The pr_ key is public. It’s meant to be embedded in your SDK init code or in the loader URL, and it’s safe to ship in browser bundles. Patchrooms still protects your project on the backend: ingest is gated per request, and you can restrict which origins are allowed to submit feedback with a given key under Settings → Allowed origins.

You use the pr_ key in either install form:

<!-- loader: key in the URL -->
<script src="https://room.patchrooms.com/v1/patchrooms/pr_xxx.js"></script>

<!-- programmatic -->
<script src="https://room.patchrooms.com/v1/patchrooms.js"></script>
<script>Patchrooms.init({ projectKey: 'pr_xxx' });</script>

pr_ key vs. pr_sk_ secret key

These are two different things — don’t mix them up.

pr_ — project key

Public. Used by the widget to submit reports. Embed it in browser code and loader URLs. Lives in Settings → Project key.

pr_sk_ — secret API key

Secret. Used for read-only access over MCP (scope feedback:read) so an AI tool can list and read reports. Created in Integrations. Never ship it in client-side code.

Danger

A pr_sk_ secret key is shown once, at creation time. Store it somewhere safe — you can’t view it again, only revoke it and create a new one. If a secret key leaks, revoke it in the Integrations tab.