PromptWall API key (every mode)
Issued by PromptWall when you create an application in the Console. Format:pw_….
Send it on every PromptWall request:
| Endpoint | Required header |
|---|---|
POST /v1/chat/completions (Proxy) | X-PromptWall-Api-Key: pw_… or X-API-Key: pw_… |
POST /v1/verify | X-API-Key: pw_… or Authorization: Bearer pw_… |
POST /v1/chat | X-API-Key: pw_… or Authorization: Bearer pw_… |
POST /v1/events | X-API-Key: pw_… or Authorization: Bearer pw_… |
X-PromptWall-Api-Key)
because the standard Authorization: Bearer … slot already carries
your OpenAI key — see below.
OpenAI API key (Proxy mode only)
Issued by OpenAI. Format:sk-…. PromptWall never reads or stores
this key — it is forwarded verbatim to api.openai.com. Your OpenAI
billing relationship is unchanged.
Proxy mode
Example: Verify and Events modes
Verify
Events
Storing keys safely
- Treat the PromptWall key like any other secret — env vars or a secrets manager. Never commit it.
- Rotate by creating a new application in the Console and migrating callers; the old key is revoked when its application is deleted.
- All proxy traffic is auth-checked before PromptWall contacts OpenAI, so a missing or invalid PromptWall key cannot result in charges on your OpenAI account.