chore(backend): Add M2M token list method

[wobsoriano]

Description

Cherry picked from #7939

Changeset available in Core 2

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

Release Notes

• New Features
  • Added M2M token listing capability with pagination and filtering support. Users can now retrieve paginated lists of M2M tokens and filter by subject, revoked status, or expiration status for improved token management and discovery.

[changeset-bot]

🦋 Changeset detected

Latest commit: bf507c6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Feb 27, 2026 8:59pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b896f16 and bf507c6.

📒 Files selected for processing (1)

• .changeset/nasty-pianos-shop.md

✅ Files skipped from review due to trivial changes (1)

• .changeset/nasty-pianos-shop.md

---

📝 Walkthrough

Walkthrough

This pull request adds pagination support for listing M2M tokens in the backend API. A new list() method is introduced to the M2MTokenApi class, accepting query parameters for filtering by subject, revocation status, and expiration status. The corresponding tests expand token metadata fields and add comprehensive test coverage for the listing functionality, including authorization validation and pagination handling. The deserializer is updated to properly handle M2M token list responses, mapping them to the standard paginated response format.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly and concisely summarizes the main change: adding an M2M token list method to the backend API.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@7947

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@7947

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@7947

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@7947

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@7947

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@7947

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@7947

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@7947

@clerk/express

npm i https://pkg.pr.new/@clerk/express@7947

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@7947

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@7947

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@7947

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@7947

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@7947

@clerk/react

npm i https://pkg.pr.new/@clerk/react@7947

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@7947

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@7947

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@7947

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@7947

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@7947

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@7947

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@7947

commit: bf507c6

[jacekradko]

Don't we want an actual changeset/version bump for this?

[wobsoriano]

Oh oof, thought we want to keep the one in core 2 and not in core 3. Reverting

[jacekradko]

Did we add this changeset to core 2 already? If so, then we don't need one for core 3. Sorry for the confusion

[wobsoriano]

yes we did! deleting