Skip to content
Home
Docs/API Tester

API Tester

A full-screen API client inside PocketCode: REST requests with scripts and no-code assertions, GraphQL, WebSocket, Server-Sent Events, Socket.IO and MQTT. Collections, environments with secret variables, a history you can compare, a collection runner, a load test, a mock server and code generation round it out. Each screen below says what it does and, where something is missing, what and why.

What it is and how to open it

API Tester opens as a full-screen layer over the app and keeps the open request, the screen you were on and your live connections while you rotate the device. It speaks six protocols: REST, WebSocket, GraphQL, SSE, Socket.IO and MQTT. A gRPC panel is in the code, but this version hides it until it works on Android.

Open it

  1. 1Tap Tools in the navigation bar. The Dev tools sheet opens: tap API Test (the tile reads “API Test” in every app language).
  2. 2Or open the command palette and run API Tester.
  3. 3Or, from Home, use the API Tester quick action, or tap the API tester widget, which shows your saved collections and the requests you last ran.
  • The system back gesture goes from a request back to Start; from Start it closes API Tester.
  • API Tester has no deep link of its own. Keyboard shortcuts exist only in the landscape tablet layout (see Open requests, saving and shortcuts).

Who else uses it

  • The AI assistant has three tools for this module: send a request, list your collections and parse a cURL command. They answer without the screen being open, using the same REST engine. The response body it receives is cut at 4096 characters, it can't attach files, it won't call PocketCode's own backend, and parsing a cURL command only reads it: nothing is loaded into the editor.
  • Workflows can start from a response sent on this screen. The event carries the URL, the method, the status code and the time, never the body or the headers. Requests the AI sends don't trigger it.
  • Cloud Sync (Pro) doesn't sync your collections and environments for now: that part is paused. See Privacy and security.

Screen map

One row per screen and sheet. On a phone, Start, Collections and History are reached from the ⋮ menu of the request; on a tablet the top bar has Home, the request's name, the environment menu and Open library (which opens Collections).

ScreenHow you get thereWhat you can do
StartIt opens first; back from a request; Home on a tabletPick New request, Collections or History, and return to anything still connected.
RequestNew request, a chip on Start, or loading an entry from Collections or HistoryBuild and send a request. Four layouts, depending on the window.
Protocol panelsThe protocol menu on the request's context lineWebSocket, GraphQL, SSE, Socket.IO and MQTT each have their own panel, the same in all four layouts.
ToolsThe sliders icon on the context line (only on the request screen)Open Environments, Mock Server, Cookies, Import and Settings.
EnvironmentsTools → Environments, or the environment menu → Manage environmentsPick the active environment; edit variables, secrets and globals.
Mock ServerTools → Mock ServerSwitch the local server on (Pro), set port and latency, add routes, read its log.
Cookie JarTools → CookiesSee the cookies servers have stored; remove them from the list.
Import RequestTools → ImportPaste cURL, Postman, Insomnia, OpenAPI or HAR text; generate a mock from OpenAPI.
Import from projectImport → Import from projectPreview and import collections saved as files in the open project.
Request SettingsTools → SettingsTimeout, redirects, SSL, cookies and URL encoding for the open request.
Code Generator⋮ → Code GenSee the request as code in 26 different outputs and copy it.
Generated cURL⋮ → cURL ExportCopy the request as a cURL command.
Save to collection⋮ → Save, or Ctrl+S on a landscape tabletPick a collection or type a new name.
CollectionsStart → Collections; ⋮ → Collections on a phone; the folder icon on a tabletSearch, create, load a request, run, export, save to the project, delete.
ExportCollections → ⋮ on a collection → ExportPreview and copy a collection in five formats.
HistoryStart → History; ⋮ → History on a phoneSearch, filter, load, star, compare, use as a mock, clear.
Compare responsesHistory → ⋮ on an entry → Compare with…, then another entryRead a Body and Headers diff of two responses.
RunnerCollections → ⋮ → RunRun every request of a collection, with iterations or a data file (Pro).
Load Test⋮ → Load TestSend the open REST request many times and read latency percentiles (Pro).

Start

Start is where the module opens. It has no URL field, protocol picker or Tools button: those belong to the request screen. On a window wider than tall it shows two columns.

API Tester start screen on a tablet: the title on the left, and the New request, Collections and History cards on the right
Start on a tablet: the title on the left, New request, Collections and History on the right
API Tester start screen on a phone: a New request card listing the seven protocols, with Collections and History cards under it
Start on a phone: New request with the protocols under it, then the Collections and History counters

What Start offers

You can

  • Tap New request. The card lists the six protocols (REST · WS · GQL · SSE · IO · MQTT) and opens the request screen.
  • Tap Collections or History. Each card shows how many you have, or Empty.
  • Use the strip of live chips at the top, shown only when something is running: each open request, the mock server with its port, connected WebSocket, SSE, Socket.IO and MQTT sessions, a load test or a collection run. Tapping one takes you back to it.

You can't, and why

  • Pick a protocol, type a URL, choose an environment or open Tools from Start: none of them is there.By design
  • Close live connections by going back to Start: they keep running, which is why the chips exist.By design

The request (REST)

This is where REST requests are built and sent. A request has six sections: Params, Headers, Body, Auth, Scripts and Settings. The other protocols use the same URL bar and context line with a panel of their own (see Other protocols).

Four layouts

The layout follows the window, not the device, so a split-screen tablet gets the phone one.

Phone, portrait (under 600 dp wide)A Request | Response switch under the URL bar and the six sections as tabs. Sending flips to Response on its own.
Phone, landscape (600 dp or wider, under 480 dp tall)Section tabs and a draggable split between request and response. With the keyboard up, the response shrinks to a 48 dp strip.
Tablet, portraitRequest on top and response below, with a draggable divider and 30 / 50 / 70 % presets. Sections as an accordion; Collections as a side drawer (folder icon).
Tablet, landscape (840 dp or wider, 480 dp or taller, and wider than tall)Three columns with draggable dividers: the Collections sidebar, the request with tabs for open requests, and the response. Double-tap a divider to reset it.

