API Maker

The backend engine for the AI era

SecurityEpisode 28 5:05 10 chapters November 2026

Secure by Default: Encrypted APIs, Allowed Origins, Two-Step Sign-In

Security that ships with the server: encrypted requests and answers, Encrypt Strings for your env file, allowed origins, two-step sign in, and the known vulnerabilities of every package, with a report. The security features of API Maker, on Calm Home.

In the playlists The complete course Security & access

Chapters

What you will learn

  • APIs that take encrypted requests only
  • An encrypted answer
  • Encrypt Strings, for the env file
  • Allowed origins, and browsers of other sites
  • Two-step sign in
  • Vulnerabilities of every package, with a report
In the docsSecurity features
Transcript687 words · click a time to play from there

Intro

Some security comes with the server itself. Encrypted requests and answers, encrypted strings, allowed origins, two step sign in, and the known weak points of every package. In this video, we look at the security features of API Maker, on Calm Home.

Security, the usual way

Security is usually a long list of work. There is a ticket for each item: encryption, CORS, two step sign in, and audits. Each one is built by hand, in a different way in every service. And some never get done. With API Maker, they are settings and headers, ready on every server. They are the same for every API of every table. And a report says what is left to fix.

In this video: encrypted requests and answers, Encrypt Strings, allowed origins, two step sign in, and weak points in packages, with their report.

Encrypted requests and answers

Payments come from the browser of the shop. The Collection Settings of sales.payments say acceptOnlyEncryptedData. So the app encrypts each body with the transfer key of the default secret, and the time it was made. The key is shared with the app, but never written in its code. First, a payment sent as plain text. It is refused: this API takes only encrypted payloads. Now the app encrypts the payment.

It is sent with x-am-encrypted-payload, and it is saved: two hundred and one. Now the same payment, encrypted ten minutes ago. The answer is: payload expired. So a request caught on the way cannot be sent again later. An answer can be encrypted too. With x-am-get-encrypted-data, data is null, and encryptedData holds the answer. The app reads it with the same key: order three, delivered.

Encrypt Strings

Open Security, then Encrypt Strings. Type a connection string. This one is fake. Click Encrypt. You get the text to put in the env file instead, so a terminal or a shared screen shows no password. Copy it. Note that this hides the string, but it does not protect it. Every copy of API Maker can read it back.

Allowed origins

Open Operations, then Sandbox Settings, and the Allowed Origins card. Click Add New, and type the web shop, https://shop.calmhome.example. Save it. The settings of the sandboxes are saved with it. A browser call from another site gets four hundred and three. It is blocked before anything runs. From the shop, it gets two hundred. From a server, with no Origin header, it gets two hundred too. It is a rule for browsers.

Two-step sign in

Now two step sign in. Open the menu of the account, then My Security. The root user sets the policy, and it is shown here as read only: email codes, an authenticator app, and recovery codes. To set it up, scan the square with an authenticator app, and type its code. The account is then linked, and its recovery codes are shown once. Here we close it, so nothing is linked.

Vulnerabilities

Open Security, then Vulnerabilities. There are two audits. The first checks the packages of the sandboxes, in eight languages. The second checks the hundreds of crates that API Maker itself is built from. Each advisory has its score, and what can be done. Download the audit. You get a report, ready to print or to save as a PDF, with what to do first.

Good to know

Good to know. Signing in to the panel asks for a captcha. Too many wrong passwords stop the sign in for a few minutes. The panel talks to the server through an encrypted channel, and its pages carry security headers. Encrypted and hashed fields protect stored data. Video four shows them. And while this video was made, the audit found four advisories in rustls. API Maker moved to the version that fixes them.

Built on standards

Security is a set of settings, not a list of tickets. The same rules hold for every API of every table. So code written by an AI assistant cannot skip them, because they run before it does.

Recap

To sum up. Encrypted requests, and encrypted answers. Strings encrypted for the env file. Allowed origins. Two step sign in. And weak points in packages, with a report. Next: automatic caching. API Maker. Build faster, spend smarter, deliver better.