Everything developers and security engineers ask about implementing APIPLAY in production.
How does APIPLAY inject secrets without frontend exposure?
Frontend browsers submit runbook parameters with placeholder tokens (e.g., {{SECRET:GATEWAY_KEY}}). The request is authenticated via stateless JWT at our Next.js edge and forwarded to the backend gateway. The gateway queries MySQL, decrypts the ciphertext using AES-256-GCM with an authenticated 128-bit tag, compiles the HTTP header, and executes the upstream call. The secret never leaves the secure server process.
Can support staff run destructive actions by mistake?
No. First, role-based access control (RBAC) allows you to designate which roles can execute queries in Staging vs Production. Second, all non-idempotent HTTP methods (POST, PUT, DELETE, PATCH) require explicit dual-confirmation modals before the browser dispatches the execution request.
What happens to response bodies and customer data?
APIPLAY records execution metadata (timestamp, user email, portal, environment, HTTP status code, and latency) in an append-only audit log table. We do not store third-party response bodies or sensitive customer payload contents on disk. Responses are streamed directly back to the staff browser for real-time inspection.
Can I import my existing OpenAPI / Swagger specification?
Yes! When creating or editing a portal, you can upload an OpenAPI v3 JSON/YAML or a Postman Collection v2.1 export. APIPLAY automatically parses all paths, methods, query parameters, headers, and request bodies into strongly-typed form schemas instantly.