API Maker
The backend engine for the AI era
LoggingEpisode 45 5:53 11 chapters November 2026
Every call of your APIs written down: who called, what was sent, what came back, and what the code printed. Choose what is logged with a log profile, search and filter, open the detail of a call, follow calls live, and clean up old logs.
In the playlists The complete course Run in production
Every call of your APIs can be written down. Who called, what was sent, what came back, and what the code printed. In this video, we look at logging, and the Log Explorer.
Logs are usually hard to use. Logger lines are added to every endpoint, by every developer in their own way. Log files are searched with grep, server by server. And nobody can tie a console line to the call that printed it. With API Maker, a log profile says what is logged, without one line of code. Every call goes to one log database, and you search it from the panel.
And each call keeps its request, its answer, and its console lines together. In this video: a log profile, what a log entry holds, search and filters, the details of a call, live tail, and the clean up of old logs.
From the dashboard, open Log Profile. There is no profile yet, so nothing is logged. Click Add New. Name it Storefront, and make it Active. Only the active profile of the account writes logs. Save it. Select it to see what it logs, by kind of API. Under Instance APIs, pick All Instances, every API of every table. Under Custom APIs, pick Cart Quote, with Log Response, so its answers are kept too.
The green save icon saves the profile. No code, and no deploy.
Every call that the profile names becomes one entry. It has the API, its status, the time it took, and the API user. It has the request, the answer when the profile keeps it, and the console lines of its code. Entries wait in memory, and leave in batches, at most five seconds later, for their own log database. If the log database is slow, or down, it never slows an API.
A batch that fails is dropped.
Open Log Explorer. For this hour, you see every call, and the ones that failed. You also see the calls of the shop, and the queries that the code of Cart Quote made. The slash key jumps to the search. Type customers, and press Enter. We get four calls. The sidebar counts the values of every field. Leave out GET, and we see two sign ups, refused. Save keeps this search in the browser, with a name.
Click Clear all, then Failures. We get four calls: the two sign ups, and two carts with an unknown coupon. Show every call again, sort by time, with the slowest first. One click brings the saved search back.
Pick the failures, and the first refused sign up. It has two errors: no city, and a status two letters too long. Then you see the time it took, the API user, and the request id. Request shows the headers it came with, with its token blurred here, and the body it sent. Response is kept, because the call failed, even though the profile keeps no answer of instance APIs.
Press Escape. Among the calls that worked, open a read of customers. No answer is kept, and the drawer says why. Close it. Now open a Cart Quote call. Its answer is kept, because Log Response is on. And Console shows the lines that its hook and its code wrote, for this call only.
In Custom APIs, the row of an API that the profile logs has a button, View logs. It opens the Log Explorer on Cart Quote alone, in a new tab. The address holds the whole view, so it is a link a colleague can open. Turn on Live tail. The shop keeps calling, and the new calls come in every five seconds. Pick All logs to see every API, still live.
Then turn Live tail off.
Old logs are removed on a schedule. As the root user, open Deployment Settings, then Logging. It sets the log database, when old logs are removed, with a cron of six fields, every day at midnight by default, and how many entries each administrator keeps, a hundred thousand by default. Set every day at three, and fifty thousand entries. Here we discard it, so nothing is saved.
Good to know. CSV and JSON download the calls of the search, up to twenty thousand. Events, schedulers, and web socket events are logged by the same profile. A request id from an error report finds its call in one search. And Clear deletes every log of the account, after you confirm.
What is logged is a setting next to the code, not lines inside it. Every call is written the same way, in one place, with its console lines. So an API that an AI assistant writes is logged like every other. There is nothing to add, and nothing to forget.
To sum up. A log profile chooses what is logged. There is one entry for each call, in its own database. You get search, filters, and saved searches. You see the request, the answer, and the console of a call. And you get live tail, and the clean up of old logs. Next: sandboxes and runtimes. API Maker. Build faster, spend smarter, deliver better.
Length 6:36Sandboxes
Length 10:58By mail
Length 8:36Heavy APIs
Length 6:16Per admin