API Maker
The backend engine for the AI era
Developer toolsEpisode 78 7:16 11 chapters November 2026
Every code editor of the API Maker admin panel opens an IDE: every file of your repository in tabs, go to definition in TypeScript, Python and every other language, search in all the files, saves into the items, the debugger, and git blame with the history of each file.
In the playlists The complete course Developer workflow
Here is the IDE of the admin panel. Every file of your code is in one editor. You get tabs, search, go to definition in every language, the debugger, and who wrote each line.
Changing the code of a backend is usually slow. You need a clone of the repository on each laptop, with the tools of each language. A web editor shows one file at a time. Search stops at the page you are on. And you cannot jump from a call to the code it calls. With API Maker, every code editor of the panel opens an IDE. It has every file of your account, in tabs.
It has search, and go to definition in every language. And it has the debugger and the Git history, in the same window. In this video: the IDE around a page, go to definition, back and forward, go to file, and search, a save and a run, the debugger, who wrote each line, and the IDE page of the dashboard.
Open API Testing, then Custom APIs, and Order Quote. It gives the price of a cart, in TypeScript. Open its code. Every code editor of the panel now has three buttons. Types loads its types again. IDE opens the IDE. And the zoom fills the page. Click IDE. The code of the page is the first tab, pinned. The page still saves it. Around it are the files of your repository, as Git keeps them.
There is a folder for each kind of item: custom APIs, utility classes, schemas, and migrations. And at the root are the projects of each language. The other files of this item are read only here, because their page saves them. And below are the tabs of API Testing.
Order Quote calls the utility class Tax. Click on add, and press F12. The class opens in its own tab, at its method, and the explorer shows where it lives. Back goes to the code of the page, and forward goes there again. Back and forward walk through every place you went, across files.
Command P opens go to file. Type a few letters of a name, in order, and Order Status opens. It is a custom API in Python. It rounds with cents, and F12 opens the utility class Rounding, in Python too. Go to definition works in all eight languages: for a name in the same file, a utility class, or the declarations of API Maker. Command Shift F searches every file at once.
Search for the word round. You see the lines of the class in TypeScript, of the class in Python, and of the API that uses it. You can match case, whole words, and regular expressions. A click opens the file, at its line.
Now a change. In the explorer, open utility classes, then pricing, then Tax. The tax on home goods drops to twelve percent. The dot on the tab means it is not saved yet. Command S saves it into the utility class, with the checks of its page, and every editor gets its new types. Back to Order Quote. Click Send, in the bar of the IDE. The answer arrives in the panel below the editor, with the new tax.
The panel holds the tabs of API Testing: the response, the logs, the docs, and Index Maker, with the database calls of the run. Command J folds it away.
With debugging on, the IDE is a debugger too. A click in the margin sets a breakpoint. Send, and the code stops on the line. The bar of the IDE holds Continue and the steps. The values show at the ends of the lines, and the Debug tab shows the variables, the call stack, and the console. Step over, to the shipping. Then step into. The debugger follows the code into the utility class Tax, in its own tab, at the line it runs, with its amount.
Click Continue, and the answer comes.
The account keeps its code in Git. Option A annotates the file with git blame. Each line shows its day and its author, and its color shows its age. The lines of today say not committed yet. Put the mouse on the line of Arjun, and you see his commit, and its message. A click opens the history of the file at his commit. It shows what he changed: the shipping fee.
Pick the first version, by Nisha, and compare it with the database. You see everything that changed since. Revert writes a version back into the database, for you to review and commit. Close it.
The IDE also has its own page. The IDE tile of the dashboard opens it on the whole repository, with no page around it. No file is open yet. Use go to file, type tax, and it opens. Dashboard, in its bar, goes back to where you came from.
No key of the IDE is a key of the browser. Command P goes to a file. Command Shift F searches. Command B shows the side, and Command J the panel. Option W closes a tab, and Option A annotates. Command S saves, and Command Option S saves them all. On Windows and Linux, use Control and Alt. Every save of the IDE goes through the checks of the page of its item.
Settings are checked, and code is compiled. If a file was saved somewhere else since you opened it, it asks what to keep. So nobody overwrites anybody by accident. And the code that an AI assistant wrote is reviewed where it lives, with go to definition, the debugger, and who wrote each line.
To sum up. Every code editor opens an IDE around the code of its page. You get go to definition, back and forward, in every language. You get go to file, and search in every file. You save into the items, run in its panel, and use the debugger. And you see who wrote each line, and the history of every file. Next: your own editor, in sync with API Maker.
API Maker. Build faster, spend smarter, deliver better.
Length 4:57Local client
Length 5:58Debugging
Length 4:55Developer tools
Length 6:28Git