Puma

Puma Thread Backtraces API

The Thread Backtraces API from Puma — 1 operation(s) for thread backtraces.

GitHub OpenAPI

Operations 1

GET /thread-backtraces Thread backtraces #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/puma/refs/heads/main/openapi/puma-thread-backtraces-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/puma-thread-backtraces-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

puma-thread-backtraces-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Puma Control/Status Application Gc Thread Backtraces API
  version: 1.0.0
  description: 'Puma ships with an optional control/status HTTP application that can be

    bound to a local TCP port or Unix socket and queried for runtime statistics

    and lifecycle control (stop, restart, halt, gc, etc.). Endpoints are

    served by Puma''s built-in status app and require a shared control token

    passed via the `token` query parameter; requests without a valid token

    receive HTTP 403.


    When the status app is started in `data_only: true` mode, only the

    read-only endpoints (`/stats` and `/gc-stats`) are enabled and all other

    paths return 404.

    '
  contact:
    name: Puma
    url: https://puma.io/
  license:
    name: BSD-3-Clause
    url: https://github.com/puma/puma/blob/master/LICENSE
servers:
- url: http://127.0.0.1:9293
  description: Default local Puma control/status server (host and port are configured by the operator).
security:
- controlToken: []
tags:
- name: Thread Backtraces
paths:
  /thread-backtraces:
    get:
      summary: Thread backtraces
      description: Returns the current thread backtraces for the Puma process as a JSON array.
      operationId: getThreadBacktraces
      responses:
        '200':
          description: JSON array of thread backtraces.
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
        '403':
          $ref: '#/components/responses/Forbidden'
      tags:
      - Thread Backtraces
components:
  responses:
    Forbidden:
      description: Missing or invalid control token.
  securitySchemes:
    controlToken:
      type: apiKey
      in: query
      name: token
      description: Shared control-app authentication token. Configured via Puma's `--control-token` option (or `auth_token` in the control app configuration). Required on every request; missing or wrong token returns 403.
externalDocs:
  description: Puma restart and control documentation
  url: https://github.com/puma/puma/blob/master/docs/restart.md