API Clients

An index and topic collection covering API clients, the developer tools used to inspect, debug, exercise, and document APIs interactively. API clients include desktop and web applications such as Postman, Insomnia, Bruno, Hoppscotch, HTTPie, Paw, Yaak, Thunder Client, and Apidog, along with command-line HTTP clients and language-specific HTTP libraries presented as products. These tools sit between developers and APIs, providing request building, response inspection, collection management, environment variables, scripting, mocking, and team collaboration features that accelerate every stage of the API consumption and integration lifecycle.

API Clients is profiled on the APIs.io network. Tagged areas include API Client, HTTP Client, API Debugging, Developer Tools, and REST Client.

The API Clients catalog on APIs.io includes 1 JSON-LD context.

API Clients’ developer surface includes developer portal and 1 more developer resources.

9.6/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
0 APIs 8 Features 7 Use Cases
API ClientHTTP ClientAPI DebuggingDeveloper ToolsREST ClientAPI Testing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/api-clients: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 8

Notable capabilities this provider offers.

Interactive Request Building

API clients provide visual editors for composing HTTP requests with methods, URLs, headers, query parameters, and request bodies, removing the friction of hand-crafting requests...

Response Inspection and Pretty-Printing

Clients render JSON, XML, HTML, image, and binary responses with syntax highlighting, formatting, and inspection tools that make debugging and exploration far faster than raw ou...

Collections and Workspaces

Tools like Postman, Insomnia, and Bruno organize requests into named collections and shared workspaces that capture how an API is intended to be exercised end-to-end.

Environments and Variables

API clients let developers parameterize requests across environments (dev, staging, prod) using variable substitution, secret stores, and dynamic value providers.

Authentication Flows

Built-in support for Bearer tokens, API keys, Basic auth, OAuth 2.0 with PKCE, AWS SigV4, and other auth mechanisms removes the need to script authentication by hand.

Scripting, Assertions, and Testing

Pre-request and post-response scripting hooks combined with assertions turn ad-hoc requests into runnable, repeatable test suites that can be executed in CI.

Mocking and Local Development

Many clients can publish mock servers from collections or specs, letting frontend and consumer teams build against a stable contract before the real API is ready.

Specification Import and Sync

API clients import OpenAPI, AsyncAPI, GraphQL SDL, and Postman Collection formats so request libraries stay in sync with the API source of truth.

Scroll for all 8

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Api Clients Context

6 classes · 18 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

Collection

11 properties

JSON SCHEMA

HTTPRequest

11 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Api Clients Collection Structure

11 properties

JSON STRUCTURE

Api Clients Http Request Structure

11 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Use Cases 7

What developers build with this provider.

Exploring a Third-Party API

Developers use Postman, Insomnia, or HTTPie to send their first requests against a new third-party API, inspect responses, and understand its behavior before writing integration...

Debugging a Failing Integration

When a production integration fails, developers replay the failing request in a client like Bruno or Paw, tweak headers and payloads, and isolate the root cause without redeploy...

Building Reusable Request Collections

Teams curate shared collections of API requests in Postman or Insomnia workspaces so engineers, support staff, and QA can run common operations consistently.

Local Mocking for Frontend Development

Frontend teams generate mock servers from API collections or specs so they can develop UI against realistic responses before the backend is finished.

API Contract Testing in CI

Tools like Hurl, Step CI, and Postman's Newman run collections of requests with assertions as part of CI pipelines to catch regressions against contracts.

gRPC and GraphQL Exploration

Clients like Kreya, Yaak, and Insomnia provide first-class support for gRPC reflection and GraphQL introspection so developers can explore non-REST APIs interactively.

Reverse-Engineering and Traffic Capture

Tools like mitmproxy, Charles Proxy, and Fiddler capture live HTTP traffic from mobile apps, browsers, or services to understand undocumented or third-party APIs.

Scroll for all 7

Integrations 8

Pre-built integrations with other platforms and tools.

