STUD
← Plays

Build · Create · Engineering

OpenAPI endpoint reference

A complete, well-formed reference for one endpoint: method, path, parameters (with every path placeholder covered), the required status codes, and a consistent request body.

You receive: A structured endpoint reference (JSON) that passes the method, path-parameter, response-code, and body checks.

Part of Ship MVP

What's verified: STUD verifies the submitted endpoint reference (JSON) is well-formed and complete: the HTTP method and path are valid and match your intake, every {placeholder} in the path has a required path parameter, parameters are typed and non-duplicated, the required status codes are all documented, and a request body is present and typed exactly when one is required. STUD does NOT call the endpoint or verify the descriptions are accurate; it checks the reference's structure.

Opens soon

Cost20 credits
ProtectionHeld until verified delivery

This play is verified and ready. It opens soon, once sign-in and payments are live.

Example

A sample of what this play produces. Your result is generated for your inputs.

Method

POST

Path

/plays/{playId}/runs

Parameters

NameInRequiredTypeDescription
playIdpathtruestringUUID of the play to run.
Idempotency-KeyheaderfalsestringClient-supplied key that makes a retried commission safe to resend.

Responses

StatusDescription
201The run was created and queued for the judge.
404No play exists with the given playId.
422The intake is missing a required buyerParamKey or fails validation.

Request body

Schema fields
NameTypeDescription
intakeobjectThe buyer's frozen answers, one entry per buyerParamKey the play declares.
idempotency_keystringOptional dedupe key echoing the Idempotency-Key header.

Get early access to STUD the day it goes live.