REST · GraphQL · WebSockets

The API client that keeps working when you stop

Build and send API requests from your browser, chain them into workflows, and schedule them to run on their own - every few minutes, every Monday, or on any cron expression. Nothing to install.

  • Free forever plan
  • No card needed
  • Runs in any browser
API Buddy in the browser: a folder tree of saved requests on the left, and a JSON request with its formatted response side by side

Features

Everything you reach for, every day

A fast, focused API client for testing and debugging - with the automation built in, not bolted on.

Every kind of request

REST and GraphQL over HTTP, WebSockets, and GraphQL subscriptions over WebSocket - with JSON, plain-text, form-data and file-upload bodies.

Environments & variables

Write {{BASE_URL}} once, then switch between local, staging and production in a click. Clone an environment to start a new one.

Chain requests together

Pull a token, an ID or anything else out of a response - by JSON path, header or regex - and use it in the next request automatically.

Request history

The last ten responses of every saved request, kept for you - so "what did it return earlier?" is one click away.

Organised your way

Folders and sub-folders, drag-and-drop ordering, search, and your most recent requests always at the top.

Secrets stay secret

Sensitive variables are asked for when you send, never saved, and blanked out of history and responses.

Import your whole API

Bring in an OpenAPI or Swagger spec - upload it, paste it or link to it - and every endpoint becomes a ready-to-send request, in folders, with its environment set up.

Built-in values

Drop {{$uuid}}, {{$timestamp}} or {{$isoDate}} into any request for a fresh value every time it's sent - no scripting needed.

Cookies, handled

Switch on cookie saving for an environment and every cookie a response sets becomes a variable - log in once, and the session is ready for your next request.

Workflows

Turn a handful of requests into one click

Line up your saved requests into a workflow, and each step hands what it learned to the next: log in, fetch the account, create the order, check the result.

  • Pass values along - tokens and IDs flow from one step's response into the next step's request.
  • Check every response - expect a status code, require values to be found, and assert on what comes back.
  • Stop or carry on - a failing step stops the run, unless you tell it to keep going.
  • Watch it live - every step's status, timing and response appear as it runs.
A three-step workflow run - log in, fetch the account, check the balance - with each step's status, timing and the variables it passed to the next

Schedules

Set it running, and get on with your day

Schedule any workflow and it runs on our servers - while your laptop is closed, overnight, at weekends. It's API monitoring without another tool to learn - and it tells you when something breaks.

  • Every few minutes, hours or days - for health checks and keep-alives.
  • Weekly at a set time - "every Monday at 09:00".
  • Any cron expression - with a preview of its next run times, so you know it's right.
  • Once, at a date and time - for the job that just needs doing later.
  • Alerts when it matters - an email, or a signed webhook to Slack or your own system, when a run fails, succeeds, or both.
A workflow's schedules: every 15 minutes, weekly on Mondays at 09:00, and a cron expression showing its next run times

Environments

One set of requests, every environment

Keep the URLs, keys and IDs that change between environments in variables, and switch which environment is active in a click. Your requests stay exactly the same.

  • Sensitive variables - passwords and API keys are asked for at send time and never stored.
  • Sensitive responses - mark a request so its responses are never kept in history.
  • Clone in a click - copy staging to make a new environment, then change what's different.
  • Edit values beside your request - change a variable and send again, without opening a dialog.
The environments editor with Staging selected: a BASE_URL variable, and an API_KEY variable marked sensitive

Teams Premium

Share the work, not the passwords

Link your account with your teammates', then share folders of requests and whole environments with them - read-only, or with permission to edit.

  • Read or edit access - per folder and per environment, and you can take it back at any time.
  • Your variables stay yours - shared requests always run with the variables of the account that owns them.
Sharing a folder of requests with a teammate, choosing between read-only and edit access

How it works

From first request to fully automated in minutes

  1. Import or build your requests

    Import an OpenAPI spec in seconds, or pick REST, GraphQL or WebSocket, fill in the URL and body, and hit Send.

  2. Chain it into a workflow

    Add your saved requests as steps, pull values from one response into the next, and add checks.

  3. Schedule it

    Choose when it runs. API Buddy does the rest, and keeps every run's results for you to look back on.