Postman

The most widely adopted API client and platform with collections, environments, mock servers, monitors, and team workspaces serving millions of developers.

Insomnia

Open-source desktop API client from Kong supporting REST, GraphQL, gRPC, and WebSocket with a strong focus on simplicity and design workflows.

Bruno

Open-source, file-based, offline-first API client that stores collections as plain text files in your git repository, making collections diffable and reviewable.

Hoppscotch

Open-source web-based API client supporting REST, GraphQL, WebSocket, SSE, and MQTT with no install required.

HTTPie

Human-friendly command-line HTTP client with intuitive syntax, JSON support, and a desktop GUI counterpart for terminal-first developers.

Paw

Native macOS API client (now part of RapidAPI) with deep macOS integration, advanced dynamic values, and code-generation across many languages.

Yaak

Modern open-source desktop client supporting REST, GraphQL, and gRPC with a focus on local-first data and offline workflows.

Apidog

All-in-one platform combining API design, debugging, mocking, and automated testing in a single workspace, often positioned as a Postman alternative.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Build 1

SDKs, sample code, and the tooling you integrate with

Source (apis.yml)

apis.yml Raw ↑
aid: api-clients
name: API Clients
description: An index and topic collection covering API clients, the developer tools used to inspect, debug, exercise, and
  document APIs interactively. API clients include desktop and web applications such as Postman, Insomnia, Bruno, Hoppscotch,
  HTTPie, Paw, Yaak, Thunder Client, and Apidog, along with command-line HTTP clients and language-specific HTTP libraries
  presented as products. These tools sit between developers and APIs, providing request building, response inspection, collection
  management, environment variables, scripting, mocking, and team collaboration features that accelerate every stage of the
  API consumption and integration lifecycle.
type: Index
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- API Client
- HTTP Client
- API Debugging
- Developer Tools
- REST Client
- API Testing
url: https://raw.githubusercontent.com/api-evangelist/api-clients/refs/heads/main/apis.yml
created: '2026-05-19'
modified: '2026-05-19'
specificationVersion: '0.19'
apis: []
network:
- name: API Dash
  url: https://raw.githubusercontent.com/api-evangelist/api-dash/refs/heads/main/apis.yml
- name: Apidog
  url: https://raw.githubusercontent.com/api-evangelist/apidog/refs/heads/main/apis.yml
- name: Axios
  url: https://raw.githubusercontent.com/api-evangelist/axios/refs/heads/main/apis.yml
- name: Bruno
  url: https://raw.githubusercontent.com/api-evangelist/bruno/refs/heads/main/apis.yml
- name: Charles Proxy
  url: https://raw.githubusercontent.com/api-evangelist/charles-proxy/refs/heads/main/apis.yml
- name: cURL
  url: https://raw.githubusercontent.com/api-evangelist/curl/refs/heads/main/apis.yml
- name: Fiddler
  url: https://raw.githubusercontent.com/api-evangelist/fiddler/refs/heads/main/apis.yml
- name: Firecamp
  url: https://raw.githubusercontent.com/api-evangelist/firecamp/refs/heads/main/apis.yml
- name: Got
  url: https://raw.githubusercontent.com/api-evangelist/got/refs/heads/main/apis.yml
- name: Hoppscotch
  url: https://raw.githubusercontent.com/api-evangelist/hoppscotch/refs/heads/main/apis.yml
- name: HTTP Client
  url: https://raw.githubusercontent.com/api-evangelist/http-client/refs/heads/main/apis.yml
- name: HTTPie
  url: https://raw.githubusercontent.com/api-evangelist/httpie/refs/heads/main/apis.yml
- name: HTTPX
  url: https://raw.githubusercontent.com/api-evangelist/httpx/refs/heads/main/apis.yml
- name: Hurl
  url: https://raw.githubusercontent.com/api-evangelist/hurl/refs/heads/main/apis.yml
