API Key Management
Request project API keys stored securely in vault. Keys are created after project owner confirms via email.
⚡ Built-in — No Setup Required
This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.
Endpoints (2)
POST
request-key
Request a new WPA key. Sends confirmation email to project owner. Key is stored in vault after approval. The AI never sees the raw token.
| Field | Type | Required | Description |
|---|---|---|---|
vault_key_name |
string | ✓ Yes | Vault key name (must start with wpa_, lowercase alphanumeric + underscores, 7-44 chars total) |
purpose |
string | ✓ Yes | Human-readable description shown in confirmation email to project owner |
POST
check-status
Check if a pending key request has been approved by the project owner.
| Field | Type | Required | Description |
|---|---|---|---|
request_id |
string | ✓ Yes | Request ID from the request-key response (req_... format) |
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| request-key | auth_keys_request_key |
| check-status | auth_keys_check_status |