Security Protocols

Access control is enforced via Bearer Tokens. Secure your geometry data streams with enterprise-grade keys.

Authorization Header

The API requires a valid key in the HTTP Authorization header for every request.

Authorization: Bearer sk_live_a1b2c3...

Provisioning Keys

1. Initialize workspace account via dashboard.
2. Verify identity via email confirmation loop.
3. Navigate to Settings > API Keys.
4. Click Generate Key button.

WARNING: Keys are shown only once. Store in a secure vault immediately.

Key Specification

sk_live_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6

| Property | Value | |----------|-------| | Prefix | sk_live_ | | Entropy | 32 chars | | Algorithm | SHA-256 Hashed |

Key Rotation Protocol

In event of compromise, execute the rotation protocol immediately.

Grace Period Active
Old keys remain valid for 6 hours post-rotation to allow for zero-downtime migration. After T+6h, old keys are hard-revoked.

Security Directives

• No Version Control
  Do not commit keys to Git. Use .env files.

• Server-Side Only
  Keys grant full access. Never expose them in client-side React/JS code.

• Environment Segregation
  Maintain separate keys for Development, Staging, and Production.

---

Need help? Contact Security Team