Requests
Open and save
Click a request in the sidebar to open it in a preview tab (its name is in italics): the next click replaces it. Edit the request or double-click it to keep the tab. ⌘-click opens a request in a new tab.
Changes are kept as a draft until you press ⌘S. A dot on a tab means it has unsaved changes. Open tabs and drafts survive a restart.
⌘T opens a new request. When you save it the first time, FleetFoot asks for a name and a collection or folder.
URL and parameters
Type the URL with {{variables}} right in the address bar. The Params tab stays in step with it: editing one updates the other. A parameter that is switched off stays in the table but is not sent.
Path variables such as /users/:id get their own table under the parameters.
Paste a cURL command
Paste a curl … command into the address bar and FleetFoot turns it into a request: method, URL, headers, body and basic auth. Copy as cURL (⌘⇧C) does the opposite.
Headers
Add headers in the Headers tab; the key column suggests common names. Headers added automatically shows what FleetFoot adds for you: the content type of the body, the auth header, Host, User-Agent. A header with the same name that you add yourself wins.
Body
| Mode | Sent as |
|---|---|
| Raw | text with a content type for JSON, text, XML, HTML or JavaScript; Beautify re-indents JSON without changing values |
| Form data | multipart/form-data, text fields and files |
| URL-encoded | application/x-www-form-urlencoded |
| Binary file | the file as is |
| GraphQL | a JSON body with the query and the variables |
Like Postman, FleetFoot does not send a body with GET unless you allow it for the request. Edit the body of a GET request and it is allowed automatically.
Auth
A request can use Bearer token, Basic auth, API key (in a header or in the query), No auth, or Inherit from parent (the default). Inherited auth comes from the nearest folder that sets one, then from the collection; the Auth tab shows where it comes from.
Settings of a request
The Settings tab overrides the app settings for one request: follow redirects, verify TLS certificates, send a body with GET, and use the cookie jar.
History
Every request you send is kept in History in the sidebar, with its response. Click an entry to open it in a new tab.