URL bar, context line and ⋮ menu

Type the URL (monospaced, no auto-capitalisation). Without http:// or https://, the app adds https://. Under it, the context line holds the protocol menu, the environment menu, the Tools icon and the ⋮ menu.

You can

  • Pick the method among eight: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS and TRACE, each in its own colour. The picker shows for REST and GraphQL.
  • Tap Send (the paper plane). While the request runs it becomes Cancel request.
  • Pick the protocol: REST, WebSocket, GraphQL, SSE, Socket.IO or MQTT.
  • Pick the active environment, or No environment; Manage environments opens the editor.
  • Open the ⋮ menu: New, Duplicate (adds “ (copy)” to the name), Save, cURL Export, Code Gen and Load Test. On a phone it also lists Home, Collections and History.

You can't, and why

  • Choose the method of a GraphQL request: the picker is there, but the panel always sends POST.Not yet
  • Name a request: there is no field for it, so requests you save are called New Request (imported ones keep their own names).Not yet

The Tools sheet

Five rows, each with a line about what it holds and, on the right, its live state: the active environment, the mock server (for example :8090 · 3 served) and the number of stored cookies. The sheet opens only from the request screen, never from Start.

RowWhat it opens
EnvironmentsBase URLs, tokens and variables
Mock ServerServe canned responses on a local port
CookiesWhat servers have stored on this device
ImportcURL, Postman, OpenAPI, HAR
SettingsTimeout, redirects, SSL
Tools sheet with the Environments, Mock Server, Cookies, Import and Settings rows
Tools: one row per sheet, each with a line saying what it holds

Params and Headers

Both are key–value lists with the same editor. The tabs carry a counter of enabled rows (for example Headers 25). A new request starts with a Content-Type: application/json header.

You can

  • Add rows with Add param or Add header, switch each one on or off with its checkbox, drag to reorder and swipe to delete.
  • Open a row's details to add a description or turn on Secret value: the value is masked in the interface and left out of exported cURL and generated code.
  • Use Bulk edit to paste lines in Key: value form.

You can't, and why

  • Pick common headers from a list: there is no header autocomplete.Not yet
  • Have query parameters percent-encoded for you: they are added to the URL as typed, and the Encode URL switch has no effect.Not yet

Body

You can

  • Pick the type. None, JSON, Form URL-Encoded, Multipart Form and Raw Text are chips; XML, HTML, JavaScript, Binary and GraphQL are under More…. Ten in all, named in English in every language.
  • In JSON: line numbers, live validation (Invalid JSON: …) and Beautify / Minify.
  • In Form URL-Encoded and Multipart Form: key–value rows. Multipart rows can be a text field or a file field (Choose file, through the system file picker).
  • In Binary: Select binary file. In GraphQL as a body type: a Query and Variables (JSON).
  • Use {{variables}} in raw, JSON, XML, HTML and JavaScript bodies and in form fields: they are replaced when you send.

You can't, and why

  • Get syntax highlighting in the body editor.By design
  • Set an operation name for a GraphQL body, or use {{variables}} inside its query and variables.Not yet

Auth

Pick the type in the Authentication type menu; only that type's form appears.

No AuthNothing is added.
Bearer TokenA token and a prefix (default Bearer).
Basic AuthA username and a password.
API KeyA key name, a value and where it goes: header or query parameter.
OAuth 2.0Four grant types, described below.
Digest AuthA username and a password. The realm, nonce and the rest come from the server's 401 challenge.
AWS SignatureAccess key ID, Secret access key, Region (default us-east-1), Service and an optional Session token. Requests are signed with real SigV4.
CustomA header name and a value.
Hawk Auth, NTLM AuthListed with a Soon badge. They do nothing yet.
Authentication type menu listing No Auth, Bearer Token, Basic Auth, API Key, OAuth 2.0, Digest Auth, AWS Signature, Hawk Auth and NTLM Auth, the last two marked Soon
Authentication type: the list of types, with Hawk and NTLM marked Soon

You can

  • Choose a Grant type: Authorization Code, Client Credentials, Password Credentials or Implicit.
  • With Client Credentials, fill in Token URL, Client ID, Client Secret and Scope, then tap Get token.
  • With Authorization Code, tap Open browser, sign in, copy the code value from the address you are sent back to, paste it under Authorization code and tap Exchange code.
  • With Password Credentials or Implicit, paste the token into Access token yourself: there is no button.
  • Use {{variables}} in credentials. To keep a token out of sight, store it as a secret environment variable and write {{token}} here.

You can't, and why

  • Have the OAuth redirect captured for you: the module can't register a link back into the app, so you paste the code.By design
  • Use PKCE or a refresh token.Not yet
  • Send an OAuth 2.0 token anywhere but in an Authorization: Bearer … header.Not yet
  • Use Hawk or NTLM: choosing them does nothing when you send.Not yet
  • Mask what you type in Auth: tokens and passwords are shown as plain text on this screen.Not yet

Scripts and assertions

The Scripts section has three parts: Assertions (no code), a Pre-request Script and a Test Script.

