User Guide

This guide covers what you need to run Flipper API Caller on your Flipper Zero, how to set up the Wi-Fi board, and how to use the app today.

Requirements

• A Flipper Zero with recent official/custom firmware
• A Wi-Fi board that speaks the FlipperHTTP protocol:
  • ESP32 (official Wi-Fi Devboard or a bare WROOM/S2 devkit) running FlipperHTTP v2.2.0
• The latest .fap from the Releases page, copied to apps/Tools on the Flipper (e.g. with qFlipper)

Board wiring (bare devkits)

The official Wi-Fi Devboard plugs directly into the GPIO header. For a bare ESP32 devkit, wire it like this:

ESP32 pin	Flipper pin
TX	14 (RX)
RX	13 (TX)
3v3	9
GND	11

Power: the Devboard runs from the Flipper 3v3 rail; a bare devkit is best powered from its own USB port.

FlipperHTTP firmware

• Repository: https://github.com/jblanked/FlipperHTTP (build the release v2.2.0, the version this app is tested against)
• Web flasher: https://flipperhttp.jblanked.com/ (targets the official Wi-Fi Devboard)

Make sure the build you flash matches your chip (ESP32-S2 Devboard build vs ESP32 WROOM build).

Using the app

1. Connect to Wi-Fi

1. Open the app → Connessione.
2. Ricerca reti: wait for the scan, pick a network from the live list.
3. Type the password → the result screen shows the outcome.
4. Reti salvate lists known networks for quick reconnection; Disconnetti disconnects the board.

2. Save an API call

1. Main menu → Aggiungi chiamata.
2. Fill the fields:
   • URL: the request target (see limitations below)
   • Tipo: HTTP / HTTPS (used to prepend the scheme automatically)
   • Metodo: GET, POST, PUT, DELETE, PATCH or HEAD
   • Query, Headers (JSON), Body (JSON): optional
3. Salva → the call appears in the list.

3. Run a call

1. Main menu → Lista chiamate.
2. Pick the call → Esegui.
3. The result screen shows method, URL, status code and the response body.
   • UP / DOWN: scroll one line
   • OK: next page
   • BACK: back to the menu

Modifica opens the same form pre-filled, where you can also delete the call.

4. Logs

Every run is appended to debug.log in the app data folder on the SD card (apps_data/api_caller/debug.log), with SEND / RESULT / ERROR entries. The log self-truncates at 32 KB.

Text input keyboard

All text fields (URL, query, headers, body, Wi-Fi password) use the app's extended keyboard. The typed text is shown on two lines above the keys: when it grows longer, the view scrolls to keep the end visible with ... on the left of the first line.

• OK (short press): type the selected character.
• OK (long press): type the shifted character (see the table below).
• BACK (long press) or the backspace key: delete the character before the cursor.
• Save key (check icon): confirm and leave the field.
• Edit mode: from the top key row, press UP to move into the text:
  • LEFT / RIGHT: move the cursor inside the text (the text scrolls only when the cursor reaches the edge);
  • OK: back to the keys; typed characters are inserted at the cursor.

The four key rows are: symbols ({ ( [ | @ & # ; ^ * \ " ~ ' . /), letters plus digits, more letters with the backspace key, and the last letters with the save key and ! +`.

Long-press (shift) characters

Key	Long-press OK
a–z	A–Z (uppercase)
_	(space)
(	)
{	}
[	]
/	\
;	:
.	,
!	?

Any other key is unchanged by long-press.

Current limitations

• URLs without a scheme get http:// / https:// prepended automatically (from the protocol setting).
• Headers and Body must be valid JSON; {} is sent when the field is empty.
• Body input is single-line.
• Responses are shown up to 32 KB (a notice appears if truncated).
• One request at a time; requests time out after 30 s.
• HEAD is executed as GET (the board protocol has no HEAD).