Juno

REST API concepts

Understand what each REST action does. Use the reference for exact payloads and responses.

7 topics4 min read

Create study

Send the user's brief as guidance. If documents are part of the brief, upload them first and include their file_ids. Uploading a file by itself does not create or change a study.

Update study

Give Juno further guidance to change an existing study. Include file_ids when new documents are part of the update. The REST path :refine and MCP tool refine_study retain their wire names.

Check study job

Create and update requests return a job_id. Poll that job until status is ready, then use the returned study_id.

Simulate interview

Test mode is a safe preview. The user can simulate an interview with a synthetic participant to understand its shape. Test mode uses no credits, provides no analysis or exports, and is not for real participant research. The current API does not enforce mode=test, so developers must honour that product contract.

Set study mode

Set an explicit target; the endpoint never toggles blindly. 'test' selects Test mode. 'live' selects Live mode and performs Go live the first time. 'paused' and 'closed' are technical collection states. Setting 'live' requires studies:golive; other changes require studies:write.

Get the durable invite link after setting mode to live. The user shares it with participants. The REST path retains the technical name /interview-link.

Full endpoint reference

Browse the full API reference Every endpoint, request, and response — rendered live from the OpenAPI spec, with copy-paste examples in your language.
Machine-readable spec Point your codegen at the raw OpenAPI document at /v1/api/openapi.json to generate a typed client.