github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #8546] [CLOSED] feat: expose /api-key/verify to clients #24953

New Issue
Closed
opened 2026-04-15 22:39:10 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 22:39:10 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/8546
Author: @heiwen
Created: 3/11/2026
Status: ❌ Closed

Base: canary ← Head: feat--expose-api-key-verify-to-clients

📝 Commits (1)

  • 6e211c4 feat: expose /api-key/verify to clients

📊 Changes

2 files changed (+2 additions, -0 deletions)

View changed files

📝 packages/api-key/src/client.ts (+1 -0)
📝 packages/api-key/src/routes/verify-api-key.ts (+1 -0)

📄 Description

Added POST /api-key/verify as a concrete API key route and registered it in the API key client plugin. This enables client-side access to API key verification through authClient.apiKey.verify(...) and supports HTTP-based verification flows that were not previously available.

Fixes: https://github.com/better-auth/better-auth/issues/8535

Summary by cubic

Exposed POST /api-key/verify to clients. Apps can now call authClient.apiKey.verify(...) to verify API keys over HTTP.

Written for commit 6e211c4cdd. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/8546 **Author:** [@heiwen](https://github.com/heiwen) **Created:** 3/11/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `feat--expose-api-key-verify-to-clients` --- ### 📝 Commits (1) - [`6e211c4`](https://github.com/better-auth/better-auth/commit/6e211c4cdd1d70ef508af66303b19d633c2f5956) feat: expose /api-key/verify to clients ### 📊 Changes **2 files changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/api-key/src/client.ts` (+1 -0) 📝 `packages/api-key/src/routes/verify-api-key.ts` (+1 -0) </details> ### 📄 Description Added POST /api-key/verify as a concrete API key route and registered it in the API key client plugin. This enables client-side access to API key verification through authClient.apiKey.verify(...) and supports HTTP-based verification flows that were not previously available. Fixes: https://github.com/better-auth/better-auth/issues/8535 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Exposed POST `/api-key/verify` to clients. Apps can now call `authClient.apiKey.verify(...)` to verify API keys over HTTP. <sup>Written for commit 6e211c4cdd1d70ef508af66303b19d633c2f5956. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 22:39:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#24953
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?