API Maker

The backend engine for the AI era

DebuggingEpisode 76 5:58 10 chapters November 2026

Debug Your Backend in Every Language: Breakpoints in the Browser

Set a breakpoint with a click and stop your API code on its line, in TypeScript, Python, PHP, C#, Go, Rust, Java and Kotlin: variables, console, step over, watch and call stack in the Debug tab of API Testing, in sandboxes and on the native process, with no debug port open on the network.

In the playlists The complete course Testing & debugging

Chapters

What you will learn

  • Debug Settings: one switch for the account
  • TypeScript in depth: a breakpoint, the values, the variables and the console
  • Step over, watch an expression, Continue
  • The same breakpoint in Bun, Python, PHP, C#, Go, Rust, Java and Kotlin
  • Code on the native process of the server
  • The engine of each language behind one tab
  • Safe by design: no open port, the encrypted channel of the panel
In the docsDebugging
Transcript748 words · click a time to play from there

Intro

Here is debugging in every language. You can stop your code on a line, in TypeScript, Python, PHP, C#, Go, Rust, Java, or Kotlin, and read its values, right in the admin panel. There is no debugger to install, and no port to open.

Debugging a backend, the usual way

Debugging a backend usually means a log line, a deploy, and the logs again. A different debugger for each language, set up on each laptop. A debug port opened on a server, for anyone on the network. And code that behaves one way on your laptop, and another way where it runs. With API Maker, one switch turns debugging on. A click sets a breakpoint, in any language. The code stops where it runs, in its sandbox or on the server.

And only the server reaches the debug engines. In this video: one switch, TypeScript, in depth, the same breakpoint in every other language, code on the native process, and how it stays safe.

One switch

Open the user menu, then Debug Settings. The help behind the question mark says what it does. Switch it on, and Save. Nothing restarts. What you send from API Testing now runs in a debug runner of its language.

TypeScript, in depth

Open API Testing, then Custom APIs, and Cart Total. It reads the prices of three products of the catalog, adds them up, and adds shipping, which is free from one hundred and fifty. The Debug tab sits next to Response, ready. Open the code, and click in the margin of the shipping line. A red dot shows a breakpoint. Send. The request waits on that line, and the Debug tab says where.

The values show at the ends of the lines above. Variables shows the total, one hundred and twenty eight, and the products, which you can open like any object. The console runs code where the request stopped. Here, it gives the names of the three products. Step over the line. Shipping is nine ninety, because the cart is under one hundred and fifty. Watch keeps an expression in sight, here, total plus shipping.

Click Continue, and the answer reaches API Testing.

Every other language

The same tab debugs every language that API Maker runs. Each one does the same small sum: forty, sixty, and fifty, with a breakpoint where the total is one hundred and fifty. First, Bun. Set a breakpoint, and Send. It stops, with the total in the variables. Continue. Now Python, through debugpy. The same breakpoint gives the same stop. Continue. Now PHP, through Xdebug. Set a breakpoint. It stops, with dollar total.

Continue. Now C#, through netcoredbg. Set a breakpoint. It stops. Continue. Now Go, through Delve. Set a breakpoint. It stops. Continue. Now Rust, through LLDB. Set a breakpoint. It stops. Continue. Now Java, through the debugger of the JVM. Set a breakpoint. It stops. Continue. And Kotlin, on the same JVM. Set a breakpoint. It stops. Continue.

The native process

And now TypeScript on the native process. The code runs on the server machine, for the lowest delay, not in a sandbox. Set a breakpoint, and Send. It stops the same way. Continue.

How it works

Behind the tab, each language keeps its own engine: the inspector of Node.js and Bun, debugpy, Xdebug, netcoredbg, Delve, LLDB, and the debugger of the JVM. The server speaks to each of them, and the panel speaks to the server. So you get one tab, and the same keys, F5, F10, and F11, in every language.

Safe by design

And it is safe by design. No debug port is open on the network. Only the server reaches the engines, through the agent of the runner. What the debugger shows travels inside the encrypted channel of the admin panel. And a run stops only when it asks for the debugger, on an account that is debugging. So the calls of your users never wait at a breakpoint.

Good to know

Good to know. Hooks, schedulers, and utility classes stop at their breakpoints too. Other callers ask for the debugger with the header x-am-run-in-debugger. A paused request can wait up to an hour. And a debug runner that nobody uses goes away by itself.

Recap

To sum up. One switch turns debugging on. A click sets a breakpoint, in every language. The Debug tab shows where it stopped, the variables, the console, watch, and the call stack. It works in sandboxes, and on the native process. And no port is open, because only the server reaches the engines. Next: your own editor, in sync with API Maker. API Maker. Build faster, spend smarter, deliver better.