API Maker

The backend engine for the AI era

Local clientEpisode 39 4:57 12 chapters November 2026

Code Your Backend in VS Code: Two-Way Sync with the Local Client

The panel is not the only place to write code. The local client keeps a folder on your computer and API Maker in step, both ways, in VS Code, WebStorm or any editor, with the types of your tables in it. A sync token, a clone, npm run start, and every save lands on the other side.

In the playlists The complete course Developer workflow

Chapters

What you will learn

  • A sync token
  • The folder, in sync: git clone and npm run start
  • Typed tables, in VS Code
  • A change from the editor, in the panel
  • A change from the panel, in VS Code
  • A team on one sync token: who changed what, who is connected
  • An encrypted channel: the sync token never travels
  • Offline work, merged
In the docsYour own editor
Transcript717 words · click a time to play from there

Intro

The panel is not the only place to write code. The local client keeps a folder on your computer in sync with API Maker, both ways. It works in VS Code, WebStorm, or any editor, and the types of your tables come with it.

Your own editor, the usual way

Working in your own editor is usually hard. You copy code between the browser and your files. Your local setup never quite matches the server. The rows of your databases have no types. And your editor does not know the platform. With API Maker, you need a clone of the repository of the account, and one command. A save on either side reaches the other side in a second. Every table and every call of g has types, in the editor you like.

In this video: a sync token, the folder, the code in VS Code, a change from the editor, a change from the panel, a team on one sync token, and what happens offline.

A sync token

In the user menu, open Local Client Sync Token. Click Generate, and confirm. The token is shown only this once, so it is blurred here. Copy it. The dialog says what comes next. Clone the Git repository of the account, and write a config file with the token. Then run npm install once, and npm run start.

The folder

Clone the repository, write the config file, install the type files of Node.js for the editor, and start the local client. It connects, and writes every file of the account. From now on, it watches both sides. The folder is the repository. am-types holds the types of API Maker, src holds the account, and there are project files for every language. Inside src, there are the custom APIs, one folder each, with the code, its settings, and its docs.

Next to them are the schemas, the instances, the groups, and the security report.

The code in VS Code

Here is Cart Quote, in VS Code. g has types. The query of products answers with the rows of the products schema, with its columns, and the docs of the call. The editor knows the platform, and the tables.

A change from the editor

Marketing wants free shipping from one hundred and twenty. We change it to one hundred and twenty. Save. The local client sends the file, and API Maker saves Cart Quote. In the panel, open Cart Quote, and its code. It already says one hundred and twenty.

A change from the panel

Now the other way. The shipping fee becomes seven point nine, and we save it in the panel. The local client writes the file, and VS Code shows it: seven point nine. Nobody copied anything.

A team, one sync token

Many developers can sync the same account at once, each in their own editor, with the same sync token. When one of them saves, the others get the change a moment later. Every line says where it came from: the panel, a Git pull, or another computer. It also says who joins and who leaves. And the bar of the admin panel shows who is connected.

Encrypted, end to end

The local client talks to API Maker inside the encrypted channel of the panel. The sync token never travels. The local client proves that it knows it, and the server proves it back. So nothing is sent to anybody else. Whatever it receives, it writes only inside its own folder. And a new sync token disconnects every local client at once.

Offline, and merged

Work done while the client was stopped is merged when it starts again. The newer change of a file wins, and what it replaces is kept in dot local client slash backups. The config file with its token, node modules, and coverage never go to Git.

Built on standards

The folder is the repository of the account. What you see is what is reviewed, and pulled on every server. Every account has the same layout, so a person or an AI assistant finds their way. And npm run test runs the tests from the same folder.

Recap

To sum up. You need a sync token, a clone, and npm run start. A save on either side reaches the other. Every table and every call of g has types in your editor. A whole team can share one token, encrypted. And offline work is merged, with nothing lost. Next: API Maker and AI, in the same folder. API Maker. Build faster, spend smarter, deliver better.