01 — Overview
Half the systems a team relies on have an API and no admin screen. Connect the API once with its base URL and auth method, such as a bearer token, OAuth 2.0 or a custom header, and describe the job the tool should do. If you have an OpenAPI or Swagger file, import it and the Bench learns every endpoint, parameter and response shape at once. Pagination, retries and error states are handled for you, so a slow endpoint shows a clear message instead of a blank screen.
Apps call the API from Chamfer’s servers, never from the browser, so tokens are never exposed to users. Add rate limits per app, retries for flaky endpoints and a Sign-off for any call that moves money or deletes data. The Logbook records each request with the user, endpoint, status code and duration, which makes a failed call easy to trace.
02 — What you can do
OpenAPI import
Import an OpenAPI or Swagger file and the Bench builds forms from its parameters.
Server-side calls
Requests run from Chamfer's servers, so tokens and keys never reach the browser.
Request history
Every call is logged with user, endpoint, status and timing, ready to filter or export.
03 — FAQ
Before you connect REST API
Which authentication methods are supported?
Can Chamfer reach an API in our private network?
How are rate limits and failures handled?
Do we need an OpenAPI file?
04 — Pairs well with