Nokku LogoNokku
Nokku LogoNokku

VerifyCLILogin

VerifyCLILogin

nokku.v1.AuthService
POST
https://app.nokku.sh/nokku.v1.AuthService/VerifyCLILogin

header Parameters

Connect-Protocol-Versionnumberrequired
Example 1
Connect-Timeout-Ms?number
Example 0

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

required

application/json

object
loginCode?
string

Responses

200

Success

application/json

object
default

Error

application/json

object

Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation

code?
string

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

Enum:"canceled""unknown""invalid_argument""deadline_exceeded""not_found""already_exists""permission_denied""resource_exhausted""failed_precondition""aborted""out_of_range""unimplemented""internal""unavailable""data_loss""unauthenticated"
message?
string

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?
array<object>

A list of messages that carry the error details. There is no limit on the number of messages.

object

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?
string

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?
string <binary>

The Protobuf message, serialized as bytes and base64-encoded. The specific message type is identified by the `type` field.

debug?
one of 1

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?
object

Detailed error information.

Code Samples

Example Responses