ably-auth-openapi 0.2.0

Unofficial generated OpenAPI bindings for the Ably platform auth REST API (token issuance/revocation, server time). Not affiliated with or endorsed by Ably. Prefer the `ably-chat-rs` crate.
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
43
44
45
46
47
48
49
50

/*
 * Ably Platform Auth REST API
 *
 * The subset of the Ably **platform** REST API used for authentication and token lifecycle: requesting Ably Tokens, revoking them, and reading server time. This is a *separate* API from the Ably Chat REST API (`openapi/ably-chat-rest.yaml`, path prefix `/chat/v4`) — token issuance and revocation live on the platform host under `/keys/...`, not under `/chat/_*`.  ## Scope & provenance Ably publishes an authoritative platform spec, [`ably/open-specs`](https://github.com/ably/open-specs) `platform-v1.yaml`, which covers the full generic pub/sub REST API (`/channels`, `/push`, `/keys`, `/stats`, `/time`). **This document is deliberately narrow**: it models only the endpoints this project's authentication story ([ADR-0012](../docs/adr/0012-token-issuance-permissions.md), [SPEC §13](../docs/SPEC.md)) touches — `POST /keys/{keyName}/requestToken`, `POST /keys/{keyName}/revokeTokens`, and `GET /time`. Field-level details are cross-checked against `platform-v1.yaml`, the Ably auth docs, and the `ably-js` auth implementation (see [`../docs/research/2026-07-24-ably-chat-auth-permissions.md`](../docs/research/2026-07-24-ably-chat-auth-permissions.md)).  ## Relationship to the Chat client `ably-chat-rs` is a Chat REST client; it does not itself sign TokenRequests or call `/keys/...` (ADR-0012 Tier 4). This spec documents the platform endpoints a *token server* (or the official `ably` crate) uses to mint the Bearer credentials that are then handed to the Chat client. Capability documents carried by these tokens are described in SPEC §13, not here. 
 *
 * The version of the OpenAPI document: 1.0.0
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

/// TokenDetails : An issued Ably Token. The `token` string is presented as a Bearer credential.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct TokenDetails {
    /// The token string, sent as `Authorization: Bearer <token>`.
    #[serde(rename = "token")]
    pub token: String,
    /// The API key name the token was issued from.
    #[serde(rename = "keyName", skip_serializing_if = "Option::is_none")]
    pub key_name: Option<String>,
    /// Milliseconds since the Unix epoch at which the token was issued.
    #[serde(rename = "issued", skip_serializing_if = "Option::is_none")]
    pub issued: Option<i64>,
    /// Milliseconds since the Unix epoch at which the token expires.
    #[serde(rename = "expires", skip_serializing_if = "Option::is_none")]
    pub expires: Option<i64>,
    /// A capability document as a JSON **string** (a stringified object mapping resource-name patterns to arrays of operations, e.g. `{\"my-room\":[\"publish\",\"history\"]}`). For a signed `TokenRequest` this string must be canonicalized (resource keys and operation arrays sorted, no whitespace) because it is part of the HMAC-signed text. See SPEC §13. 
    #[serde(rename = "capability", skip_serializing_if = "Option::is_none")]
    pub capability: Option<String>,
    /// The identity bound to the token, if any.
    #[serde(rename = "clientId", skip_serializing_if = "Option::is_none")]
    pub client_id: Option<String>,
}

impl TokenDetails {
    /// An issued Ably Token. The `token` string is presented as a Bearer credential.
    pub fn new(token: String) -> TokenDetails {
        TokenDetails {
            token,
            key_name: None,
            issued: None,
            expires: None,
            capability: None,
            client_id: None,
        }
    }
}