Tanitar Developers

Authenticate Players in your product, assert them from your backend, and use Tanitar's public Player API.

Your product owns Player authentication. Your trusted backend uses a dedicated Player-session credential to assert an authenticated Player's stable external identifier to Tanitar. Tanitar returns a 15-minute Player token for direct bearer calls to the public Player API.

sequenceDiagram
  Player->>Customer backend: Authenticated session
  Customer backend->>Tanitar: POST /player/v1/sessions
  Tanitar-->>Customer backend: 15-minute Player token
  Customer frontend->>Tanitar: /player/v1/* with Bearer token

Tanitar does not register or call your identity provider. There is no issuer, JWKS or introspection integration, pre-registered mapping, hosted Player application, handoff cookie or Player refresh token. First assertion creates the tenant-scoped mapping and Player idempotently.

Start with Create a Player session, then use the generated public API reference. Keep the session credential on your backend and the short-lived Player token in frontend memory.

Player identity