API Maker
The backend engine for the AI era
Management APIEpisode 72 5:50 11 chapters November 2026
One call from your sign-up system makes an admin account of API Maker: its Git repository pulled, its secret saved and a deployment hook, with nobody in the panel. Turn the API on, make an account, change its owner and its secret, remove it, read every refusal, and keep the token safe.
In the playlists The complete course Run in production
You can create accounts from your own code. One call from your sign up system makes an admin account of API Maker. Its Git repository is pulled, its secret is saved, and it gets a deployment hook. Nobody needs to use the panel.
Onboarding a customer by hand takes many steps. Root signs in and adds the account. Root sets its Git repository, and pulls it. Root writes its secret. And root makes its deployment hook, for every customer. With the API of API Maker, your sign up system makes the account in one call. Its repository is pulled. Its secret is saved. And the address that deploys it comes in the answer.
In this video: turn it on, one call, what it made, a new owner, and a new secret, an account removed, when it refuses, and how to keep it safe.
As root, open Deployment Settings. Find the card API Access. Turn on Operate API Maker Using API. The address of the API appears. It is one address for every operation. Generate a communication token, at least forty eight characters long. It is the only key of this API, so keep it like a password. Save it.
Calm Home sells shops to partners. When Harbor Home signs up, the sign up system of Calm Home sends one POST to that address, with the token, and CREATE_ADMIN_USER. It sends the user: the owner of the shop, and its API path. It sends its Git repository, made from the template of Calm Home, and its branch. And it sends its secret, written by your code. Here is the answer.
It has the account, without its password. The branch is pulled, and the secret is saved. And it has a deployment hook, with the address your CI calls to deploy it. Keep that address secret.
Sofia, the owner of Harbor Home, signs in for the first time. Git Integration shows her repository, with main pulled a few seconds ago, and the deployment hook that the call made. The custom APIs of the template are there. There is one secret, the one the call sent. It holds the password of her API user, and the connection string of her own database. Every new account gets the sample shop: custom APIs, schemas, and hooks.
With a repository, the pull puts the items of the branch in their place. Without one, send insertDefaultData set to false. Then only its default group, its API user, and its secret are made.
Root sees Harbor Home among the accounts. Now it has a new owner. UPDATE_ADMIN_USER finds the account by its API path, and changes only what you send, here the name and the email. It is the same account, with its new owner. Harbor Home moves its database. UPDATE_SECRET replaces the code of its default secret. Send it whole, with the same keys. Otherwise, what the account encrypted with them cannot be read any more.
And send the new connection string. The answer is true.
Harbor Home leaves. Send DELETE_ADMIN_USER, with its API path. The account is gone, with everything it owns: its APIs, its secrets, its API users, and its logs. If you call it again, it answers false, because nothing is left to remove. There is no undo.
When the API refuses, the answer says why. 403 means it is off, or has no token. 401 means a wrong token, like an old one after you changed it. 400 means an account already has that API path. And 404 means no account has it.
The token is the only key. There is no session, and no sign in. So call the API from your backend, over HTTPS, never from a browser or an app. Keep the token with the other secrets of your backend. When you change it, every program with the old one stops at once. And keep the deployment address of each account secret, because anyone who has it can start a deployment of that account.
Here is the whole pattern. A partner signs up. Your backend makes its repository from your template. One call makes its account, pulls its branch, and saves its secret. Its developers push to that branch. Your CI calls the deployment address, and the new code is live.
To sum up. Turn it on in Deployment Settings, with a token of forty eight characters or more. One call makes an account, with its repository pulled, its secret saved, and a deployment hook. By its API path, you can change it, change its secret, or remove it. Every refusal says why. And the token stays on your backend. Next: Git integration, and the deployment hooks your CI calls. API Maker.
Build faster, spend smarter, deliver better.
Length 6:28Git
Length 6:41Root & admins
Length 5:21Multi-tenant
Length 6:42Deploy