- name: Insomnia
  url: https://raw.githubusercontent.com/api-evangelist/insomnia/refs/heads/main/apis.yml
- name: Kreya
  url: https://raw.githubusercontent.com/api-evangelist/kreya/refs/heads/main/apis.yml
- name: Microcks
  url: https://raw.githubusercontent.com/api-evangelist/microcks/refs/heads/main/apis.yml
- name: Milkman
  url: https://raw.githubusercontent.com/api-evangelist/milkman/refs/heads/main/apis.yml
- name: Mitmproxy
  url: https://raw.githubusercontent.com/api-evangelist/mitmproxy/refs/heads/main/apis.yml
- name: Nightingale
  url: https://raw.githubusercontent.com/api-evangelist/nightingale/refs/heads/main/apis.yml
- name: Node-Fetch
  url: https://raw.githubusercontent.com/api-evangelist/node-fetch/refs/heads/main/apis.yml
- name: OkHttp
  url: https://raw.githubusercontent.com/api-evangelist/okhttp/refs/heads/main/apis.yml
- name: Paw
  url: https://raw.githubusercontent.com/api-evangelist/paw/refs/heads/main/apis.yml
- name: Postman
  url: https://raw.githubusercontent.com/api-evangelist/postman/refs/heads/main/apis.yml
- name: RapidAPI
  url: https://raw.githubusercontent.com/api-evangelist/rapidapi/refs/heads/main/apis.yml
- name: ReadyAPI
  url: https://raw.githubusercontent.com/api-evangelist/readyapi/refs/heads/main/apis.yml
- name: ReqBin
  url: https://raw.githubusercontent.com/api-evangelist/reqbin/refs/heads/main/apis.yml
- name: Requests
  url: https://raw.githubusercontent.com/api-evangelist/requests/refs/heads/main/apis.yml
- name: REST Assured
  url: https://raw.githubusercontent.com/api-evangelist/rest-assured/refs/heads/main/apis.yml
- name: REST Client
  url: https://raw.githubusercontent.com/api-evangelist/rest-client/refs/heads/main/apis.yml
- name: RestSharp
  url: https://raw.githubusercontent.com/api-evangelist/restsharp/refs/heads/main/apis.yml
- name: Restfox
  url: https://raw.githubusercontent.com/api-evangelist/restfox/refs/heads/main/apis.yml
- name: Retrofit
  url: https://raw.githubusercontent.com/api-evangelist/retrofit/refs/heads/main/apis.yml
- name: Scalar
  url: https://raw.githubusercontent.com/api-evangelist/scalar/refs/heads/main/apis.yml
- name: Step CI
  url: https://raw.githubusercontent.com/api-evangelist/step-ci/refs/heads/main/apis.yml
- name: Stoplight
  url: https://raw.githubusercontent.com/api-evangelist/stoplight/refs/heads/main/apis.yml
- name: Thunder Client
  url: https://raw.githubusercontent.com/api-evangelist/thunder-client/refs/heads/main/apis.yml
- name: Voiden
  url: https://raw.githubusercontent.com/api-evangelist/voiden/refs/heads/main/apis.yml
- name: Wget
  url: https://raw.githubusercontent.com/api-evangelist/wget/refs/heads/main/apis.yml
- name: Xh
  url: https://raw.githubusercontent.com/api-evangelist/xh/refs/heads/main/apis.yml
- name: Yaak
  url: https://raw.githubusercontent.com/api-evangelist/yaak/refs/heads/main/apis.yml
common:
- type: Portal
  url: https://apievangelist.com
- type: GitHubOrganization
  url: https://github.com/api-evangelist
