All projects

Web app / 2026

Endpoint Studio

An interactive REST API workbench for exploring real requests, responses and private demo data.

An orange and charcoal API instrument panel with a spirograph and MAKE CONTACT headline.

The project

Endpoint Studio turns my WEB 420 REST API coursework into an interactive developer workbench. Its orange and charcoal instrument-panel layout pairs kinetic typography and a rotating spirograph with split-flap-style response codes. The visual feedback follows real request activity, so the interface makes the backend easier to explore.

Choose composers, people, teams or customers; create a private workspace; then send a request and inspect its response. The recovered API also includes team players, customer invoices and a signup/password-verification exercise. Example requests make the workflows approachable without hiding the JSON or HTTP methods.

How it works

A Node.js and Express API validates requests and stores visitor records in an isolated workspace. The Azure deployment uses native MongoDB access to the existing shared Cosmos DB database. A random bearer credential identifies each workspace; only its hash is stored on the server. Password examples use salted scrypt hashes, and invoice totals are calculated by the server.

Visitor workspaces expire 96 hours after creation. Editing data or signing in does not renew the deadline. Expired data is rejected by the API and physically removed by the next successful cleanup job. Fictional, read-only examples are bundled with the application and remain available after cleanup.

The signup exercise demonstrates password verification within a private demo workspace; it is not a production identity service. Visitors should use fictional details and a password they do not use elsewhere.

Built together

I worked with ChatGPT/Codex to recover the coursework, modernize its dependencies and build an interface around the real API. Validation covers private workspace isolation, expiry boundaries, immutable examples, malformed input, password handling, invoice preservation and database persistence. Customer edits also preserve unique usernames so invoice routes remain unambiguous.

The live demo is published with automated checks and deployment through GitHub Actions.

Thanks for taking a look.Back to the collection