This checklist defines the technical requirements for production-grade integration with the LumaTrace Cloud API.
- M2M Credentials: Service account credentials stored in a secure Vault (not in .env or source).
- Token Management: Client implements automatic session renewal by re-authenticating via
/api/v1/auth/loginbefore the 60-minute TTL expiry (LumaTrace JWTs are strictly non-refreshable by design). - Audit Scopes: Integration uses specific scopes if configured (default:
tenant_access).
- Idempotency:
Idempotency-Key(UUID v4) generated for every/registerand/protectrequest. - Retry Strategy: Exponential backoff implemented for 429 and 5xx errors (as shown in Python example).
- Timeouts: Connection timeouts set to 10s (auth) and 30s (processing).
- Traceability: Client logs the
x-request-idfor every response to facilitate support correlation. - Monitoring: Client tracks 4xx error rates to detect integration drift.
- Payload Validation: Client-side check for < 25MB and < 16MP to reduce unnecessary egress.
- TLS: Connection restricted to TLS 1.3.