API console

Your API application

Create one in the dashboard under Integrations, API applications.

Sign in to pick from your organisations' applications, or enter a client id and secret below.

Shown once, when the application was created or its secret rotated. Held in this page only.

Scopes to ask for

Tick none for every scope the application has.

Leave empty to send the request as your server would. A browser application only accepts requests from its allowed origins, so pick one of them.

No token yet.

GET /api/v1/products/{product_slug}/journeys/{slug}/questions

Get a journey's questions

Journeys Scopes: read or write Read the docs

Path

The product's slug, shown on its page in the dashboard under Products.

The journey's slug, from List a product's journeys.

Query

Which of the journey's presentations to use, by its address slug. Leave it out for the journey's default presentation (an unknown slug also gives the default).

An application already under way on this journey. Its questions and presentation are the ones it started with. An id that isn't one of yours, or is on another journey, is ignored. So is one a browser application sends without the application's share_token in X-Share-Token.

Headers

The application's share_token, from the answer that started it. A browser application sends it with every request about an application that already exists, a replay of the request that started it included. Without it, or with another application's, the answer is 404 not_found (409 idempotency_replay_unproven on a replay). A server-only application doesn't need it.

Ctrl + Enter sends too

Response

Send a request to see its response here.

Code

curl

The code reads your token from the SUBCONTEXT_TOKEN environment variable.