Skip to content
Prism API

Prism API / Interactive walkthrough

From API key to useful data.

Explore real HTTP requests backed by PostgreSQL. The demo uses three sample projects and nine deployment records in a separate, read-only workspace.

1. Read and paginate

Run this request, then choose Next page. Inspect the cursor, rate-limit headers, and database query count.

GET/v1/projects?first=2&include=owner
curl "https://prism-apis.vercel.app/v1/projects?first=2&include=owner" \  -H "Authorization: Bearer <API_KEY>"
No key yet? or paste one above.

2. Follow a resource

Sandbox mode selects a real sample project ID so this request works without editing placeholders.

GET/v1/projects/YOUR_PROJECT_ID/deployments?first=2
curl "https://prism-apis.vercel.app/v1/projects/YOUR_PROJECT_ID/deployments?first=2" \  -H "Authorization: Bearer <API_KEY>"
No key yet? or paste one above.

3. Compare batching

Open the playground and run its default query with batching on, then off. With three sample projects, batching uses 3 resource queries versus 7 without batching. These counts exclude authentication, rate limiting, and telemetry queries.

Open playground

4. Inspect the contract

REST routes, reference docs, and the TypeScript SDK share the GraphQL schema. CI checks the SDK and validates schema compatibility. Public resource APIs are read-only.

The public sandbox shares a token bucket across visitors: burst 10, refill 1 request/second. A 429 response includes Retry-After. Timing shown by examples is measured for your request; it is not a production latency claim.