← Back to home
Technical Whitepaper

Security Architecture

At APIPLAY, security is not an afterthought — it's the core foundational directive of the platform. We built this gateway to keep your production credentials out of the hands of non-technical staff while still empowering them to perform their jobs.

1. Zero Client-Side Secrets

The defining security feature of APIPLAY is that API credentials (such as Bearer tokens, private API keys, or basic auth credentials) never reach the user's browser.

When an engineer configures a portal, the API keys are encrypted immediately and stored in the backend vault. When a staff member runs a query, the frontend only sends the unauthenticated form data to our gateway. The backend retrieves the vault credentials, decrypts them in memory, attaches them to the outgoing HTTP request, and proxies the call to your API.

2. AES-256-GCM Authenticated Encryption

All vault secrets are encrypted at rest using AES-256-GCM (Galois/Counter Mode), an Authenticated Encryption with Associated Data (AEAD) standard. Each secret is protected with a unique 96-bit cryptographically secure initialization vector (IV) and a 128-bit authentication tag that guarantees cryptographic authenticity. If any ciphertext is altered or tampered with, decryption halts immediately. The master encryption key is derived via SHA-256 from secure environment storage and is never persisted in the database.

3. Stateless JWT Authentication

User authentication relies on short-lived JSON Web Tokens (JWTs). We do not maintain server-side session state, significantly reducing the attack surface. Sensitive routes (like creating portals or modifying environments) enforce strict role-based access control (RBAC), verifying that the user is an Administrator or Developer on every single request.

4. Append-Only Audit Logging

Every API execution is recorded in an append-only database audit log table with server-generated timestamps. Operational staff accounts have strictly read-only access with no capabilities to edit, truncate, or delete execution records. The audit log captures:

  • The authenticated user's email address and user ID
  • The specific portal and environment executed
  • The server timestamp and execution duration
  • The sanitized input payload parameters
  • The HTTP response status code

Crucially, we do not log your raw API secrets, nor do we permanently store third-party API response bodies in our database.

5. Strict Schema Validation & Sanitization

All user inputs from the visual form builder are strongly typed and validated against developer-defined field constraints before being serialized into downstream API requests. While no client-side or gateway validation can guarantee complete protection against all arbitrary downstream vulnerabilities, this layer of strict type-checking, regex validation, and input sanitization directly defends against malformed requests and parameter tampering.

If you have specific technical security questions or enterprise review inquiries regarding our architecture, please contact us at: info@markuting.com.