--- source_url: https://www.pubnub.com/docs/sdks/ruby/api-reference/access-manager title: Access Manager v3 API for Ruby SDK updated_at: 2026-05-20T11:08:10.401Z sdk_name: PubNub Ruby SDK sdk_version: 6.0.2 --- > Documentation Index > For a curated overview of PubNub documentation, see: https://www.pubnub.com/docs/llms.txt > For the full list of all documentation pages, see: https://www.pubnub.com/docs/llms-full.txt # Access Manager v3 API for Ruby SDK PubNub Ruby SDK, use the latest version: 6.0.2 Install: ```bash gem install pubnub@6.0.2 ``` :::warning Access Manager isn't enabled by default Without it, PubNub resources on this keyset have no access controls and clients can reach channels and metadata without permission checks. Enable Access Manager in [Admin Portal](https://admin.pubnub.com/) before deploying to production. ::: Access Manager allows you to enforce security controls for client access to resources within the PubNub Platform. With Access Manager v3, your servers (that use a PubNub instance configured with a secret key) can grant their clients tokens with embedded permissions that provide access to individual PubNub resources: * For a limited period of time. * Through resource lists or patterns (regular expressions). * In a single API request, even if permission levels differ (`read` to `channel1` and `write` to `channel2`). You can add the [authorizedUuid](https://www.pubnub.com/docs/general/security/access-control#authorized-uuid) parameter to the grant request to restrict the token usage to one client with a given `userId`. Once specified, only this `authorizedUuid` will be able to use the token to make API requests for the specified resources, according to permissions given in the grant request. :::note User ID / UUID User ID is also referred to as **UUID/uuid** in some APIs and server responses but **holds the value** of the **userId** parameter you [set during initialization](https://www.pubnub.com/docs/general/setup/users-and-devices#set-the-user-id). ::: ## Grant token :::note Requires Access Manager add-on This method requires that the *Access Manager* add-on is enabled for your key in the [Admin Portal](https://admin.pubnub.com/). Read the [support page](https://support.pubnub.com/hc/en-us/articles/360051974791-How-do-I-enable-add-on-features-for-my-keys-) on enabling add-on features on your keys. ::: :::warning Requires Secret Key authentication Granting permissions to resources should be done by administrators whose SDK instance has been [initialized](https://www.pubnub.com/docs/sdks/ruby/api-reference/configuration) with a **Secret Key** (available on the [Admin Portal](https://admin.pubnub.com/) on your app's keyset). ::: The `grant_token()` method generates a time-limited authorization token with an embedded access control list. The token defines time to live (`ttl`), `authorized_user_id`, and a set of permissions giving access to one or more resources: * For a limited time period. * Through resource lists or regular expression (RegEx) patterns. * In one API request, even when permissions differ. * channels * channel_groups * uuids (other users' object metadata, such as their names or avatars) Only this `authorized_user_id` will be able to use the token with the defined permissions. The authorized client will send the token to PubNub with each request until the token's `ttl` expires. Any unauthorized request or a request made with an invalid token will return a `403` with a respective error message. ###### Permissions The grant request allows your server to securely grant your clients access to the resources within the PubNub Platform. There is a limited set of operations the clients can perform on every resource: | Resource | Permissions | | --- | --- | | `channel` | `read`, `write`, `get`, `manage`, `update`, `join`, `delete` | | `channel_group` | `read`, `manage` | | `uuid` | `get`, `update`, `delete` | For permissions and API operations mapping, refer to [Manage Permissions with Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#permissions). ###### TTL (time to live) The `ttl` (time to live) parameter defines how many minutes the permissions remain valid. After expiration, the client must get a new token to maintain access. `ttl` is required for every grant call. There is no default value. The maximum value is 43,200 (30 days). For more details, see [TTL in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#ttl). ###### RegEx patterns Use regular expressions (RegEx) to specify permissions by pattern instead of listing each resource. Define RegEx permissions as `pattern` before making a grant request. Patterns are evaluated on the server using [RE2-style syntax](https://github.com/google/re2/wiki/Syntax); backreferences and lookaround assertions are not supported. For more details, see [RegEx in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#regex). ###### Authorized UUID Setting an `authorized_user_id` in the token specifies which client should use this token in every request to PubNub. If you do not set `authorized_user_id` during the grant request, the token can be used by any client with any UUID. Restrict tokens to a single `authorized_user_id` to prevent impersonation. For more details, see [Authorized UUID in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#authorized-uuid). ### Method(s) ```ruby grant_token( ttl: ttl, authorized_user_id: authorized_user_id, uuids: uuids, channels: channels, channel_groups: channel_groups ) ``` | Parameter | Description | | --- | --- | | `ttl` *Type: `Integer`Default: n/a | Total number of minutes for which the token is valid. The minimum allowed value is 1., The maximum is 43,200 minutes (30 days). | | `authorized_user_id`Type: `String`Default: n/a | Single `uuid` which is authorized to use the token to make API requests to PubNub. | | `uuids`Type: `Hash`Default: n/a | Hash containing `uuid` metadata permissions provided either as a list or a RegEx pattern, for example: `{"uuid-1": Pubnub::Permissions.res(get: true, update: true, delete: true),"^uuid-2.$": Pubnub::Permissions.pat(...)}`. | | `channels`Type: `Hash`Default: n/a | Hash containing channel permissions provided either as a list or a RegEx pattern, for example: `{"channel-1": Pubnub::Permissions.res(read: true, write: true, manage: true, delete: true, get: true, update: true, join: true),"^channel-2.$": Pubnub::Permissions.pat(...)}`. | | `channel_groups`Type: `Hash`Default: n/a | Hash containing channel group permissions provided either as a list or a RegEx pattern, for example: `{"group-id-1": Pubnub::Permissions.res(read: true, manage: true),"^group-id-2.$": Pubnub::Permissions.pat(...)}`. | | `meta`Type: `Object`Default: n/a | Extra metadata to be published with the request. Values must be scalar only; arrays or objects aren't supported. | :::note Required key/value mappings For a successful grant request, you must specify permissions for at least one `uuid`, `channel`, or `channel_groups`, either as a resource list or as a pattern (RegEx). ::: ### Sample code :::tip Reference code This example is a self-contained code snippet ready to be run. It includes necessary imports and executes methods with console logging. Use it as a reference when working with other examples in this document. ::: ```ruby require 'pubnub' def grant_token(pubnub) future_result = pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-uuid", channels: { "my-channel" => Pubnub::Permissions.res(read: true) } ) result = future_result.value result.result[:data]['token'] end def main # Configuration for PubNub instance pubnub = Pubnub.new( subscribe_key: ENV.fetch('SUBSCRIBE_KEY', 'demo'), publish_key: ENV.fetch('PUBLISH_KEY', 'demo'), secret_key: ENV.fetch('SECRET_KEY', 'my_secret_key'), user_id: 'myUniqueUserId' ) begin # Grant token token = grant_token(pubnub) puts "Token granted successfully: #{token}" rescue StandardError => e puts "Error: #{e.message}" end end if __FILE__ == $0 main end ``` ### Returns ```ruby # { "message" => "Success", "token" => "p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI" } }, @status = { :code => 200 } > ``` ### Other examples #### Grant an authorized client different levels of access to various resources in a single call The code below grants `my-authorized-uuid`: * Read access to `channel-a`, `channel-group-b`, and get to `uuid-c`. * Read/write access to `channel-b`, `channel-c`, `channel-d`, and get/update to `uuid-d`. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-uuid", channels: { "channel-a": Pubnub::Permissions.res( read: true ), "channel-b": Pubnub::Permissions.res( read: true, write: true ), "channel-c": Pubnub::Permissions.res( read: true, write: true ), "channel-d": Pubnub::Permissions.res( read: true, write: true ) }, channel_groups: { "channel-group-b": Pubnub::Permissions.res( read: true ) }, uuids: { "uuid-c": Pubnub::Permissions.res( get: true ), "uuid-d": Pubnub::Permissions.res( get: true, update: true ) } ); ``` #### Grant an authorized client read access to multiple channels using RegEx The code below grants `my-authorized-uuid` read access to all channels that match the `channel-[A-Za-z0-9]` RegEx pattern. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-uuid", channels: { "^channel-[A-Za-z0-9]$": Pubnub::Permission.pat( read: true ) }, ); ``` #### Grant an authorized client different levels of access to various resources and read access to channels using RegEx in a single call The code below grants the `my-authorized-uuid`: * Read access to `channel-a`, `channel-group-b`, and get to `uuid-c`. * Read/write access to `channel-b`, `channel-c`, `channel-d`, and get/update to `uuid-d`. * Read access to all channels that match the `channel-[A-Za-z0-9]` RegEx pattern. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-uuid", channels: { "channel-a": Pubnub::Permissions.res( read: true ), "channel-b": Pubnub::Permissions.res( read: true, write: true ), "channel-c": Pubnub::Permissions.res( read: true, write: true ), "channel-d": Pubnub::Permissions.res( read: true, write: true ), "^channel-[A-Za-z0-9]$": Pubnub::Permission.pat( read: true ) }, channel_groups: { "channel-group-b": Pubnub::Permissions.res( read: true ) }, uuids: { "uuid-c": Pubnub::Permissions.res( get: true ), "uuid-d": Pubnub::Permissions.res( get: true, update: true ) } ); ``` ### Error responses If you submit an invalid request, the server returns HTTP 400 with a message that identifies the missing or incorrect argument. Causes can include a RegEx issue, an [invalid timestamp](https://support.pubnub.com/hc/en-us/articles/360051973331-Why-do-I-get-Invalid-Timestamp-when-I-try-to-grant-permission-using-Access-Manager-), or incorrect permissions. The server returns error details in JSON. ## Grant token - spaces & users :::note Requires Access Manager add-on This method requires that the *Access Manager* add-on is enabled for your key in the [Admin Portal](https://admin.pubnub.com/). Read the [support page](https://support.pubnub.com/hc/en-us/articles/360051974791-How-do-I-enable-add-on-features-for-my-keys-) on enabling add-on features on your keys. ::: The `grantToken()` method generates a time-limited authorization token with an embedded access control list. The token defines time to live (`ttl`), `authorizedUserId`, and a set of permissions giving access to one or more resources: * `spaces` * `users` (other users' metadata, such as their names or avatars) Only this `authorizedUserId` will be able to use the token with the defined permissions. The authorized client will send the token to PubNub with each request until the token's `ttl` expires. Any unauthorized request or a request made with an invalid token will return a `403` with a respective error message. ###### Permissions The grant request allows your server to securely grant your clients access to the resources within the PubNub Platform. There is a limited set of operations the clients can perform on every resource: | Resource | Permissions | | --- | --- | | `space` | `read`, `write`, `get`, `manage`, `update`, `join`, `delete` | | `user` | `get`, `update`, `delete` | For permissions and API operations mapping, refer to [Manage Permissions with Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#permissions). ###### TTL (time to live) The `ttl` (time to live) parameter defines how many minutes the permissions remain valid. After expiration, the client must get a new token to maintain access. `ttl` is required for every grant call. There is no default value. The maximum value is 43,200 (30 days). For more details, see [TTL in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#ttl). ###### RegEx patterns Use regular expressions (RegEx) to specify permissions by pattern instead of listing each resource. Define RegEx permissions as `patterns` before making a grant request. For more details, see [RegEx in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#regex). ###### Authorized user ID Setting an `authorized_user_id` in the token specifies which client should use this token in every request to PubNub. If you do not set `authorized_user_id` during the grant request, the token can be used by any client with any `userId`. Restrict tokens to a single `authorized_user_id` to prevent impersonation. For more details, see [Authorized UUID in Access Manager v3](https://www.pubnub.com/docs/general/security/access-control#authorized-uuid). ### Method(s) ```ruby grant_token(ttl: ttl, authorized_user_id: authorized_user_id, users_permissions: users, spaces_permissions: spaces) ``` | Parameter | Description | | --- | --- | | `ttl` *Type: `Integer`Default: n/a | Total number of minutes for which the token is valid. The minimum allowed value is 1., The maximum is 43,200 minutes (30 days). | | `authorized_user_id`Type: `String`Default: n/a | Single `uuid` which is authorized to use the token to make API requests to PubNub. | | `users_permissions`Type: `Hash`Default: n/a | Hash containing all User permissions provided as a list of individual permissions or RegEx patterns, for example: `{"user-1": Pubnub::Permissions.res(get: true, update: true, delete: true),"^user-2.$": Pubnub::Permissions.pat(...)}`. | | `spaces_permissions`Type: `Hash`Default: n/a | Hash containing all Space permissions provided as a list of individual permissions or RegEx patterns, for example: `{"space-1": Pubnub::Permissions.res(read: true, write: true, manage: true, delete: true, get: true, update: true, join: true),"^space-2.$": Pubnub::Permissions.pat(...)}`. | | `meta`Type: `Object`Default: n/a | Extra metadata to be published with the request. Values must be scalar only; arrays or objects aren't supported. | :::note Required key/value mappings For a successful request, you must specify permissions for at least one User or Space, either as a resource list or as a pattern (RegEx). ::: ### Sample code ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-userId", spaces_permissions: { "my-space": Pubnub::Permissions.res( read: true ) } ); ``` ### Returns ```ruby # { "message" => "Success", "token" => "p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6han3Jwsample3KgQ3NwY6BDcGF0pERjaG3BjoERGOAeTyWGJI" } }, @status = { :code => 200 } > ``` ### Other examples #### Grant an authorized client different levels of access to various resources in a single call The code below grants `my-authorized-userId`: * Read access to `space-a`, and get to `userId-c`. * Read/write access to `space-b`, `space-c`, `space-d`, and get/update to `userId-d`. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-userId", spaces_permissions: { "space-a": Pubnub::Permissions.res( read: true ), "space-b": Pubnub::Permissions.res( read: true, write: true ), "space-c": Pubnub::Permissions.res( read: true, write: true ), "space-d": Pubnub::Permissions.res( read: true, write: true ) }, users_permissions: { "userId-c": Pubnub::Permissions.res( get: true ), "userId-d": Pubnub::Permissions.res( get: true, update: true ) } ); ``` #### Grant an authorized client read access to multiple spaces using RegEx The code below grants `my-authorized-userId` read access to all channels that match the `space-[A-Za-z0-9]` RegEx pattern. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-userId", spaces_permissions: { "^space-[A-Za-z0-9]$": Pubnub::Permission.pat( read: true ) }, ); ``` #### Grant an authorized client different levels of access to various resources and read access to spaces using RegEx in a single call The code below grants the `my-authorized-userId`: * Read access to `space-a` and `userId-c`. * Read/write access to `space-b`, `space-c`, `space-d`, and get/update to `userId-d`. * Read access to all channels that match the `space-[A-Za-z0-9]` RegEx pattern. ```ruby pubnub.grant_token( ttl: 15, authorized_user_id: "my-authorized-userId", space_permissions: { "space-a": Pubnub::Permissions.res( read: true ), "space-b": Pubnub::Permissions.res( read: true, write: true ), "space-c": Pubnub::Permissions.res( read: true, write: true ), "space-d": Pubnub::Permissions.res( read: true, write: true ), "^space-[A-Za-z0-9]$": Pubnub::Permission.pat( read: true ) }, users_permissions: { "userId-c": Pubnub::Permissions.res( get: true ), "userId-d": Pubnub::Permissions.res( get: true, update: true ) } ); ``` ### Error responses If you submit an invalid request, the server returns HTTP 400 with a message that identifies the missing or incorrect argument. Causes can include a RegEx issue, an [invalid timestamp](https://support.pubnub.com/hc/en-us/articles/360051973331-Why-do-I-get-Invalid-Timestamp-when-I-try-to-grant-permission-using-Access-Manager-), or incorrect permissions. The server returns error details in JSON. ## Revoke token :::note Requires Access Manager add-on This method requires that the *Access Manager* add-on is enabled for your key in the [Admin Portal](https://admin.pubnub.com/). Read the [support page](https://support.pubnub.com/hc/en-us/articles/360051974791-How-do-I-enable-add-on-features-for-my-keys-) on enabling add-on features on your keys. ::: :::note Enable token revoke To revoke tokens, you must first enable this feature on the [Admin Portal](https://admin.pubnub.com/). To do that, navigate to your app's keyset and mark the *Revoke v3 Token* checkbox in the *ACCESS MANAGER* section. ::: The `revoke_token()` method allows you to disable an existing token and revoke all permissions embedded within. You can only revoke a valid token previously obtained using the `grant_token()` method. Use this method for tokens with `ttl` less than or equal to 30 days. If you need to revoke a token with a longer `ttl`, [contact support](https://www.pubnub.com/docs/mailto:support@pubnub.com). For more information, refer to [Revoke permissions](https://www.pubnub.com/docs/general/security/access-control#revoke-permissions). ### Method(s) ```ruby revoke_token( token: token ) ``` | Parameter | Description | | --- | --- | | `token` *Type: `String`Default: n/a | Existing token with embedded permissions. | ### Sample code ```ruby pubnub.revoke_token("p0thisAkFl043rhDXisRGNoYW6han3Jwsample3KgQ3NwY6BDcGF0pERjaG3BjoERGOAeTyWGJI") ``` ### Returns ```ruby { "message" => "Success" } }, @status = { :code => 200 } > ``` ### Error Responses If you submit an invalid request, the server returns an error status code with a descriptive message informing which of the provided arguments is missing or incorrect. Depending on the root cause, this operation may return the following errors: * `400 Bad Request` * `403 Forbidden` * `503 Service Unavailable` ## Parse token The `parse_token()` method decodes an existing token and returns the object containing permissions embedded in that token. The client can use this method for debugging to check the permissions to the resources or find out the token's `ttl` details. ### Method(s) ```ruby parse_token( token: token ) ``` | Parameter | Description | | --- | --- | | `token` *Type: `String`Default: n/a | Current token with embedded permissions. | ### Sample code ```ruby pubnub.parse_token("p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI") ``` ### Returns ```ruby { "v"=>2, "t"=>1627968380, "ttl"=>15, "res"=>{ "chan"=>{ "channel-1"=>239 }, "grp"=>{ "channel_group-1"=>5 }, "usr"=>{}, "spc"=>{}, "uuid"=>{ "uuid-1"=>104} }, "pat"=>{ "chan"=>{ "^channel-\\S*$"=>239 }, "grp"=>{ "^:channel_group-\\S*$"=>5 }, "usr"=>{}, "spc"=>{}, "uuid"=>{ "^uuid-\\S*$"=>104 } }, "meta"=>{}, "uuid"=>"test-authorized-uuid", "sig"=>"\xFAT\xFA\xF0\x9E\xF6\xB9)b\xCF;aJ\xC55i26\xAF\x02V\xF9\x8A\xC0H\xD5\x8Ay\xC3\xAC\x92\\" } ``` ### Error Responses If you receive an error while parsing the token, it may suggest that the token is damaged. In that case, request the server to issue a new one. ## Set token The `set_token()` method is used by the client devices to update the authentication token granted by the server. ### Method(s) ```ruby set_token(token: token) ``` | Parameter | Description | | --- | --- | | `token` *Type: `String`Default: n/a | Current token with embedded permissions. | ### Sample code ```ruby pubnub.set_token("p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI") ``` ### Returns This method doesn't return any response value. ## Terms in this document * **Access Manager** - A cryptographic, token-based permission administrator that allows you to regulate clients' access to PubNub resources, such as channels, channel groups, and user IDs. * **Action** - The type of activity (procedure) to execute when a condition is satisfied (for example, sending a message). * **Billing alert notification** - A means of informing a user that a billing alert has been triggered. Before notifications can happen, a billing alert must be triggered first. * **Business Object** - A container for data fields and metrics that defines aggregations and data sources. * **Channel** - A pathway for sending and receiving messages between devices, created automatically when you first use it, that can handle any number of users and messages for different communication needs, like 1-1 text chats, group conversations, and other data streaming. * **Channel pattern** - A way to group and analyze channel data to track performance metrics like message counts and user engagement over time with PubNub Insights. * **Condition** - A requirement that must be satisfied or evaluated to true for an action to be executed. Input in a decision table. * **Cryptor** - An implementation of a specific cryptographic algorithm used for data encryption/decryption that adheres to a standard interface. * **Dashboard** - A collection of widgets (charts) that give an overview of the metrics one is evaluating. * **Data fields** - Data you want Illuminate to track. These can be quantitative (measures), like "Number" or "Timestamp" or qualitative (dimensions) values, like "String" that can be used to categorize and segment data. Data fields can be aggregated and calculated. * **Decision** - A collection (or decision table) of conditions and actions. When conditions are satisfied, the corresponding actions are triggered as per defined rules. * **End Customer** - A customer of a PubNub partner. End customers do not have direct access to the Admin Portal. Instead, they interact with PubNub products—such as Illuminate—through the partner’s portal, where PubNub services are embedded. They can create PubNub objects only within this partner-provided environment. * **Entity** - A subscribable object within a PubNub SDK that allows you to perform context-specific operations. * **Listener** - A function or objectthat reacts to events or messages, like new chat messages or connection updates, letting your app respond in real-time. * **Mapped/Unmapped** - Whether the data source for a data field has been defined or the action has been configured. * **MCP Server** - A Model Context Protocol server that coordinates communication and synchronization between AI agents, clients, or services, such as Cursor IDE and Windsurf. * **Message** - A unit of data transmitted between clients or between a client and a server in PubNub, containing information such as text, binary data, or structured data formats like JSON. Messages are sent over channels and can be tracked for delivery and read status. * **Metric** - What exactly is evaluated using measures and dimensions (collectively called data fields), as well as aggregation functions. * **Module** - A Functions v1 container that groups related functions for configuration and deployment on an app’s keysets. * **Origin** - The subdomain used to establish a connection to the PubNub network that allows your application's traffic to appear like it's coming from your own domain. * **Package** - A Functions v2 container that groups Functions, tracks Revisions, and is deployed to keysets. * **Partner** - A PubNub customer who resells PubNub products, such as Illuminate, to their own customers. Partners have access to the Admin Portal, enabling them to create and manage PubNub objects for themselves or on behalf of their end customers. * **Publish Key** - A unique identifier that allows your application to send messages to PubNub channels. It's part of your app's credentials and should be kept secure. * **PubNub** - PubNub is a real-time messaging platform that provides APIs and SDKs for building scalable applications. It handles the complex infrastructure of real-time communication, including: Message delivery and persistence, Presence detection, Access control, Push notifications, File sharing, Serverless processing with Functions and Events & Actions, Analytics and monitoring with BizOps Workspace, AI-powered insights with Illuminate. * **Push token** - A device identifier issued by a push provider (APNs or FCM) used to register a device for receiving mobile push notifications. * **Rule** - A definition (row in a decision table) stating which action should be triggered for which condition. * **Service Integration** - A machine identity that represents a program or service consuming the Admin API, scoped to your account and authenticated using expirable API keys with configurable permissions. * **Signal** - A non-persistent message limited to 64 bytes designed for high-volume usecases where the the most recent data is relevant, like GPS location updates. * **Subscribe Key** - A unique identifier that allows your application to receive messages from PubNub channels. It's part of your app's credentials and should be kept secure. * **Timetoken** - A unique identifier for each message that represents the number of 100-nanosecond intervals since January 1, 1970, for example, 16200000000000000. * **Trigger details** - A set of predefined criteria for a given billing alert. When met, billing alert notifications are generated. * **User** - An individual or entity that interacts with a system, application, or service. In PubNub, a user typically refers to someone who sends or receives messages through the platform, identified by a unique user ID or username. * **User ID** - UTF-8 encoded, unique string of up to 92 characters used to identify a single client (end user, device, or server) that connects to PubNub. * **Vibe Coding** - A way to build applications in an intuitive, relaxed, and improvisational manner, using AI tools and natural language descriptions.