Pricing

Simple, yearly, and never automatic

Pay once for a year - nothing renews by itself. Start on the free plan and upgrade from inside the app whenever you need more.

Free

£0 forever

Everything you need to start sending and saving requests.

  • 10 saved requests
  • No scheduled workflows
  • 30 run credits an hour
  • Environments, variables and request history
Start free

Basic

£10 / year

For regular use, with a scheduled workflow doing the dull bits.

  • 50 saved requests
  • 1 scheduled workflow
  • 120 run credits an hour
  • Environments, variables and request history
  • Keeps the last 1 run of each workflow
Get Basic

How run credits work

Every request you send costs one credit - on its own, or as a workflow step - and your balance refills every hour at your plan's rate, up to two hours' worth. Need a burst? Additional credits can be purchased on-demand.

FAQ

Questions, answered

What is API Buddy?

An API client that runs in your browser. Build and send REST, GraphQL and WebSocket requests, keep them organised in folders, switch between environments, and chain requests together into workflows that can run on a schedule.

Do I need to install anything?

No. API Buddy runs entirely in your web browser, on any operating system - there is nothing to download, and your saved requests are there on any computer you sign in from.

Is there a free plan?

Yes - the Free plan is free forever, with low usage limits for saved requests and run credits an hour. You can also try API Buddy without an account: a guest account is deleted, with everything in it, after 24 hours.

What are run credits?

Every request you send costs one credit, whether you send it yourself or it runs as a step in a workflow. Your balance refills continuously at your plan's hourly rate (e.g. 60 credits an hour), up to two hours' worth. If you need more, credit packs never expire, and are only used once your runtime balance has run out.

How do workflows and schedules work?

A workflow runs a series of saved requests in order. Each step can pull values out of its response - from a JSON path, a header, or a regular expression - into variables the next steps use, and can check the response with assertions - a failing step stops the workflow, unless you tell it to carry on. Run a workflow whenever you like, or schedule it every few minutes, hours or days, weekly at a set time, with a cron expression, or once at a date and time. Workflows run on our servers, so they keep going when your laptop is closed.

Will I know if a scheduled workflow fails?

Yes. Add alerts to any workflow: email addresses, or URLs to send a webhook to - for runs that fail, runs that succeed, or both. Webhooks are signed, so you can check they really came from API Buddy, and an email address other than your own is only sent alerts once its owner confirms it.

Can I import my existing API?

Yes - from an OpenAPI 3 or Swagger 2 spec, in JSON or YAML: upload the file, paste it, or give its URL. Each operation becomes a request, in a folder per tag, with an environment holding the base URL and the variables they use. You see exactly what will be created before anything is saved.

How are passwords and API keys kept safe?

Mark a variable as sensitive and its value is never saved: API Buddy asks for it when you run a request, uses it, and blanks it out of the request history and the response. You can also mark a request's responses as sensitive, so they are never stored in its history.

Can it reach APIs on my own computer or private network?

HTTP and GraphQL requests are sent from API Buddy's servers, so the API needs to be reachable from the internet - and browser CORS rules never get in the way. WebSocket connections are made straight from your browser.

Can I share requests with my team?

Yes, on the Premium plan. Link your account with a teammate's, then give them read-only or edit access to folders of requests and to environments. Requests always use the variables of the account that owns them.

Is it a subscription?

No. Basic (£10) and Premium (£50) are a one-off payment for a year, taken securely by Stripe. Nothing renews automatically - when the year is up, your account moves back to the Free plan unless you choose to buy another year.

How is API Buddy different from Postman or Insomnia?

If you have used either, you will feel at home. API Buddy runs in your browser with nothing to install, has a free plan, and its workflows run on our servers on a schedule - so the same requests you build by hand can monitor an API around the clock.

Your next request could be your last manual one

Start free in seconds - no card, nothing to install.