Skip to content
API PLAYGROUND GUIDE

Explore data. Shape an API. Put it to work.

API Playground is a place to explore free sample APIs and turn datasets and ideas into clear JSON endpoints. This page explains what you can try today and how the product is intended to work as it grows.

Sample APIs are liveThe 50 built-in sample APIs have public, paginated JSON endpoints. Saving your own APIs and accounts are not part of this phase.
01 / QUICK START

Try the workbench

  1. Choose a sample. Browse the catalog or search by name; category filters narrow the list.
  2. Load it in the builder. Select Use this API to bring its example route and JSON response into the editor.
  3. Shape the response. Edit the route and JSON body. The response is an example you control in this browser.
  4. Preview your JSON. Select Preview response to format and validate the JSON. Invalid syntax produces an error to fix.
  5. Start fresh. Select New API to replace the current draft with a blank response.
02 / CATALOG

Start with ready-to-explore data

The catalog contains 50 original sample APIs across space, games, films, books, animals, food, music, nature, cities, and science. Each API returns 120 deterministic generated records, so pagination and field selection can be explored without copying third-party datasets.

Use search, category filters, or the catalog’s page controls. Choose Use this API to load a sample endpoint and response into the workbench.

03 / BUILDER

Understand the endpoint draft

The workbench shows a sample API’s live route and a JSON example. Choose a page, the number of records, and optional fields, then use Try live API to open the real endpoint. You can also copy the configured URL.

Endpoint pathThe path a future published API would answer, such as /v1/orbit-atlas/planets.
Response bodyThe JSON returned by that endpoint. Keep it valid JSON and use Preview to check it.

Sample endpoints use GET and support pagination and field selection. The response editor still edits a local example only; edits do not change the live sample API. User-created API publishing, write methods, schemas, and GraphQL are later work.

04 / LIVE SAMPLE ENDPOINTS

Paginate and choose fields

Every catalog endpoint returns JSON with a data array and a pagination object. The default page size is 20; the maximum is 100. Each sample contains 120 records.

First page, 10 recordsGET /v1/orbit-atlas/planets?page=1&limit=10
Only return selected fieldsGET /v1/indie-game-index/games?page=2&limit=5&fields=id,name,genre
Response shape{ "data": [{ "id": "orbit-atlas-001", "name": "Aster planet 001", "type": "terrestrial" }], "pagination": { "page": 1, "limit": 10, "total": 120, "totalPages": 12, "hasNext": true, "hasPrevious": false } }

Unknown endpoints, invalid pagination values, or unavailable fields return a JSON error. Responses are public, CORS-enabled, and cacheable for five minutes at Cloudflare’s edge.

05 / PRODUCT DIRECTION

From prototype to API platform

The intended product is a web-only workspace with accounts and public APIs. The first live milestone is the built-in catalog; the next sequence is:

  1. Improve sample data and add dataset provenance and update notes.
  2. Add accounts and save user-owned drafts and catalog copies.
  3. Publish versioned user APIs and invalidate their edge cache when versions change.
  4. Add request analytics, usage limits, and plan boundaries so hosting costs stay predictable.
  5. Expand endpoint behavior and add GraphQL after the REST flow is stable.

Pricing is still undecided. Free usage can be useful for trying the product, while published API count, request volume, data size, and retention can guide sustainable plan limits.

Explore sample APIs