Skip to main content
PanoFlow runs a development copy of the API while the platform is being built. It’s useful for trying requests from the API reference, or from your own code, without touching anything real.

​
Using it from the API reference

On any endpoint page, open the playground and choose Development (Railway) in the server picker. Requests then go to the development server instead of production.

​
What works today

The development server runs whatever has been built so far, so not every endpoint in the reference answers yet:
  • Built: platform behaviour that every endpoint shares, including errors, idempotency, pagination, rate limits, request ids and validation against the contract. Sign-up and sign-in are built as they land, but they’re used by the PanoFlow web app and aren’t listed in this reference.
  • Not yet: endpoints whose features haven’t been built answer 404 with code resource_not_found. They switch on as each part of the platform is released.
  • API keys arrive with the developer platform. Until then, requests that need a key can’t be authenticated on the development server.
Responses follow the contract version shown in the reference. Each one carries an X-Request-Id, and quoting it helps when something looks wrong.

​
Health

GET https://api-dev-9d8b.up.railway.app/readyz reports whether the server, its database and its cache are up, and which contract version it runs.