Ident.ink 2.8.1 opens the platform to secure ecosystem connections without weakening the account, billing, publishing or administrative boundaries that protect it.

Sign in with Ident.ink

Applications can now request narrowly scoped access through an authorisation code flow with PKCE S256. People see the requested permissions before approving them. Redirect addresses must match exactly, codes are short-lived and single-use, refresh credentials rotate, and consent can be revoked.

The initial public scopes cover identity, profile, verified email and read-only project access. An application receives only the information its user approved. Passwords, sessions, payment details, private administrative data and unrelated projects are never exposed.

[Open the developer portal](https://ident.ink/developers) to register an application, read the operational guide and download the live OpenAPI description.

A controlled integration plane

The founder can connect trusted internal systems through a separate private integration control plane. Credentials are hashed at rest and shown only once. Each integration has explicit scopes, rotation and disable controls, idempotent event ingestion, durable jobs and a complete audit trail.

This private plane is not a shortcut around normal permissions. It is isolated from public OAuth and remains restricted to the official founder account.

Publisher and writer review access

Publisher review is not a separate suite. An approved publisher or writer signs into the normal Ident.ink account and can explore the real platform through a disposable sandbox spanning the main suites.

They can learn workflows, create previews and prepare accurate coverage, but cannot publish to production, spend infrastructure, charge payment methods, contact other users, operate live hosting, run bots or change shared data. The sandbox has a strict cumulative storage budget and is wiped when the grant ends or the password is reset.

Verified account lifecycle

Unverified normal accounts now receive a fresh working verification link and a clear grace period before deletion. Founder, admin, staff, partner, billing, financial and legal records are protected from automated deletion. Cleanup is idempotent and audited, and verification cancels deletion automatically.

Release evidence

The production candidate passed 55 automated tests, a clean dependency and syntax review, database integrity verification, a production build, and a 358-surface production route audit with zero route failures. Public status and release history remain available throughout.

[View Transparency](https://ident.ink/transparency), [check live Status](https://status.ident.ink), or [contact Support](https://support.ident.ink).

Nic Founder and Head Developer