API Testing in the Panel: Call, Debug, Export and Share Any API

Intro

0:00 One page to call any API of your account, change its code and run it, read its logs, and take the request away as code. In this video, the API Testing page, tab by tab.

Testing APIs, the usual way

0:13 Testing a backend usually means a Postman collection which drifts from the server, tokens copied by hand, and a round trip through the editor, the deploy and the logs for every try. With API Maker, every API of the account is listed as the server describes it, the page signs the requests for you, and the code you test is the code on your screen. In this video : the categories and the APIs of a table, query params and the model of an answer, rows from the schema, and an answer as a table you can edit, a custom API with the keyboard, its hooks and its logs, the request as code, and the history of your requests.

Categories and APIs

0:54 APIs and Logic, API Testing. Its categories : the APIs of your tables, custom APIs, system APIs, and code which is not an API, like events, schedulers, migration scripts or hooks, run on demand. Instance APIs : postgres, crm, customers. Every API of the table, schema or generated, and Get all.

Query params, and a model

1:21 Query Params lists what this API takes. limit two, and three fields. Send : two customers, the time, the status. Copy Interface takes the first customer of the answer, names its model Customer, and writes it : in TypeScript, or in Kotlin, ready for an app. And many more languages.

Rows and tables

1:44 MariaDB, the coupons, Save single or multiple. Generate Data writes the body for you, from the schema of the table : an array of two coupons, every column with a value of its type. Change what matters, and send it. One object, an array, or as many rows as you ask for. Get all, Send : the ten coupons. Switch to Table view : the same answer, as a grid.

2:12 A quick filter : WELCOME5. A double click on max_uses, twelve thousand, and Save counts one change. Save : the grid calls Update by id of the table, and MariaDB has the new value. Every row again. Export : CSV, Excel or PDF, of the rows as they are filtered and sorted. Two rows chosen, with Command click : Delete asks first, then calls Remove by id for each row.

2:42 Here, nothing is removed. A table of MongoDB, or one whose schema names its primary key, can be edited this way.

A custom API with the keyboard

2:52 Custom APIs, Cart Quote. The Header tab signs the call with the API user Default : a test token, made by the server for this page only. The body : a cart of a hundred and fifty dollars, with a coupon. Command E sends it. Pre Hooks : the hook which runs before the code, Normalize cart. Logs : what the hook and the code wrote for this call, in order.

3:18 The Code tab holds the code of the API. A new log line, not saved. Command E runs the code on screen : the new line is in the logs already. Command S saves it : the next call from anywhere runs it.

The request as code

3:34 The same cart, sent. Integrations writes this request as code, in dozens of languages and variants. cURL : the request on screen, copied, with __token__ in place of the token. The same request, in Python, with requests. Pasted in a terminal, with a real token in place of __token__ : the same answer, two hundred, a total of a hundred and forty two fifty.

Every request, kept

4:01 Every Send is kept. The cart with the coupon, then the same cart, without it, sent again. Request States : both calls, with their headers, their body, the answer and the code. Save the request on screen, under a name, for you alone, or for every user, through git.

Good to know

4:22 The Test API button of every page opens API Testing on that item. x-am-meta, true, adds what ran the call and how long it took. The Index Maker tab lists the queries a custom API made. Test Hooks runs one hook alone : video thirty eight follows a whole bug with them.

Built on standards

4:43 The request comes from the definition of the API, not from a collection kept by hand. The code tested is the code on screen, saved with one key. So the requests an AI assistant writes can be checked here first, with the same tokens and the same logs.

Recap

5:00 To sum up. Every API and every kind of code, in one page. Query params, and the model of an answer. Rows from the schema, and the answer as a table : edited, saved, exported. Command E runs the code on screen, Command S saves it. Logs and hooks of the call. The request as code, and its history. Next : test cases, with mocks and coverage. API Maker. Build faster, spend smarter, deliver better.