connekt-script-writer

Create a .connekt.kts file, read the base URL with val host: String by env, then declare requests like GET("$host/api/pets") then { assert(code == 200) }. The script registers requests and the runner executes them, so no imperative code goes between requests.

Capture the value in a then block with decode, for example val petId by POST(...) then { decode<Long>("$.id") }, then reference it in the next request using a {petId} URL placeholder with pathParam("petId", petId). Never interpolate the value directly into the URL string.

Use useCase only when a scenario involves multiple requests passing results between each other, such as creating a resource and then verifying it. A single HTTP request, even with a then block, should never be wrapped in useCase.

Yes, declare val auth by oauth(...) with authorize and token endpoints, client credentials, scope, and a redirect URI. It opens a browser for login and starts a local callback server, then you use bearerAuth(auth.accessToken) on protected requests. A Keycloak shorthand via KeycloakOAuthParameters is also available.

A Connekt script only registers requests; the runner decides what to execute, so top-level imperative code does not run as expected. Assertions and logic must live inside then or useCase blocks, with only declarations like env vals, data classes, and request definitions allowed at the top level.

Store values in connekt.env.json under an env object and read them with property delegation, such as val host: String by env. Supported types are String, Int, Long, Double, and Boolean, and missing keys throw an error.