Skip to content
APIForge
Get started

API workspace for teams

Where APIs get forged.

Build requests, document endpoints and keep watch over them, in one shared workspace for your whole team.

Get started Log in

Requests · Docs · Monitors · Webhooks

acme / payments-api / users
GET api.example.com/v1/users/42 Send
ParamsHeadersAuthBody
200 OK184 ms1.2 KB 
{
  "id": 42,
  "name": "Ada Lovelace",
  "role": "developer",
  "active": true
}

01 — What is inside

Everything an API team reaches for, in one place.

From the first request to published documentation and ongoing monitoring, your team works from the same page.

Request builder

Send it. Read it. Save it.

Compose HTTP requests with headers, auth and a body, inspect the response, then save the useful ones into collections.

Documentation

Docs that stay true.

Describe endpoints next to the requests that test them, and publish a page when it is ready.

Monitoring

Hear it first.

Schedule checks against your endpoints and see failures at a glance.

Webhooks

Retries built in.

Failed deliveries are retried automatically, so a bad moment does not become a lost event.

Teams

The right access.

Invite teammates and give each person a role, so everyone can do their job and nothing more.

Also included Collections Environments Request history API keys Workspaces

02 — How it works

From first request to live monitoring in three steps.

  1. Step 1: Create a workspace

    Sign up, create a workspace and invite your team. Start a project for each API you work on.

  2. Step 2: Build and save requests

    Use the request builder to send requests, then save the useful ones into collections.

  3. Step 3: Document and monitor

    Publish documentation, schedule checks and add webhooks so you hear about problems early.

03 — Security

Safe by default, not by afterthought.

APIForge sends requests on your behalf, so it is built to protect your data and your network.

  • SSRF protection

    Requests to internal and loopback addresses are blocked before they are sent.

  • Encrypted secrets

    Secret environment variables are encrypted at rest.

  • Role-based permissions

    Viewer, developer and admin roles control who can see and change what.

  • Secret redaction

    Sensitive values are redacted from stored request history.

Start forging.

Create an account and set up your first workspace in a few minutes.

Get started Log in