Skip to content
fetchpier.comFetchpier Docs

Requests and the .http format

Each request is a single .http file that uses standard HTTP syntax plus a small set of comment-prefixed extensions. Because the format is plain text, the same file is readable from any editor and reviewable in a diff.

# @id 9e3a4f72-1234-4abc-9def-0123456789ab
# @rawSubtype: json


# @pre-request-script
# fp.environment.set('token', 'abc')
# @end-script


# @settings
# httpVersion: auto
# verifySsl: true
# followRedirects: true
# maxRedirects: 5
# @end-settings


POST {{baseUrl}}/api/users
Content-Type: application/json


{ "name": "Juan" }

Key elements:

  • {{variable}} placeholders in the URL, headers, body, and form fields are resolved against the active environment merged with any in-flight script mutations.
  • ### is the request separator, but Fetchpier keeps one request per file: when a file holds several, it opens and runs only the first. See Compatibility with other .http tools.
  • # @id <uuid> identifies the request by a stable UUID across renames, so history records keep pointing at the right source even if you move the file.
  • # @rawSubtype: declares the body sub-type (json, xml, javascript, text, html) for syntax highlighting and Content-Type defaults.
  • # @pre-request-script … # @end-script and # @post-response-script … # @end-script carry user scripts as comment-prefixed lines, so the file stays valid .http.
  • # @settings … # @end-settings carries per-request HTTP overrides.
  • # @disable-cookie-jar marks a request that should bypass the cookie jar for this send.
  • # @auth … # @end-auth persists the request’s authentication scheme (type and field mapping) so it survives save / reopen. The active scheme is also materialized into the executable request as a standard header — or a leading query parameter — so the file still sends auth when opened in another .http tool; None writes no block and no materialized entry. A malformed block, including one whose closing line is missing, is reported and ignored, and the request is still loaded and still runnable, without auth.

For the full syntax reference, see The .http format.