Authentication

Partners authenticate with credentials issued during onboarding. End users authenticate through your product; Eterna maintains segregated sub-accounts under your partner umbrella.

Partner integration pattern

1. Your backend holds partner API credentials (secret manager)
2. Your backend creates or resolves an end-user trading account mapping
3. Trading and private reads use short-lived access tokens or signed server-to-server calls (as issued for your tenant)
4. Browsers and mobile apps never embed long-lived exchange secrets

What we do not publish here

• Exact header names for internal service mesh auth
• Encryption key lengths or key-derivation steps for custody material
• Break-glass or e2e-only authentication routes
• Shared “demo” secrets

Those details are delivered securely to your technical contact.

Operational guidance

• Rotate credentials on a defined schedule and after staff offboarding
• Prefer separate credentials for market-data-only workloads
• Log request ids for support tickets; never log secrets or full authorization headers

Continue to Market data or Trading.