You can

  • Add an assertion with Add assertion: a field (Status code, Response time, Header, Body (JSONPath) or Body size), an operator (equals, does not equal, contains, does not contain, is greater than, is less than, exists, does not exist) and an expected value. Assertions always run, with no JavaScript engine.
  • Insert one of nine Quick templates: Status is 200, Status is 2xx, Response time < 500ms, Has JSON body, Body not empty, Has Content-Type, JSON schema valid, Body contains string, Array length > 0.
  • Write JavaScript for the pre-request and test scripts. They run in an isolated engine (androidx.javascriptengine), a fresh one each time, so a script that crashes can't take the app down.
  • Use the pm subset: pm.test(name, fn); pm.expect(value) with equal, include, above, below, within, an(type), empty and their not forms; pm.environment.get and pm.environment.set; pm.globals.get (read-only); pm.request (method, url, headers, body: a read-only copy); in tests, pm.response (code, status, headers, responseTime, text(), json() and to.have.status / header / jsonBody); and console.log / info / warn / error.
  • Count on pm.environment.set being saved: it updates an existing global first, then a variable of the active environment, and otherwise creates one in the active environment (or a global if none is active).
  • Read results in the response's Tests tab and the script's output in Console.

You can't, and why

  • Use the rest of Postman's API: pm.sendRequest, pm.variables, pm.collectionVariables, setNextRequest, require and pm.globals.set don't exist, scripts can't change the request and there is no async. A Postman script that needs them ends with Script error: … in the console.By design
  • Run scripts on a device without a modern WebView: the script is skipped with a warning in the console, and only the assertions run.Device
  • Have a collection's or folder's scripts run: they are imported and saved, but only the request's own scripts execute.Not yet
  • Validate a body against a JSON schema: the JSON schema valid template only checks that the body is JSON.Not yet

Settings

Three settings sit inline in the Settings section; the Request Settings sheet (Tools → Settings, “Applies to the open request only”) has five. They travel with the request.

You can

  • Set Timeout (ms) inline (any number, default 30000), or pick 5, 10, 15, 30, 60 or 120 s in the sheet. One value covers connecting, reading and writing.
  • Switch Follow redirects and Verify SSL.
  • Switch Enable Cookies and Encode URL: only in the sheet.

You can't, and why

  • Set a proxy, a client certificate or a maximum number of redirects: no screen offers them.Not yet
  • Make Encode URL do anything: the switch is there, but sending ignores it.Not yet
With Verify SSL off, any certificate and any host name is accepted.

Open requests, saving and shortcuts

On the landscape tablet layout the request column has tabs for several open requests, and these shortcuts:

ShortcutAction
Ctrl+EnterSend (or connect / disconnect in a streaming protocol)
Ctrl+TNew tab
Ctrl+WClose the tab
Ctrl+SSave to a collection

You can

  • Open a New tab, switch tabs and close them with ✕. A dot marks a request changed since it was saved; an empty one reads Untitled.
  • Tap ⋮ → Save to see Save to collection: pick a collection (it shows its request count) or type a new name and Create.
  • Use Duplicate and New from the ⋮ menu, and cURL Export to read Generated cURL and Copy it.

You can't, and why

  • Open requests in tabs on a phone or a portrait tablet: tabs exist only in the landscape tablet layout, and so do the shortcuts. There is no Ctrl+F or Ctrl+K either.By design
  • Keep the response when you switch tabs: it is cleared.Not yet

The response

The panel has four states: empty (Send a request to see the response), loading (Sending request…), success and error. On a phone in portrait the summary rides on the switch itself, for example Response · 200 · 679 ms.

A 200 REST response on a phone with the Request and Response switch, the Body, Headers, Cookies and Tests tabs, the two JSON filters and the JSON tree
A REST response on a phone: the Request | Response switch, tabs and the JSON tree with its two filters

Status and tabs

You can

  • Read the status chip, coloured by range (2xx green, 3xx turquoise, 4xx orange, 5xx red), with the total time, the size and the content type.
  • Switch between six tabs, in this order: Body, Headers (with a count; copy any header), Cookies (name=value, domain and path, with Secure and HttpOnly badges), Tests (assertion and script results; No tests ran for this response when empty), Timeline and Console.
  • Read Timeline: DNS, TCP, TLS, TTFB and Transfer, plus Total.
  • Read Console: a log of the whole session (sends, scripts, the mock server, connections) with the time and a level, LOG, INFO, WARN or ERROR.

You can't, and why

  • See the protocol, the remote IP or the redirect chain: the panel doesn't show them.Not yet
  • See why a request failed: on a network, TLS or timeout error the panel shows only a 0 Error chip and an empty body. The reason goes to the Console log.Not yet
  • Clear the console: it has no clear button.Not yet

Body

You can

  • Switch the view with the floating button at the bottom right: Pretty, Raw or Preview. Copy sits next to it.
  • With Pretty, browse a collapsible JSON tree with two filters, Search keys… and JSONPath filter · $.a.b[0].c (an exact path; No match for that path if nothing is found).
  • Open a node's ⋮ menu: Copy value, Copy path and Save as variable (pick an environment and a name).
  • With Raw, read monospaced text; bodies over 512 K characters use a virtualised list.
  • With Preview, see text/html rendered in a WebView with JavaScript turned off; any other type says No preview available for this content type.

You can't, and why

  • Get XML or HTML pretty-printed: only JSON is formatted, anything else is shown as received.Not yet
  • Preview an image: the preview never receives the image bytes.Not yet
  • Search the body with highlighted matches, jump to the top or bottom, or share or save the response to a file.Not yet

Compare two responses

Comparing starts from History, not from this panel: ⋮ on an entry → Compare with…, then another entry. See History for the steps.

Other protocols

Pick the protocol on the request screen's context line. Each panel below sits in the request area; the address and Send (which connects, in the streaming ones) stay in the URL bar. {{variables}} are not replaced in any of them except in a GraphQL endpoint URL. Plain http:// and ws:// only reach localhost, 127.0.0.1 and 10.0.2.2; everything else needs HTTPS or wss://.

GraphQL

