FlexDoc 2.8 · published workspace

A local API workspace built on the same request engine as Try It.

FlexDoc 2.8 completes the standalone API Client workspace and adds Postman Collection v2.1 plus environment import. Imported folders, requests, variables, supported auth/body modes and compatible scripts become ordinary FlexDoc workspace data, with explicit warnings wherever Postman behavior cannot be represented faithfully.

Published 2.8 artifact

This page runs ApiClientWorkspace from @prauga/flexdoc-client@2.8.0. Workspace state is browser-local and persists through IndexedDB unless persistence is disabled.

Standalone embed

`ApiClient`

Use the request editor/executor by itself when you want arbitrary HTTP requests without an OpenAPI document, collections or persisted workspace state.

import { ApiClient } from '@prauga/flexdoc-client'

Persistent workspace

`ApiClientWorkspace`

Choose the workspace when you also need collections, nested folders, variables, inherited auth/OAuth, scripts, tests, history, Postman import and optional IndexedDB persistence.

import { ApiClientWorkspace } from '@prauga/flexdoc-client'

Import Postman directly into the canonical workspace

Select Postman Collection v2.1 and environment JSON files together. Supported content is converted into native FlexDoc collections, folders, requests, variables, auth and scripts; unsupported auth, multipart/file and sandbox-specific behavior is surfaced as a compatibility warning instead of silently approximated.

FlexDoc API Client Workspace · 2.8.0

collections · Postman import · variables · auth · scripts · history

2.8 workspace

Local-first, reusable requests

Postman Collection v2.1 and environment exports import through the browser into the same canonical workspace model, with compatibility warnings for unsupported behavior.

Collections, arbitrarily nested folders, saved requests, collection variables and named environments persist in origin-scoped IndexedDB.

Collection, folder and request auth can inherit or override Bearer, Basic, API keys and OAuth 2.0; OAuth supports manual tokens plus browser-compatible grant flows.

Trusted pre-request JavaScript can mutate requests, collection variables and environments; post-response tests render pass/fail output and captured logs.

History keeps resolved execution metadata, test results, logs and originating collection/folder identity while replay restores the raw editable template.

Local data & execution

Saved auth values, collection/environment variables, scripts and history are stored as entered and are not encrypted by FlexDoc. Scripts are trusted local JavaScript, not a sandbox. Nothing is sent until you press Send request.

2.8 API Client example