- type: Features
  data:
  - name: Interactive Request Building
    description: API clients provide visual editors for composing HTTP requests with methods, URLs, headers, query parameters,
      and request bodies, removing the friction of hand-crafting requests in code.
  - name: Response Inspection and Pretty-Printing
    description: Clients render JSON, XML, HTML, image, and binary responses with syntax highlighting, formatting, and inspection
      tools that make debugging and exploration far faster than raw output.
  - name: Collections and Workspaces
    description: Tools like Postman, Insomnia, and Bruno organize requests into named collections and shared workspaces that
      capture how an API is intended to be exercised end-to-end.
  - name: Environments and Variables
    description: API clients let developers parameterize requests across environments (dev, staging, prod) using variable
      substitution, secret stores, and dynamic value providers.
  - name: Authentication Flows
    description: Built-in support for Bearer tokens, API keys, Basic auth, OAuth 2.0 with PKCE, AWS SigV4, and other auth
      mechanisms removes the need to script authentication by hand.
  - name: Scripting, Assertions, and Testing
    description: Pre-request and post-response scripting hooks combined with assertions turn ad-hoc requests into runnable,
      repeatable test suites that can be executed in CI.
  - name: Mocking and Local Development
    description: Many clients can publish mock servers from collections or specs, letting frontend and consumer teams build
      against a stable contract before the real API is ready.
  - name: Specification Import and Sync
    description: API clients import OpenAPI, AsyncAPI, GraphQL SDL, and Postman Collection formats so request libraries stay
      in sync with the API source of truth.
- type: UseCases
  data:
  - name: Exploring a Third-Party API
    description: Developers use Postman, Insomnia, or HTTPie to send their first requests against a new third-party API, inspect
      responses, and understand its behavior before writing integration code.
  - name: Debugging a Failing Integration
    description: When a production integration fails, developers replay the failing request in a client like Bruno or Paw,
      tweak headers and payloads, and isolate the root cause without redeploying code.
  - name: Building Reusable Request Collections
    description: Teams curate shared collections of API requests in Postman or Insomnia workspaces so engineers, support staff,
      and QA can run common operations consistently.
  - name: Local Mocking for Frontend Development
    description: Frontend teams generate mock servers from API collections or specs so they can develop UI against realistic
      responses before the backend is finished.
  - name: API Contract Testing in CI
    description: Tools like Hurl, Step CI, and Postman's Newman run collections of requests with assertions as part of CI
      pipelines to catch regressions against contracts.
  - name: gRPC and GraphQL Exploration
    description: Clients like Kreya, Yaak, and Insomnia provide first-class support for gRPC reflection and GraphQL introspection
      so developers can explore non-REST APIs interactively.
  - name: Reverse-Engineering and Traffic Capture
    description: Tools like mitmproxy, Charles Proxy, and Fiddler capture live HTTP traffic from mobile apps, browsers, or
      services to understand undocumented or third-party APIs.
- type: Integrations
  data:
  - name: Postman
    description: The most widely adopted API client and platform with collections, environments, mock servers, monitors, and
      team workspaces serving millions of developers.
  - name: Insomnia
    description: Open-source desktop API client from Kong supporting REST, GraphQL, gRPC, and WebSocket with a strong focus
      on simplicity and design workflows.
  - name: Bruno
    description: Open-source, file-based, offline-first API client that stores collections as plain text files in your git
      repository, making collections diffable and reviewable.
  - name: Hoppscotch
    description: Open-source web-based API client supporting REST, GraphQL, WebSocket, SSE, and MQTT with no install required.
  - name: HTTPie
    description: Human-friendly command-line HTTP client with intuitive syntax, JSON support, and a desktop GUI counterpart
      for terminal-first developers.
  - name: Paw
    description: Native macOS API client (now part of RapidAPI) with deep macOS integration, advanced dynamic values, and
      code-generation across many languages.
  - name: Yaak
    description: Modern open-source desktop client supporting REST, GraphQL, and gRPC with a focus on local-first data and
      offline workflows.
  - name: Apidog
    description: All-in-one platform combining API design, debugging, mocking, and automated testing in a single workspace,
      often positioned as a Postman alternative.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
humanURL: https://apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/api-clients"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/api-clients/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/api-clients/evidence"

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.

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