Glossary

Core terms used across the Fetchpier documentation.

• Workspace — the root folder you open. Holds your requests, environments, cookies, and activity log as plain files. See Workspaces.
• Collection — a sub-folder under requests/. Folders nest to form sub-collections.
• Request — a single HTTP call, stored as a .http file. See Requests (.http).
• .http file — the plain-text file format Fetchpier reads and writes; standard HTTP plus comment-prefixed directives. See The .http format.
• Environment — a named set of variables stored as JSON. One is active at a time. See Environments.
• Variable — a {{name}} placeholder resolved against the active environment. See Variables.
• Cookie jar — the per-environment store of cookies, auto-captured and auto-attached per RFC 6265. See Cookies.
• Pre-request script — JavaScript that runs before a request is sent and can mutate it. See Pre-request scripts.
• Post-response script — JavaScript that runs after the response arrives. See Post-response scripts.
• Sandbox — the isolated, synchronous environment scripts run in, exposing a single global fp. See the execution model.
• fp — the only global available to scripts: request/response access, environment and variable read/write, tests, assertions, and logging.
• Test — an assertion registered with fp.test(name, fn); results appear in the Tests tab. See Tests and assertions.
• Activity record — the JSON file written to requests/.runs/ for every send. See History.
• CA certificate / client certificate — TLS material imported into Fetchpier’s own trust store. See TLS and certificates.
• Schema import — generating a collection from an OpenAPI, GraphQL, Postman, or WSDL schema. See the import overview.