Use case

Add authentication to a Hono API

AscendKit access tokens secure a Hono API the same way they secure any backend: verify the token in middleware and resolve the request to a usr_ record scoped by your public key. Because Hono runs on edge runtimes, JWKS-based verification keeps the check lightweight.

How it works

  1. 1. Authenticate the client
    Sign users in with the AscendKit SDK and pass access tokens to your Hono API.
  2. 2. Verify with middleware
    Add Hono middleware that verifies the access token against AscendKit's JWKS endpoint.
  3. 3. Resolve the user
    Map each verified request to a usr_ record scoped by your project public key.

FAQ

Does token verification work on edge runtimes?

Yes. AscendKit publishes signing keys via JWKS, so Hono middleware can verify access tokens on edge runtimes without a round trip.

Can I add email and journeys to a Hono backend?

Yes. Auth, email, journeys, and surveys are one platform, so a Hono API can trigger lifecycle messaging on the same user record.

Start with one API key

Auth, email, surveys, and journeys share one user record, so you ship this without stitching vendors together.

Start free