API Maker
The backend engine for the AI era
i18nEpisode 34 4:34 9 chapters November 2026
Every error of your APIs in the language of the person who called them, without one line of translation in your code. Build a French dictionary, see what a dictionary holds, translate the errors of your own custom APIs, and pick the language with one request header.
In the playlists The complete course Migrations & tenants
Your APIs can give every error in the language of the person who called them. You write no translation code. In this video, we look at the dictionaries of API Maker.
Translated errors usually mean extra work. You check the language before every message. The messages of the framework stay in English, because nobody can reach them. And every new sentence needs a release. With API Maker, there is one dictionary for each language. It covers every message, yours and the ones of API Maker. One header of the request picks it, and you can change it without a deploy. In this video: i18N Management and a French dictionary, what a dictionary holds, one save, in three languages, and the errors of your own custom APIs.
Open APIs and Logic, then i18N Management. There is no dictionary yet. Add New starts from a sample, with every message that API Maker can send, and the errors of the custom APIs of the account. Here, the two errors of Apply Coupon. Name it fr. A request picks it with the header x-am-internationalization, set to fr. Here is the dictionary: two field names, the two errors of Apply Coupon, and two messages of API Maker, in French.
Save it. A dictionary has four parts. Messages of API Maker have an id and a template with placeholders, like the maximum length of a field. The dictionary gives that template in French. COMMON translates the words that fill the placeholders. For example, status becomes statut. And CUSTOM_API_ERRORS translates your own errors, text for text. The fixed texts of API Maker have their own part, CONSTANT_ERRORS.
In API Testing, pick postgres, then crm, then customers, and Save single or multiple. In the body, we put a customer with no city, and a status of fourteen letters, where twelve are allowed. Open the Header tab, and leave out the language header. Send. We get two errors, in English, and nothing is saved. Now add the header, with fr. We get the same errors in French, with the French names of the fields.
And with hi, we get Hindi. The field key stays city_id, so apps keep reading it.
Apply Coupon lists its errors in errorList, and its code throws them in plain English. There is no language in the code. From an app, we send the coupon SPRING15. It has expired. With fr, we get: ce coupon a expiré. With hi, we get the same, in Hindi. For an unknown coupon, we get: coupon introuvable. And for a language with no dictionary, like de, we get English, with no error.
Good to know. Once a dictionary exists, API Testing sends the first one by default. Untick the row to get English. A dictionary is TypeScript that runs when you save it. A mistake is refused, with its line. Dictionaries travel in Git with the project. Only the message changes. The type, the field, and the code of an error stay the same.
Code throws plain English, listed in errorList. Translations live in one file for each language, for every kind of API. So an AI assistant writes no language checks. The same rule works for every endpoint it adds.
To sum up. There is one dictionary for each language. It covers every message, yours and the ones of API Maker. One header picks it. And there is no language in your code. Next: database name masking. API Maker. Build faster, spend smarter, deliver better.
Length 3:56Masking
Length 10:05Six engines
Length 6:52Every night
Length 7:17Migrations