You can

  • Enter the endpoint and tap Fetch Schema (a standard introspection POST). Schema shows how many types it found; each type expands to its fields with their types and an argument count such as 2 arg(s). Types starting with __ are hidden.
  • Write the Query and, in the collapsible section, the Variables (JSON); send; read the answer in the usual response panel. Queries and mutations both go out as an HTTP POST.

You can't, and why

  • Set an operation name, headers or auth from this panel: it sends only Content-Type: application/json. For auth, use a REST request with a GraphQL body.Not yet
  • Use subscriptions: the explorer lists a Subscription type, but everything is sent over HTTP POST, with no graphql-ws transport.Not yet
  • See argument names: only their count.Not yet

WebSocket

Enter ws:// or wss:// (without a scheme, wss:// is added) and connect. There is no read timeout: the connection stays open until you disconnect or the server closes it.

You can

  • Follow the state: CONNECTING, CONNECTED, DISCONNECTING, DISCONNECTED or ERROR.
  • Type a Message and send it once connected.
  • Read the chat-style log (sent on the right, received on the left, with the time) and empty it with Clear messages.

You can't, and why

  • Add headers or subprotocols, reconnect automatically or save message templates.Not yet
  • Send or read binary messages: only text.Not yet
  • Use {{variables}} in the URL.Not yet

SSE

Enter the stream's URL and connect. The app sends a GET with Accept: text/event-stream and no read timeout.

You can

  • Follow the state (CONNECTING, CONNECTED, DISCONNECTED or ERROR) and the counter, for example 12 events.
  • Read the event log: a type badge, id: … and the first 300 characters of data.

You can't, and why

  • Send headers, filter by event type, reconnect automatically or honour the server's retry: value.Not yet
  • See each event's time or retry, or resume from a Last-Event-ID: the id is kept but neither shown nor sent.Not yet
  • Use {{variables}}, the cookie jar or Verify SSL: none applies here.Not yet

Socket.IO

