technitium 0.4.0

Typed async Rust client for the Technitium DNS Server API
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

# Delete User Session

## Endpoint

`/api/user/session/delete`

## Method

GET

## Description

Allows deleting a session for the current user. The session to delete is identified by a partial token value (as returned by the user profile details API call).

## Parameters

| Name | Type | Required | Conditional | Description |
|------|------|----------|-------------|-------------|
| `token` | string | Yes | - | The session token generated by the `login` or the `createToken` call (used for authentication). |
| `partialToken` | string | Yes | - | The partial token identifying the session to delete, as returned by the user profile details API call (`/api/user/profile/get`). |

## Authentication

Requires a valid token (session token from login or API token from createToken).

## Response Fields

| Field | Type | Description |
|-------|------|-------------|
| `response` | object | Empty object `{}` on success. |
| `status` | string | `"ok"` on success. |

## Conditional Logic Notes

- The `partialToken` value must be obtained from the `sessions` array in the user profile details response (`/api/user/profile/get`), where each session has a `partialToken` field.
- This endpoint only allows deleting sessions belonging to the currently authenticated user.

## Edge Cases

- Deleting the current session (the one identified by the `token` parameter itself) would effectively log the user out.
- The `partialToken` is a truncated version of the full token (e.g., `"620c3bfcd09d0a07"`), not the full token value.
- The response contains an empty `response` object, unlike most other endpoints which either omit the `response` field or include data in it.