API keys
See API keys for the key format and how it’s used across MCP vs. REST.
GET /v1/api-keys
Section titled “GET /v1/api-keys”curl https://sandbox-api.nuez.app/v1/api-keys \ -H "Authorization: Bearer <jwt>"{ "api_keys": [{ "id": "6f2c...", "name": "claude-supplier-agent", "created_at": "2026-07-18T14:32:00Z" }] }Never returns the key value itself — only POST does, and only once.
POST /v1/api-keys
Section titled “POST /v1/api-keys”curl -X POST https://sandbox-api.nuez.app/v1/api-keys \ -H "Authorization: Bearer <jwt>" \ -H "Content-Type: application/json" \ -d '{"name": "claude-supplier-agent"}'{ "id": "6f2c...", "name": "claude-supplier-agent", "key": "nz_...", "created_at": "2026-07-18T14:32:00Z" }DELETE /v1/api-keys/{id}
Section titled “DELETE /v1/api-keys/{id}”curl -X DELETE https://sandbox-api.nuez.app/v1/api-keys/6f2c... \ -H "Authorization: Bearer <jwt>"Returns 204 No Content. Requests made afterward with the deleted key fail (401 at /v1/auth/token for REST, 401 unauthorized at /mcp for MCP).