Reference pages include a runner that fires the described operation against the real API, using the data of the account with an open session.

The call is not made from the browser. The documentation sends the request to the server, which forwards it to the target operation and returns the response. The practical consequence: the API key never travels to the browser nor appears in the response, and a session left open on a shared machine does not expose it.

What can be run

The runner accepts operations of public visibility. Administration operations are out of scope, and account permissions are checked exactly as on a direct call: the runner grants no access the account lacks.

Calls count as real in every sense: they consume quota, produce effects and appear in the account history. Running POST /v1/validate from the documentation creates a validation.

Templates

GET /v1/playground/templates returns example bodies per operation, which the runner preloads. They serve as an editable starting point, not as valid data: the sample identifiers and accounts do not correspond to real records.

Use from an integration

The runner is meant for the documentation, not as an access layer. An integration calls the target operation directly with its own API key, as authentication describes; going through the runner adds a hop with no benefit and requires a browser session.