One API in 8 Languages: TypeScript, Python, PHP, C#, Go, Rust, Java, Kotlin

Intro

0:00 One custom API, in eight languages : TypeScript, Python, PHP, C sharp, Go, Rust, Java and Kotlin. Each team writes the language it knows, and every API answers the same way. In this video, the same API, eight times.

Several languages, the usual way

0:17 A team with several languages usually means one framework per language, each with its own server and its own deploy, answers and errors shaped differently by each service, and a compile error found by the build, or by a user. With API Maker, the language is a choice per API, on one server, every language answers the same envelope, and compiled code is compiled the moment it is saved. In this video : the language picker, one API in eight languages, eight calls, one answer, compiled when saved, and a compile error.

The language picker

0:52 Custom API, Add New, the Code tab : TypeScript first, on Node.js, on Bun, or on the default runtime of the sandbox settings. The language picker : Python, and the code becomes the template of Python : what g holds, as comments, and a main which answers hello. Go : the same template, in Go. Close : nothing saved.

One API, eight languages

1:18 Now one API, written eight times. It reads a name from the body, counts the customers of PostgreSQL, and answers both. TypeScript : g.sys.db.count, awaited. Python : the same call. PHP : the same call, with arrows. C sharp : the same call, with capitals. Go answers a value and an error. Rust, a Result : the question mark hands a failure back to API Maker. Java and Kotlin : a map.

1:50 Eight languages, one g : the request, the answer, the calls of API Maker and the logs. The eight APIs in the grid : a path and a language each, and the speed of the day : a few milliseconds a call, and for Java and Kotlin, a first call that also starts their runtime. Hello Rust, Edit, its code, as written above. Close. Test API on Hello Kotlin, the body, the name Calm Home, Send : hello Calm Home, and sixty customers.

2:23 From a terminal, the eight paths, one after the other, with the token of an API user. Eight answers : the same envelope, the same data. Go and Java list the keys in another order : their maps keep no order, and a JSON object needs none.

Compiled when saved

2:40 Five of the eight are compiled : C sharp, Go, Rust, Java and Kotlin. Save, and API Maker compiles the code at once, in the background, in a sandbox of the account, so the first call does not wait for the compiler. What does not compile is written to the console of the account. TypeScript, Python and PHP have nothing to compile. Custom API, Hello Go, Edit, its code. A typo, the way it happens : cuont for count.

3:13 Update : saved. Test API, the body, a name, Send : five hundred, the code does not compile. count is declared and not used, cuont is undefined, each with its line. And Console Logs View : the compiler said so as soon as the code was saved.

Good to know

3:34 An API and all its hooks are one language, on one runtime. Packages are added per language, for every sandbox of that language : video sixteen. Utility classes are written per language too : video twenty. And test cases come in the same eight languages : video thirty seven.

Built on standards

3:54 Every language gets the same g, with its types. Every language answers the same envelope and the same errors. So code written by a person or by an AI assistant, in any of the eight, gives the client the same answer.

Recap

4:08 To sum up. Eight languages, chosen per API. The same g in each. The same answer from all eight. Compiled when saved, and every compile error in the console. Next : hooks, code before and after every API. API Maker. Build faster, spend smarter, deliver better.