> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blips.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Playground

> How BLIPS Try It is bound to the Public Test Backend and what remains intentionally outside the public boundary.

# Playground

Mintlify generates the BLIPS API Playground from the same OpenAPI 3.1 source as the reference pages.

The current public state is:

* the API Reference is ready for browsing
* interactive Playground pages are generated from the OpenAPI source
* Try It is pointed at the confirmed Public Test Backend at `https://public-test.blips.network`
* the current docs surface is internet-testable
* this page does not describe the current Public Test Environment as production-ready

## Sandbox API note

The Playground also exposes a small Sandbox APIs group at the end of the Reference navigation for Public Test and demo use. Those requests go to the same `https://public-test.blips.network` backend target as the rest of the docs site.

That trailing sandbox group now contains:

* the sandbox Lightning execution-profile routes, which feed `POST /quotes` indirectly
* `POST /sandbox/incoming-payments/simulate`, which creates Step 4 review cases and then hands ongoing review work back to:
  * `GET /transactions`
  * `GET /transactions/{transactionId}`
  * `POST /transactions/{transactionId}/approve`
  * `POST /transactions/{transactionId}/reject`

The incoming-payment simulation route is Public Test / demo only, is not the real incoming-payment ingestion surface, and is not a second transaction system.

The Step 4 decision model is intentionally visible in the site copy and Playground-generated endpoint pages:

* `sanctions_hit` is reject-only
* `sender_kyc_not_approved` is reject-only
* `counterparty_info_incomplete` is manual-review-required and stays on the same transaction review lane

## What the Playground uses from OpenAPI

* `servers` to determine where requests are sent
* `securitySchemes` and `security` to render authentication inputs
* `parameters` and `requestBody` to build request forms
* `responses` and `examples` to display result shapes and sample payloads

## Public Try It contract

* Public Try It uses platform token Basic Auth.
* The backend target is the confirmed public ingress host and not the legacy/private runtime.
* Only the retained public routes present in `openapi/blips-public-reference.yaml` are exposed through the generated Playground.
* The sandbox routes use the same backend target and auth surface as the rest of the Reference, but remain visually separated from the core business API families.

## Boundary negatives

The public docs and Playground do not advertise or target:

* `/platforms`
* `/internal/*`
* `/payments/*`
* legacy-only routes
* operator/bootstrap-only surfaces

That means public Try It stays bound to the retained public ingress boundary and never falls through to the legacy/private host.

## Public Test Backend note

This Try It surface is now wired to the confirmed Public Test Backend. It is intended for internet-testable public API verification and credentialed request testing, without presenting the environment as production-ready.