{
  "opencollection": "1.0.0",
  "info": {
    "name": "Clerk Backend Account Portal M2M Tokens API",
    "version": "2025-11-10"
  },
  "request": {
    "auth": {
      "type": "bearer",
      "token": "{{bearerToken}}"
    }
  },
  "items": [
    {
      "info": {
        "name": "M2M Tokens",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Get M2M Tokens",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.clerk.com/v1/m2m_tokens",
            "params": [
              {
                "name": "subject",
                "value": "",
                "type": "query"
              },
              {
                "name": "revoked",
                "value": "",
                "type": "query"
              },
              {
                "name": "expired",
                "value": "",
                "type": "query"
              },
              {
                "name": "limit",
                "value": "",
                "type": "query"
              },
              {
                "name": "offset",
                "value": "",
                "type": "query"
              }
            ]
          },
          "docs": "Fetches M2M tokens for a specific machine.\n\nOnly tokens created with the opaque token format are returned by this endpoint. JWT-format M2M tokens are stateless and are not stored.\n\nThis endpoint can be authenticated by either a Machine Secret Key or by a Clerk Secret Key.\n\n- When fetching M2M tokens with a Machine Secret Key, only tokens associated with the authenticated machine can be retrieved.\n- When fetching M2M tokens with a Clerk Secret Key, tokens for any machine in the instance can be re"
        },
        {
          "info": {
            "name": "Create a M2M Token",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.clerk.com/v1/m2m_tokens",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Creates a new M2M Token. Must be authenticated via a Machine Secret Key."
        },
        {
          "info": {
            "name": "Revoke a M2M Token",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.clerk.com/v1/m2m_tokens/:m2m_token_id/revoke",
            "params": [
              {
                "name": "m2m_token_id",
                "value": "",
                "type": "path"
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Revokes a M2M Token.\n\nThis endpoint only revokes stored opaque-format M2M tokens. JWT-format M2M tokens are stateless and cannot be revoked.\n\nThis endpoint can be authenticated by either a Machine Secret Key or by a Clerk Secret Key.\n\n- When revoking a M2M Token with a Machine Secret Key, the token must managed by the Machine associated with the Machine Secret Key.\n- When revoking a M2M Token with a Clerk Secret Key, any token on the Instance can be revoked."
        },
        {
          "info": {
            "name": "Verify a M2M Token",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://api.clerk.com/v1/m2m_tokens/verify",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Verifies a M2M Token.\n\nThis endpoint can be authenticated by either a Machine Secret Key or by a Clerk Secret Key.\n\n- When verifying a M2M Token with a Machine Secret Key, the token must be granted access to the Machine associated with the Machine Secret Key.\n- When verifying a M2M Token with a Clerk Secret Key, any token on the Instance can be verified."
        }
      ]
    }
  ],
  "bundled": true
}