Sign in 中文
All features

API Client

A local API client built into the Unfour troubleshooting workspace

Unfour includes a local API client for sending requests, organizing API workflows, inspecting responses, and using API operations as part of MCP-assisted backend troubleshooting.

It is built for backend developers who need to move from an API symptom to server and database evidence without recreating the request context in separate tools.

Read the docs

Build, organize, and inspect API workflows

The current API Client covers everyday request work as well as scripts and collection exchange used in repeatable troubleshooting.

HTTP request building

Configure methods, URLs, query parameters, headers, request bodies, authentication, and timeouts.

Collections and folders

Save requests in collections and nested folders so a service workflow can be reused instead of rebuilt.

Environments and variables

Resolve workspace and environment variables across URLs, headers, query parameters, and request bodies.

Scripts and OpenAPI

Run pre-request and post-response scripts, review tests and console output, and import or export OpenAPI 3.x collections.

Response evidence

Inspect response bodies, headers, cookies, timing, request details, and saved request/response history.

MCP-assisted API operations

Let an approved MCP client inspect saved requests and history or send a scoped request through Unfour tools.

Connected troubleshooting

Keep the API request as the starting point, not an isolated test

Once a response exposes a timeout, error, or unexpected payload, the same workspace can carry the investigation into server and database evidence.

  1. 1. API request
  2. 2. Response evidence
  3. 3. SSH logs
  4. 4. Database state

Local-first scope

Requests run from your local Unfour workspace

Unfour is not a cloud-hosted API execution service and does not claim compatibility with every feature in other API platforms.

Request definitions, environments, and credentials stay local by default.

The local application or local MCP server performs the requested API operation.

Sensitive request and response fields are masked before MCP results are returned.

The developer chooses the request, environment, and next troubleshooting step.

Related features

Test APIs in the same workspace as the rest of the backend

Download Unfour to start with the free, open-source core.

Download Unfour Read the docs View all features