Magic Link

The backend API covers DID token validation (verifying that a user's authentication token is valid), user management (retrieving and updating user records), and session management. Agents interacting with Magic-authenticated users primarily need the token validation endpoint — verifying the DID token passed from clients to ensure requests come from authenticated users. The admin API enables programmatic user management operations.

Reliability is vendor-managed for the authentication infrastructure. Magic link delivery depends on email deliverability — teams should monitor magic link delivery rates and implement appropriate fallback authentication paths for users who don't receive the email. The managed infrastructure handles token expiry and replay prevention.

Magic.link is a passwordless authentication service providing email magic links, WebAuthn passkeys, social OAuth (Google, GitHub, Apple), and Web3 wallet authentication through a single SDK. Its managed infrastructure handles the token generation, delivery, and validation lifecycle for magic link flows without teams building email token systems. The platform's combined coverage of Web2 passwordless and Web3 wallet authentication makes it distinctive for applications serving both traditional and crypto-native users.

Authentication to the Magic admin API uses secret keys for server-side management operations. The public key enables client-side SDK initialization. Key separation follows standard patterns for API platforms with separate public/secret key pairs. Magic DID tokens are JWTs that agents can validate locally using Magic's public key without a roundtrip.

Documentation covers the SDK integration, backend validation, and admin API clearly. The DID token validation documentation is the most critical reference for backend agents — understanding the token format and validation process is essential for secure implementation. Teams evaluating Magic versus Hanko or Stytch for passwordless authentication should compare the social OAuth coverage and the Web3 wallet support for their user authentication requirements.