You can

  • Enter the URL (for example http://localhost:3000) and a Namespace (default /, which adds nothing; any other name is appended to the URL).
  • Switch Auto-reconnect (on by default).
  • Use Add listener to listen for an event name, and Emit to send an event with a JSON payload: it goes as a real JSON value (object, array or scalar), or as text if it doesn't parse.
  • Read the chat-style log, where each bubble carries its event name, and clear it.

You can't, and why

  • Set headers, auth, a query or the transport, remove a listener, or use more than one namespace per connection.Not yet
  • Know which Socket.IO server versions it talks to: the client is the official socket.io-client 2.1.2, and that library decides.Third party

MQTT

Enter host or host:port in the URL bar. With no port the app uses 1883, or 8883 if Use TLS was on when you typed the address.

You can

  • Switch Use TLS (the system's certificates), and set Client ID (generated as pocketcode- plus eight characters), Username and Password (sent only if the username isn't empty; the field is masked, with a show/hide eye).
  • Subscribe to a Topic with QoS 0 (At most once), 1 (At least once) or 2 (Exactly once); the Subscriptions list shows them.
  • Publish to a Publish topic with a text Payload and a QoS.
  • Read the messages, sent and received, grouped by topic.

You can't, and why

  • Choose the MQTT version: the client speaks MQTT 5 only, so a broker that supports only 3.1.1 may refuse the connection.Not yet
  • Publish with the retain flag.Not yet
  • Unsubscribe, set a will, keep-alive or clean-session, MQTT 5 properties, your own TLS certificates, or connect over WebSocket.Not yet

gRPC (hidden in this version)

The code has a gRPC panel, but this version hides it: gRPC is not on the New request card or in the protocol menu. The panel needs the full protobuf-java library, which the app leaves out so Firestore keeps working, so it can't work on Android yet. It comes back once it does.

Collections

A collection groups saved requests. Collections are a screen of their own, not a tab of a shared library: on a phone they open from Start or the ⋮ menu with no title bar (go back with the system gesture); on a tablet they are a side drawer in portrait and a fixed sidebar in landscape.

Collections screen with a search field, two collections and a button to create a new one
Collections: search, one row per collection, the ⋮ menu and the button to create one

You can

  • Search collections by name.
  • Create one with New collection (the round button). On Free, with one collection already, it opens the API Tester Pro window instead.
  • Expand a collection to list its requests (the method in colour, then the name or URL) and tap one to load it: you return to the request screen.
  • Open a collection's ⋮ menu: Run (with a Pro badge), Export, Save to project and Delete. Delete asks for no confirmation.
  • Save the open request into a collection with Save to collection.
  • Type a new name in Save to collection to create a collection on the spot. On Free that obeys the same cap of one: with one already, the dialog closes and the API Tester Pro window opens.

You can't, and why

  • Rename, move or reorder collections or requests, or create folders: there is no screen for it.Not yet
  • Open a folder: folders (they arrive with imports and project files) are drawn as a name (n) row that doesn't respond. You can't expand them or open their requests here, although the runner does walk them.Not yet
  • Have a collection's or folder's auth, headers or scripts applied: they are imported, saved and exported, but sending and running use only what is on the request itself.Not yet
  • Edit a collection's variables: they only arrive through imports and project files, and are used when a request was loaded from that collection.Not yet
  • Keep more than one collection on Free: New collection, a new name in Save to collection and an import all open the API Tester Pro window.Pro

Environments and variables

An environment is a named set of variables, and one can be active at a time. Reference a variable as {{name}}.

Environments sheet with the None and Default chips, the Default environment card with Add variable, and Global Variables
Environments: the chips pick the active one, the cards edit its variables

The Environments sheet

You can

  • Open it from Tools → Environments, or from the environment menu → Manage environments. The sheet blocks screenshots.
  • Pick the active environment with the chips (None or one of yours); the cards below edit.
  • Tap New environment (a dialog asks for a name), delete an environment (no confirmation) and see which one is Active.
  • Edit variables in two columns, KEY and Value, and add more with Add variable.
  • Lock a variable as secret: its value is masked with dots, an eye reveals it, and it masks again when you leave.
  • Open Global Variables (collapsible) and use Add global variable: they are visible whichever environment is active.
  • Create a variable from a response: in the JSON tree, a node's ⋮ → Save as variable.

You can't, and why

  • Choose a scope per variable, edit an initial value or pick an environment colour: only environment and global variables exist in the editor.Not yet
  • Import or export a single environment: Postman environments can't be imported, and Insomnia's import flattens the variables of every environment in the file into one list of collection variables.Not yet
  • Have a second environment on Free: creating one opens the API Tester Pro window.Pro

Where variables are replaced

Replaced inThe URL, the names and values of query params, headers, raw / JSON / XML / HTML / JavaScript bodies, form-urlencoded fields, the text fields of multipart bodies and auth credentials (bearer token, Basic, API Key, OAuth 2.0 access token, Custom, Digest, AWS).
Not replaced inA GraphQL body (query and variables), the streaming protocols (WebSocket, SSE, Socket.IO, MQTT), cookies and the bearer prefix.
PrecedenceDynamic variables first, then a row of the runner's data file, then the collection's variables, then the active environment, then globals: the most specific wins.

Dynamic variables

{{$guid}} (also {{$randomUUID}}), {{$timestamp}} (seconds), {{$isoTimestamp}}, {{$randomInt}} (0 to 1000, or {{$randomInt(min,max)}}), {{$randomEmail}} (always at example.com), {{$randomFirstName}} and {{$randomLastName}}. Each is generated afresh every time; an unknown name is left as written.

A secret is masked in the interface and left as {{name}} in exported cURL and generated code (a secret row shows ••••••••). When you send the request, though, the real value goes over the network: it has to, or the auth couldn't work.

History

History keeps the requests you sent, with their responses. It is a screen of its own, with no title bar.

History screen with a search field, the Starred, GET, POST, PUT and DELETE filters, six requests grouped under Today and Clear all history
History: filters, grouped by day, a star and a ⋮ menu per entry, Clear all history

You can

  • Search history by URL or name, and filter with Starred and by method (only GET, POST, PUT and DELETE are offered).
  • Read entries grouped under Today, Yesterday, This week (the last seven days) and Older, each with its method, status code, time and hour.
  • Tap an entry to load the request and its saved response; mark it with the star.
  • Open an entry's ⋮ menu: Compare with… and Use as mock (both greyed out if the entry has no response).
  • Tap Clear all history. It asks for no confirmation.

You can't, and why

  • Keep more than 200 entries: the oldest are deleted beyond that, on Free and on Pro.By design
  • Save history past 10 entries on Free: new requests are not saved until you clear it.Pro
  • Filter by date range or status code, or delete a single entry.Not yet

Compare two responses

  1. 1Tap ⋮ on an entry and choose Compare with…. A banner asks you to Pick another entry with a response to compare, with Cancel.
  2. 2Tap a second entry that has a response. Compare responses opens with Body and Headers, showing added, removed and unchanged lines (No differences when they match).
  3. 3The diff is line by line; very large bodies fall back to a position-by-position comparison.

Use as mock

⋮ → Use as mock adds a route to the mock server from that entry: its method, only the path of its URL, and the status code and body of the saved response. It doesn't need Pro; switching the server on does.

Collection runner

The runner sends every request of a collection in order, folders included, with the active environment and globals, and reports pass or fail per iteration. It is a Pro feature.

You can

  • Open it from Collections → ⋮ → Run. The header says Runner, and the back gesture returns to Collections.
  • Choose the collection (Pick a collection to run) and set Iterations with − and + (1 to 100).
  • Pick a Data file (Pick file; CSV or JSON). Its number of rows replaces the iterations and disables the stepper; Remove data file undoes it. CSV needs a header line (commas and double quotes, no multiline fields); JSON must be an array of flat objects. Each row feeds {{column}} variables and beats the collection, environment and global ones.
  • Tap Run collection, or Cancel run. The status reads Idle, Running, Completed, Failed or Cancelled; the numbers show Requests, Tests (passed / total) and Duration; each iteration lists its requests with method, code, time and passed / total.

You can't, and why

  • Run it on Free: Run opens the runner, but the API Tester Pro window appears over it and Run collection runs nothing.Pro
  • Add a delay between requests, stop on the first error, save responses or keep variables between runs.Not yet
  • Keep or export the results: they are not saved.Not yet
  • Rely on Failed for network errors: it means an assertion failed, so a request that errors out and has no assertions doesn't mark the run Failed.Not yet

Load test

Load Test sends the open REST request many times and summarises the latency. It is a Pro feature. Several workers send the requests at the same time, so you measure parallel load, not the latency of one client.

You can

  • Open it from ⋮ → Load Test. The TARGET is the method and URL of the request currently loaded; with none open it says No request selected.
  • Set Requests (up to five digits), Concurrency (four) and Ramp-up (s) (three), then tap Start, or Cancel.
  • Use Concurrency (default 10) for the number of workers that send at once. They share the Requests between them, and each sends its next request as soon as the previous one is answered. At most 100 run at once, and never more than Requests; an empty or 0 field means one at a time.
  • Use Ramp-up (s) to start the workers staggered over that many seconds: worker k of n (k counting from 0) starts after ramp-up × k / n seconds. With 0 they all start together.
  • Read the progress (n / N requests); p50, p90, p95 and p99; avg, min and max; req/s; Success and Failed; the Status code distribution; and up to 20 error messages.

You can't, and why

  • Run more than 100 requests at the same time: Concurrency is capped at 100, and at the number of Requests.​By design
  • Set a total duration or a think time: there are no fields for them.Not yet
  • Test a streaming protocol: only the REST request that is loaded.Not yet
  • Start it on Free: the screen opens, but Start opens the API Tester Pro window and no request is sent. The entry carries no badge.Pro

Mock server

A small HTTP server that runs inside the app and answers with canned responses, handy for building a client before the real API exists. Switching it on is a Pro feature; setting up routes is free.

Mock Server sheet, stopped, with port 8090, latency 0, the loopback-only notice and no routes
Mock Server: switch, port, latency, the loopback notice and the routes

You can

  • Open Tools → Mock Server. Switch it on from the header: the subtitle shows http://127.0.0.1:<port>, or Stopped.
  • Set Port (default 8090; 0 lets the system choose one; locked while running) and Latency (ms) (0 to 60,000), added to every answer.
  • Read the notice Listens on loopback only — reachable from this device, not from the network.
  • Tap Add route. New Mock Route asks for a method (GET, POST, PUT or DELETE), Path, Status code and Response body. Each route has an on/off switch and a delete.
  • Read the log of requests served (the sheet shows the last 30 and keeps 200): time, code, METHOD path and the route that matched, or no route matched. Clear all empties it.
  • Get routes from other places too: an OpenAPI import (Generate mock from this OpenAPI) and Use as mock in History.

You can't, and why

  • Edit a route after creating it, or set its headers, delay or priority from the dialog: you can only switch it on or off, or delete it. Imports fill those fields with defaults.Not yet
  • Keep routes and the log when you close the module: they live in memory, and the server stops with the screen.Not yet
  • Reach it from another device or over HTTPS: it listens on loopback only, with no TLS, so your fixtures aren't published on a café Wi-Fi.By design
  • Switch it on on Free: the switch stays off and the API Tester Pro window opens.Pro

How it answers

HTTP/1.1 on 127.0.0.1, one connection per request. A route matches by method and path: :name matches one segment, * one segment and ** the rest; the highest priority wins, then the most specific one; a trailing slash is ignored. The query string and the request body are ignored. With no match you get a 404 with a JSON body that says No mock route matched.

Cookies

The cookie jar is real: it stores the Set-Cookie headers of responses and sends them back by domain (subdomains included), path prefix, expiry and Secure (HTTPS only). It is kept in the device's database. Switch it off for one request with Enable Cookies in Settings.

You can

  • Open Tools → Cookies. The Cookie Jar subtitle counts them (for example 3 stored); each cookie shows its name, value, a lock if Secure, HttpOnly, domain and path.
  • Remove one with ✕, or tap Clear all.
  • Read the cookies of a single response in its Cookies tab.

You can't, and why

  • Add or edit a cookie by hand.Not yet
  • Delete the saved cookies for good: ✕ and Clear all only empty the list that is shown, and the copy stored on the device is not erased, so they can reappear.Not yet
  • Tell host-only cookies from domain cookies: the jar treats them alike.Not yet

Generate code

⋮ → Code Gen opens the Code Generator: pick a target, read the code with its file extension and Copy it. cURL Export in the same menu shows Generated cURL.

You can

  • Choose among 27 targets, which give 26 different outputs (cURL and Shell — cURL are the same command): cURL, HTTPie, Wget; JavaScript (Fetch, Axios, XHR, jQuery); TypeScript (Fetch); Python (Requests, http.client); Java (OkHttp, HttpURLConnection, HttpClient 11+); Kotlin (OkHttp, Ktor); Swift (URLSession); Go (net/http); PHP (cURL, Guzzle); Ruby (Net::HTTP); C# (HttpClient, RestSharp); Rust (reqwest); Dart (http); R (httr); PowerShell; Shell (cURL).
  • Get the method, the URL with its enabled query params, the enabled headers and the body (raw, JSON, XML, HTML, JavaScript, form-urlencoded, or GraphQL as {"query":…,"variables":…}). {{variables}} resolve with the active environment, except secrets, which stay as {{name}}; secret rows show ••••••••.

You can't, and why

  • Get auth in the generated code, except in cURL: every other target leaves it out. cURL adds Bearer, Basic, Digest, Custom and header-based API Key, but not OAuth 2.0 or AWS Signature.Not yet
  • Get a body for Multipart or Binary requests: it comes out empty.Not yet

Import and export

Import lives under Tools → Import. Export is per collection (Collections → ⋮ → Export) and per request (cURL Export).

Import

You can

  • In Import Request, pick a Format: cURL, Postman (v2.1), Insomnia, OpenAPI / Swagger, HAR File or OpenAPI YAML. Paste the text and tap Import; there is no file picker.
  • Expect cURL to replace the open request, and the other five to create a whole collection, announced as Imported "name" — N requests or Import failed: ….
  • With an OpenAPI format, tick Generate mock from this OpenAPI to add a mock route for every method and path.
  • Tap Import from project to read collections saved as files (see Save to the project).

You can't, and why

  • Import a Postman environment (only collections), or import from a file: you paste text.Not yet
  • Import a second collection on Free: the sheet closes and the API Tester Pro window opens.Pro
  • See why a cURL import failed: the error goes only to the console.Not yet

What each format brings

FormatImported
cURLThe usual flags: -X, -H, -d, --data-urlencode, -F, --data-binary, -u, --digest, --ntlm, --proxy, --connect-timeout, -k and -L. --max-redirs is not read. A --proxy is applied when you send, but no screen shows it.
Postman (v2.1)Folders, requests, auth, collection variables and pre-request and test scripts. OAuth 2.0 state beyond the token, response[] and protocolProfileBehavior are ignored.
InsomniaGroups and requests, and the variables of every environment in the file, flattened into one list of collection variables (if a name appears twice, the first one found is used). grpc_request, unit tests, specs and scripts are ignored.
OpenAPI / Swagger, OpenAPI YAMLOpenAPI 3.0 and Swagger 2.0 in JSON or YAML: one request per method and path, grouped in folders by the first tag. $ref isn't resolved and security isn't read. YAML is read by a small built-in parser: no anchors, aliases or multiple documents.
HAR FileHAR 1.2: one request per entry, with no folders and no responses.

Export

You can

  • In Export "name", choose Postman Collection v2.1, Insomnia Export, OpenAPI 3.0, HAR Archive or Markdown Documentation, read the preview and Copy it (Copied to clipboard). Markdown adds response examples from your history, matched by method and URL, the latest winning.

You can't, and why

  • Save an export to a file or share it: you can only copy it.Not yet
Collection exports don't redact credentials: Postman, Insomnia, OpenAPI and HAR carry auth and values as they are in the requests, and Markdown masks only headers marked secret. Check an export before you share it.

Save to the project

A collection can be mirrored as plain JSON files inside the open project, so you can review it in a pull request. The app's database stays the source of truth: the files are a copy you write by hand with a tap, and nothing is committed for you.

Save

  1. 1Open a project. Without one, the Collections ⋮ item reads Open a project to save collections as files and only explains.
  2. 2Tap Collections → ⋮ → Save to project. The app writes .pocketcode/api/<collection>/ and says Saved to .pocketcode/api/ — N files. Commit them with the app's Git manager to keep the change.
  3. 3Commit the files with the app's Git manager when you want to keep them.
  • _collection.json holds the collection's id, name, auth, headers, scripts and variables. Each folder is a sub-directory with a _folder.json. Each request is a <name>.json, slugged from its name in lowercase letters, digits and dashes (-2, -3 on a clash; untitled if nothing is left).
  • Saving again clears that directory and rewrites it from the database, so edits made by hand to the files are overwritten. Environments are not written.
  • Secrets are left out. Before writing, the app empties the values of the auth (bearer token, passwords, API key value, OAuth 2.0 access token and client secret, AWS keys and session token, and so on), of the rows marked Secret value or whose name looks secret (token, secret, key, password, passphrase, auth, cookie, credential) in headers, query params, form fields and collection variables, of secret-looking query params and the password in a user:password@ URL, and the proxy password and certificate passphrase. The structure stays: auth type, header names, user names, URLs.
  • A {{variable}} reference (alone or after Bearer) is not a secret and is written as it is. Keep tokens in a secret environment variable and write {{token}} in the request.

You can

  • Review the files in a pull request and commit them: auth values, secret rows and secret-looking headers, params and form fields are saved empty, so the files show the shape of the collection and not your credentials.

You can't, and why

  • Keep a secret out of a raw request body or a script in the files: both are written as typed, so a token pasted there is committed with them.By design

Import from the project

You can

  • Open Import from project from the Import sheet (it explains Open a project to import collections from files when no project is open).
  • Pick a folder under .pocketcode/api/ and read the preview, which doesn't touch your data: New collection "name" — N requests, or This will replace "name" (N current requests) with M requests from files (a replacement when the id in _collection.json matches an existing collection), plus N file(s) skipped due to errors.
  • Confirm with Import or Replace (red), or Cancel: nothing is applied on its own.
  • On Replace, the secrets you already have stay: a value that arrives empty from the files does not overwrite the one in the local collection with the same id (same auth type, same row). A new collection starts with those values empty.

You can't, and why

  • Import a new collection from files on Free when you already have one: the API Tester Pro window opens. Replacing an existing one is always allowed.Pro

Free and Pro

Almost all of API Tester is free: the six protocols, the full editor, scripts and assertions, the response tools, cookies, import and export, code generation, project files and comparing responses. Pro adds three tools and lifts three limits. On Free, a blocked action opens one window, API Tester Pro, whose text changes with the action (runner, mock server or load test). It lists Collection Runner, Mock server on your phone and Load testing with concurrency, and has Unlock API Tester Pro and Not now. Unlock API Tester Pro closes the API Tester and opens the Pro screen.

FeatureFreePro
Collections1. Creating (New collection or a new name in Save to collection) or importing a second one opens the API Tester Pro window.No limit
Environments1 (a Default one is already there). Creating a second opens the API Tester Pro window.No limit
Request history10 entries. After that new requests aren't saved until you Clear all history; a message says The free plan keeps only the last 10 history entries. This request was not saved.The latest 200 (older ones are deleted)
Mock server: switching it onNo. The switch stays off and the API Tester Pro window opens; routes can still be set up.Yes
Collection runnerNo. Run opens it, but the API Tester Pro window appears over it and Run collection runs nothing; the ⋮ menu of a collection carries a Pro badge.Yes
Load testNo. Start opens the API Tester Pro window; the entry carries no badge.Yes
Everything else: the six protocols, scripts, response tools, cookies, import and export, code generation, project files, comparing, tabsYesYes
The limits are checked on the device when you create, import or save into a new collection, create an environment or save a history entry. For prices and billing periods, see Plans & Pricing

Privacy and security

  • What is stored, and where. Collections, environments, history (each entry with its request and response) and cookies are stored in the app's database on your device.
  • History keeps requests as you wrote them. A {{token}} reference stays a reference; a token you typed straight into Auth or a header is stored as typed.
  • Secrets. A variable or row marked secret is masked in the interface, left as {{name}} or •••••••• in exported cURL and generated code, and never uploaded by Cloud Sync. The real value is sent when you send the request.
  • Project files (Save to project) are written without secrets: the values listed in Save to the project are saved empty, and {{variable}} references stay. The raw body and the scripts are written as typed.
  • Cloud Sync (Pro) doesn't sync collections or environments for now (that option is paused), so they stay on your device.
  • Plain HTTP only to your own device. http:// and ws:// work only for localhost, 127.0.0.1 and 10.0.2.2 (the Android emulator's host); everything else must be HTTPS or wss://. A LAN address such as 192.168.x.x over plain HTTP is blocked: use HTTPS or a tunnel.
  • Certificates. Only the system's certificate authorities are trusted, not ones you installed yourself. With Verify SSL off, any certificate and host name is accepted.
  • The mock server listens on loopback only: nothing else on your network can reach it.
  • Workflows receive the URL, method, status and time of each response sent from this screen, never the body or headers.
  • The AI assistant can send requests through this module without opening it; it receives at most 4096 characters of the response body and can't target PocketCode's own backend.
Collection exports (Postman, Insomnia, OpenAPI, HAR) do not redact credentials: auth and values go as they are in the requests, and Markdown masks only headers marked secret. Check an export before you share it.

Limitations

What is missing today, in one place. “Not yet” means the code has room for it but no screen does.

  • gRPC is in the code but hidden in this version: its panel needs the full protobuf-java library, which the app leaves out, so it can't work on Android yet.Not yet
  • Plain HTTP and ws:// reach only localhost, 127.0.0.1 and 10.0.2.2; a LAN address needs HTTPS.Needs network
  • Only the system's certificate authorities are trusted, so a proxy with a certificate you installed yourself won't work.Needs network
  • No proxy and no client certificate setting.Not yet
  • OAuth 2.0 redirects can't be captured; you paste the code yourself. No PKCE and no refresh token.By design
  • Hawk and NTLM are listed as Soon and do nothing.Not yet
  • WebSocket and SSE can't send headers or reconnect on their own; SSE ignores retry:.​Not yet
  • GraphQL has no subscriptions, operation name, headers or auth in its panel.Not yet
  • MQTT speaks version 5 only and can't publish with retain.Not yet
  • Scripts get a small pm subset and need a modern WebView.By design
  • Mock routes and their log live in memory only and have no edit dialog.Not yet
  • Collections can't be renamed or reorganised, folders can't be created or opened, and saved requests are all called New Request.Not yet
  • Cookies removed from the sheet are not erased from the saved copy.Not yet
  • No image preview, no share or save of a response, and no reason shown for a network error.Not yet
  • Only the cURL output of the code generator includes auth.Not yet
  • History keeps at most 200 entries.By design
  • Errors written by the MQTT and Socket.IO clients are in Spanish whatever the app language.Not yet
  • Raw request bodies and scripts are written as typed into the project files (Save to project): the app cannot tell a secret inside free text.By design

Troubleshooting

0 Error and an empty body

The request got no answer: a network, TLS or timeout failure. The panel doesn't show the reason, but the app writes it to the Console log as a line starting ✗ Request failed:; the error screen has no tabs, so read it in the Console tab of the next response that does arrive (the log covers the whole session). Check the address, your connection and Timeout (ms). A plain http:// address outside localhost, 127.0.0.1 and 10.0.2.2 is blocked: use HTTPS.

Request cancelled

You tapped Cancel request (or the request was cancelled) before the answer arrived. Nothing is wrong.

An API Tester Pro window opens when I tap Run collection, Start or the Mock Server switch

On Free these three are Pro features, and the window says which one you tried. Creating a second collection or environment (including a new name in Save to collection) and importing a collection when you already have one open the same window. Not now closes it; Unlock API Tester Pro opens the Pro screen.

The free plan keeps only the last 10 history entries. This request was not saved.

Free history stops at 10 entries. Tap Clear all history to make room (there is no way to delete a single entry), or move to Pro.

Invalid JSON: …

The JSON body doesn't parse; the text after the colon says where. Fix it before sending, or use Beautify once it is valid.

Import failed: …

The pasted text doesn't match the Format you picked, or the document is malformed. Pick the right format. For cURL there is no message: the error is in the Console log.

Could not save to project: …

The app couldn't write .pocketcode/api/ in the open project; the text after the colon says why.

Open a project to save collections as files

Save to project and Import from project work on the open project. Open one first.

No collections found under .pocketcode/api/ in this project

The open project has no .pocketcode/api/ folder with a _collection.json. Save a collection to the project first, or open the right project.

Couldn't read that file as CSV or JSON data rows

The runner's data file needs a header line if it is CSV (commas and double quotes, no multiline fields), or must be a JSON array of flat objects.

Could not get the token: …

The OAuth 2.0 token request failed; the text says why. Check Token URL, Client ID and Client Secret. With Authorization Code, paste only the code value.

Response did not contain a parseable schema

The GraphQL endpoint didn't answer the introspection query with a schema. Check the URL; some servers turn introspection off.

Error: … in an MQTT or Socket.IO panel

The connection failed; the text says why. Check the host, the port and Use TLS. For MQTT, make sure the broker speaks MQTT 5. Some messages are in Spanish, for example El host no puede estar vacío.

No preview available for this content type

Preview renders only text/html. Use Pretty or Raw for anything else; images can't be previewed.

No match for that path

The JSONPath filter looks up an exact path, such as $.a.b[0].c, not a search. Start from $.

No tests ran for this response

The request has no assertions, and its test script (if it has one) never called pm.test or could not run. Add an assertion in Scripts.

JavaScript engine unavailable on this device

A console warning: this device has no modern WebView for the script engine, so the pre-request or test script was not run. Assertions still ran.

Script error: …

Your script threw an error, often because it uses a part of Postman's API that isn't there (pm.sendRequest, pm.variables, require…). Only the documented pm subset exists.

No enabled routes: every request will get 404 until you add one

A console warning when you switch the mock server on with no enabled routes. A 404 whose body says No mock route matched means the method or path matches no route. If the console says Mock server could not start: …, the port is probably taken: choose another, or 0.