Session
Session
https://app.nokku.sh/nokku.v1.DaemonSessionService/Sessionheader Parameters
Authorization
BearerAuth (bearer)
PASETO token authentication. Include the token in the Authorization header: `Authorization: Bearer <token>`
CookieAuth (apiKey in cookie)
Cookie-based authentication (recommended for web applications). The session cookie is automatically sent by browsers after login.
Request Body
requiredOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutOne of
Option 1?exitedexitCode?errorMessage?Option 2?readysessionId?replayBuffer?username?userId?Option 3?stdoutResponses
200Success
200Success
One of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdinOne of
Option 1?closereason?Option 2?resizewidth?height?Option 3?stdindefaultError
defaultError
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message, with an additional debug field for ConnectRPC error details.
type?A URL that acts as a globally unique identifier for the type of the serialized message. For example: `type.googleapis.com/google.rpc.ErrorInfo`. This is used to determine the schema of the data in the `value` field and is the discriminator for the `debug` field.
value?The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.
debug?Deserialized error detail payload. The 'type' field indicates the schema. This field is for easier debugging and should not be relied upon for application logic.
One of
Option 1?Detailed error information.
Code Samples
curl -X POST 'https://app.nokku.sh/nokku.v1.DaemonSessionService/Session' \
-H "Authorization: Bearer <token>" \
-H 'Content-Type: application/json' \
-d '{
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}'const response = await fetch('https://app.nokku.sh/nokku.v1.DaemonSessionService/Session', {
method: 'POST',
headers: {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
},
body: JSON.stringify({
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}),
});
const data = await response.json();
console.log(data);import requests
url = 'https://app.nokku.sh/nokku.v1.DaemonSessionService/Session'
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
payload = {
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}
response = requests.post(url, headers=headers, json=payload)
print(response.json())package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
body := bytes.NewBuffer([]byte(`{
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}`))
req, err := http.NewRequest("POST", "https://app.nokku.sh/nokku.v1.DaemonSessionService/Session", body)
if err != nil { panic(err) }
req.Header.Set("Authorization", "Bearer <token>")
req.Header.Set("Content-Type", "application/json")
res, err := http.DefaultClient.Do(req)
if err != nil { panic(err) }
defer res.Body.Close()
payload, err := io.ReadAll(res.Body)
if err != nil { panic(err) }
fmt.Println(string(payload))
}using System.Net.Http;
using System.Net.Http.Headers;
using var client = new HttpClient();
using var request = new HttpRequestMessage(HttpMethod.Post, "https://app.nokku.sh/nokku.v1.DaemonSessionService/Session");
request.Headers.Add("Authorization", "Bearer <token>");
request.Content = new StringContent(
""""{
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}"""",
System.Text.Encoding.UTF8,
"application/json"
);
using var response = await client.SendAsync(request);
response.EnsureSuccessStatusCode();
Console.WriteLine(await response.Content.ReadAsStringAsync());import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class Main {
public static void main(String[] args) throws Exception {
HttpClient client = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://app.nokku.sh/nokku.v1.DaemonSessionService/Session"))
.header("Authorization", "Bearer <token>")
.header("Content-Type", "application/json")
.method("POST", HttpRequest.BodyPublishers.ofString("""{
"exited": {
"exitCode": 0,
"errorMessage": "string"
}
}"""))
.build();
HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}Example Responses
{
"close": {
"reason": "string"
}
}{
"code": "not_found",
"message": "string",
"details": [
{
"type": "string",
"value": "string",
"debug": {}
}
]
}