API Maker

The backend engine for the AI era

DebuggingEpisode 38 9:10 12 chapters November 2026

Debug an API from the Failing Call to the Line That Broke

Something broke at checkout. Follow one real bug from the failing call to the line that broke, with every debugging tool of API Maker: Log Explorer, stack traces that name the line, Test Hooks, Console Logs View, the queries of one call, Debug Settings, and a breakpoint in your own code.

In the playlists The complete course Testing & debugging

Chapters

What you will learn

  • Find the failing call in Log Explorer
  • Request, response, console and cURL, then replay it
  • The stack names the line, in one error format for every language
  • Test the hook alone, run it unsaved, then save
  • Console Logs View, x-am-meta, and the queries of one call
  • A breakpoint in the Debug tab: stopped on your line, safe by design
  • Native Process Logs, and why the standard keeps AI code honest
In the docsDeveloper tools
Transcript1289 words · click a time to play from there

Intro

Something broke at checkout. In this video, you follow one real bug, from the failing call to the line that broke. On the way, you use every debugging tool of API Maker.

Logs in five places

Debugging a backend usually means logs in five places. You open an SSH session to read a log file. You run docker logs on the right container. You search a log tool. You read the slow query log of each database. And when nothing helps, you add a print, deploy again, and wait. API Maker keeps the failing call, its error with your line, and its logs and queries, in one panel.

And it gives you real breakpoints, without opening a port. Here is the plan. Find the failing call. Read the stack. Test one hook alone. Follow the logs. See the queries. And stop on a breakpoint.

The bug reports

The checkout of Calm Home calls Cart Quote, a custom API in TypeScript. It reads the prices from MongoDB, and the coupon from MariaDB. It answers with the subtotal, the discount, the shipping, and the total. Shipping is free from one hundred and fifty dollars. Last week, an AI assistant added a pre hook, Normalize cart, which turns what customers type into capital letters. On Monday, support sends two reports.

Checkout fails for some carts. And one customer paid for shipping on an order of exactly one hundred and fifty.

Find the call

Start where it failed. The log profile, named Checkout, logs Cart Quote. So every call of the shop is written to the log database. Open Log Explorer, and click Failures. Only the failing calls are left. Open one. The status is five hundred: cannot read properties of undefined, reading trim. Request holds the headers and the body that the shop sent. This cart has no coupon. Response keeps the answer, because a failed call is always saved.

The cURL button copies the whole call, as a curl command. And on a call that worked, Console shows the g.logger lines of its code. Paste the command in a terminal, and the failure comes back, every time. A bug you can repeat is half fixed.

Read the stack

To work on it, open Custom API, and click Test API on Cart Quote. Paste the body of the failed call: three candles, and no coupon. Send. The answer is the standard error of API Maker: success false, the status, and the errors. Its stack lists only your code, and names the cause: the pre hook Normalize cart, line five. Every API answers its errors in this one shape, in all eight languages.

A Python error names its file and its line the same way. There are no framework lines, and no lines of compiled code. Your clients handle one format. And an AI assistant that reads the error knows exactly where to look.

Test Hooks

Now test the hook alone. Tick Test Hooks. API Testing picks the version and the hook, and the Code tab shows the code of the hook. Send runs only this hook, with the body you typed. No API, and no other hook. It crashes the same way, and line five is underlined in red. The coupon is optional, so add a question mark. Command E runs the code on the screen, before it is saved.

There is no error, and the Logs tab shows the cart, cleaned. Command S saves the hook, and saving is deploying.

Logs

Now the second report. Send the cart of the customer: a wall clock, a teapot, and two candles, with the coupon welcome five. Shipping is nine dollars ninety. The Logs tab tells the story in order: the line of the hook, then the line of the API. The subtotal is one hundred and fifty. That is right, so the rule is wrong. console.log goes somewhere else: to Console Logs View, in the top bar.

It collects what the code of the account prints, from every sandbox and every server. It can refresh itself every five seconds. Compile errors of Go, Rust, C#, Java, and Kotlin land here too. So remember three channels. g.logger lines travel with their request. You see them in the Logs tab while you test, and in the Console tab of Log Explorer in production. console.log goes to the console of the account.

And code on the native process prints to the output of the server.

Queries

Set x-am-meta to true, and send. The answer now has a meta block. It shows the time the server measured, which server, process, and port ran the code, on which runtime, and which groups allowed the call. And what did the code ask the databases? The Index Maker tab lists the calls of this run. One query on the MongoDB products, and one on the MariaDB coupons. Both use an index, and you see their count, their rows, and their time.

A query inside a loop shows up here at once. API Maker also runs its own queries while it serves a call, like a deep populate across databases, or a unique check. A scanning period records them when Log internal queries is on. The order page of the shop asks MySQL for orders, with their customers and their coupons. The analysis shows the query on MySQL, and the queries API Maker ran on PostgreSQL and MariaDB.

Breakpoints

Logs tell you what happened. A breakpoint shows it as it happens. Open the user menu, then Debug Settings. Switch it on, and save. Nothing restarts. What you send from API Testing now runs in a debug runner of its language. Open Custom API, and click Test API on Cart Quote. The Debug tab is next to Response. Put in the cart of the customer, open the code, and click left of the shipping line.

A red dot shows a breakpoint. Send. The request waits, and the code stops on your line, in your TypeScript. The values show at the ends of the lines above, and the variables say it: the subtotal is exactly one hundred and fifty. F10 steps over the line. Shipping becomes nine ninety, because greater than leaves one hundred and fifty out. Watch, call stack, and the console are in the same tab, and F11 steps into a utility class.

A paused request can wait up to an hour. The same tab debugs Python, PHP, C#, Go, Rust, Java, and Kotlin, and code on the native process. Video seventy six shows each of them. No debug port is open on the network. Only the server reaches the engines, and what you see travels inside the encrypted channel of the panel. Click Continue, and the answer comes: nine ninety. The fix is one character: greater or equal.

A second click removes the breakpoint. Command E gives shipping zero. Command S saves it, live on every server. Then switch debugging off, and save.

Native Process Logs

And when the server itself has something to say, Native Process Logs reads the output file of any server of the installation. Reload it, follow it every five seconds, or download the whole file. No SSH needed.

The standard

Both bugs are the kind an AI assistant writes in seconds. API Maker keeps that code on the standard. One error format. The hook and the line in every stack. Logs tied to their request. And the same answers, for a person or an assistant. Then lock the fix with a test case, as in the last video.

Recap

From a failing call to the line that broke. Log Explorer found the call. The stack named the line. Test Hooks tested the hook alone. Logs and queries explained the number. And a breakpoint proved it. Next, we take this code into your own editor, with the local client and VS Code. API Maker. Build faster, spend smarter, deliver better.